Huntertech
REMOTE · WWW.HUNTERTECH.IO · 6 COMPONENTS
Vendor incidents, public pricing, and plan-gated account tools. OAuth at /mcp/auth.
Last scanned (18 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 652 tokens (~163/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 −1
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- Tool “get_vendor_incidents” rewrote its description, which is the text the model reads security
- Tool “list_monitored_vendors” rewrote its description, which is the text the model reads security
- Tool “get_all_vendor_incidents” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “get_all_vendor_incidents” added an optional parameter “status” cosmetic
- “get_vendor_incidents” added an optional parameter “status” cosmetic
- “get_vendor_incidents” reworded the description of “includeResolved” cosmetic
- “get_vendor_incidents” reworded the description of “timePeriod” cosmetic
- “get_all_vendor_incidents” reworded the description of “timePeriod” cosmetic
- “get_all_vendor_incidents” reworded the description of “includeResolved” cosmetic
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_vendor_incidents” rewrote its description, which is the text the model reads security
- Tool “list_monitored_vendors” rewrote its description, which is the text the model reads security
- Tool “get_all_vendor_incidents” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 75% ▼ functional
- Schema quality: 352 → 462 ▼ functional
- Schema quality: excellent → good functional
- New tool “get_pricing” functional
- “get_all_vendor_incidents” reworded the description of “includeResolved” cosmetic
- “get_all_vendor_incidents” reworded the description of “limit” cosmetic
- “get_vendor_incidents” reworded the description of “includeResolved” cosmetic
- “get_vendor_incidents” reworded the description of “limit” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- HSTS header: fail → pass ▲ security
- Stability: 0.97 → pass security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Sept 26 0
- HSTS header: pass → fail ▼ security
- 27 Aug 26 0
- HSTS header: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Destructive annotations: pass functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://www.huntertech.io/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=huntertech.io | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d57cf4bcea392df40e384cfb6d573c7f |
| SANs: huntertech.io, *.huntertech.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.huntertech.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| huntertech.io. | present | 2371 | 13 | Verified |
| www.huntertech.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';base-uri 'self';object-src 'none';frame-ancestors 'none';script-src 'self' https://cdn.jsdelivr.net https://unpkg.com https://www.googletagmanager.com https://www.google-analytics.com https://static.cloudflareinsights.com 'unsafe-inline';script-src-attr 'unsafe-inline';style-src 'self' https://fonts.googleapis.com https://cdn.jsdelivr.net https://unpkg.com 'unsafe-inline';font-src 'self' https://fonts.gstatic.com;img-src 'self' data: https: blob:;connect-src 'self' https://api.mapbox.com https://events.mapbox.com https://www.google-analytics.com https://analytics.google.com https://region1.google-analytics.com https://cloudflareinsights.com;form-action 'self';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=(), payment=(), usb=(), fullscreen=(self), accelerometer=(), gyroscope=(), magnetometer=(), autoplay=(), encrypted-media=(), picture-in-picture=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.huntertech.io/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://www.huntertech.io/api/v1/mcp | HTTPS enforced | 301 | https://www.huntertech.io/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_all_vendor_incidents Get All Vendor Incidents ~202
Read-only cross-vendor incident snapshot (newest start first). Guest and Free: ongoing plus monitoring only, max 5. Optional status filters ongoing, monitoring, or resolved; resolved requires Standard or higher (includeResolved, timePeriod, or status=resolved). Signed-in callers get additional tools via tools/list, including get_incident per vendor.
| Name | Type | Req | Description |
|---|---|---|---|
| includeResolved | boolean | – | Include resolved incidents in the fetch. Requires Standard or higher. |
| limit | integer | – | Maximum incidents to return. Guest and Free maximum is 5. Standard and above maximum is 50. |
| status | string | – | Lifecycle bucket: ongoing (active impact), monitoring (watching or fix-pending), resolved (closed). investigating is an alias for ongoing. resolved requires Standard or higher. |
| timePeriod | string | – | History window such as 7d, 30d, 90d, or all when allowed by plan. Requires Standard or higher. |
| Name | Type | Req | Description |
|---|---|---|---|
| accessLevel | string | yes | – |
| checkedAt | string|null | – | – |
| dataWindow | string | – | – |
| incidents | array | yes | – |
| lastUpdated | string|null | – | – |
| nextAction | string | – | – |
| success | boolean | yes | – |
| total | number | yes | – |
| vendorId | string | – | – |
| vendorIncidentsUrl | string|null | – | – |
| vendorName | string | – | – |
No examples provided.
get_pricing Get Pricing ~87
Public plan matrix from /pricing (USD tiers and MCP entitlements). Separate from incident monitoring: use list_monitored_vendors and get_vendor_incidents for outages. Guest tools/list includes this for discovery; Standard+ sign-in (API key or OAuth at https://mcp.huntertech.io/mcp/auth) reveals history, get_incident, maintenance, probes, and watchlists.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_vendor_incidents Get Vendor Incidents ~230
Read-only incidents for one monitored vendor. Guest and Free: ongoing plus monitoring only, max 5 (default when status is omitted). Optional status narrows to ongoing, monitoring, or resolved; resolved history requires Standard or higher (use includeResolved, timePeriod, or status=resolved). After sign-in, tools/list also exposes get_incident for a single record by id.
| Name | Type | Req | Description |
|---|---|---|---|
| includeResolved | boolean | – | Include resolved incidents in the fetch. Requires Standard or higher. |
| limit | integer | – | Maximum incidents to return. Guest and Free maximum is 5. Standard and above maximum is 50. |
| status | string | – | Lifecycle bucket: ongoing (active impact), monitoring (watching or fix-pending), resolved (closed). investigating is an alias for ongoing. resolved requires Standard or higher. |
| timePeriod | string | – | History window such as 7d, 30d, 90d, or all when allowed by plan. Requires Standard or higher. |
| vendor | string | yes | Vendor ID, for example zscaler, cloudflare, github, openai. |
| Name | Type | Req | Description |
|---|---|---|---|
| accessLevel | string | yes | – |
| checkedAt | string|null | – | – |
| dataWindow | string | – | – |
| incidents | array | yes | – |
| lastUpdated | string|null | – | – |
| nextAction | string | – | – |
| success | boolean | yes | – |
| total | number | yes | – |
| vendorId | string | – | – |
| vendorIncidentsUrl | string|null | – | – |
| vendorName | string | – | – |
No examples provided.
list_monitored_vendors List Monitored Vendors ~70
Guest-safe index of vendors with public incident feeds (id, name, category, website). Pass id to get_vendor_incidents. Sign in with Huntertech MCP OAuth or an API key to expand tools/list with history (includeResolved, timePeriod), get_incident, maintenance, and analytics.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| accessLevel | string | yes | – |
| success | boolean | yes | – |
| total | number | yes | – |
| vendors | array | yes | – |
No examples provided.
How do I install the Huntertech MCP server?
Huntertech is a hosted endpoint at https://www.huntertech.io/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.huntertech.io
claude mcp add --transport http io-huntertech-vendor-insights 'https://www.huntertech.io/api/v1/mcp'
What is the Huntertech MCP server?
Huntertech is an MCP server listed in the public MCP registry as io.huntertech/vendor-insights. Vendor incidents, public pricing, and plan-gated account tools. OAuth at /mcp/auth. This page covers its hosted endpoint (https://www.huntertech.io/api/v1/mcp).
Is the Huntertech MCP server safe to use?
Huntertech scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Huntertech MCP server expose?
Huntertech exposes 4 tools: list_monitored_vendors, get_vendor_incidents, get_all_vendor_incidents, get_pricing. Their descriptions and schemas cost roughly 589 tokens of context every time the server is loaded.
Does the Huntertech MCP server require authentication?
No. We connected to Huntertech without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Huntertech MCP server still maintained?
Huntertech is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.