# Huntertech (remote · mcp.huntertech.io)

Vendor incidents, public pricing, and plan-gated account tools. OAuth at /mcp/auth.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.huntertech.io`: 88/100, [markdown](https://verifymcp.io/servers/io-huntertech-vendor-insights/api-v1-mcp.md), [page](https://verifymcp.io/servers/io-huntertech-vendor-insights/api-v1-mcp)
- remote · `www.huntertech.io`: 39/100, [markdown](https://verifymcp.io/servers/io-huntertech-vendor-insights/api-v1-mcp-auth.md), [page](https://verifymcp.io/servers/io-huntertech-vendor-insights/api-v1-mcp-auth)
- remote · `www.huntertech.io`: 30/100, [markdown](https://verifymcp.io/servers/io-huntertech-vendor-insights/api-v1-mcp-sse.md), [page](https://verifymcp.io/servers/io-huntertech-vendor-insights/api-v1-mcp-sse)
- remote · `mcp.huntertech.io`: 79/100 (this document), [markdown](https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp.md), [page](https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp)
- remote · `mcp.huntertech.io`: 30/100, [markdown](https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp-2.md), [page](https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp-2)
- remote · `mcp.huntertech.io`: 39/100, [markdown](https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp-auth.md), [page](https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp-auth)

## Channel facts

- Endpoint: `https://mcp.huntertech.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (75% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Huntertech MCP server?

Huntertech is a hosted endpoint at https://mcp.huntertech.io/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.

### Claude

```bash
claude mcp add --transport http io-huntertech-vendor-insights 'https://mcp.huntertech.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-huntertech-vendor-insights": {
      "url": "https://mcp.huntertech.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-huntertech-vendor-insights": {
      "type": "http",
      "url": "https://mcp.huntertech.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-huntertech-vendor-insights]
url = "https://mcp.huntertech.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-huntertech-vendor-insights": {
      "type": "remote",
      "url": "https://mcp.huntertech.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-huntertech-vendor-insights --url 'https://mcp.huntertech.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-huntertech-vendor-insights:
    url: "https://mcp.huntertech.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-huntertech-vendor-insights": {
      "Transport": "http",
      "Url": "https://mcp.huntertech.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-huntertech-vendor-insights -t streamable-http -u 'https://mcp.huntertech.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-huntertech-vendor-insights": {
      "type": "http",
      "url": "https://mcp.huntertech.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 75, 0)

- [security] Tool “get_pricing” 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_vendor_incidents” 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
- [functional regression] Schema quality: pass → fail
- [cosmetic] “get_vendor_incidents” added an optional parameter “status”
- [cosmetic] “get_all_vendor_incidents” added an optional parameter “status”
- [cosmetic] “get_vendor_incidents” reworded the description of “timePeriod”
- [cosmetic] “get_vendor_incidents” reworded the description of “includeResolved”
- [cosmetic] “get_all_vendor_incidents” reworded the description of “timePeriod”
- [cosmetic] “get_all_vendor_incidents” reworded the description of “includeResolved”

### 2026-10-25 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 75)

First indexed and scored.

## MCP tools (4)

### `list_monitored_vendors` (~70 tokens)

List Monitored Vendors

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.

Output parameters:

- `accessLevel` (string)
- `success` (boolean)
- `total` (number)
- `vendors` (array)

### `get_vendor_incidents` (~230 tokens)

Get Vendor Incidents

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.

Input parameters:

- `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, required): Vendor ID, for example zscaler, cloudflare, github, openai.

Output parameters:

- `accessLevel` (string)
- `checkedAt` (string|null)
- `dataWindow` (string)
- `incidents` (array)
- `lastUpdated` (string|null)
- `nextAction` (string)
- `success` (boolean)
- `total` (number)
- `vendorId` (string)
- `vendorIncidentsUrl` (string|null)
- `vendorName` (string)

### `get_all_vendor_incidents` (~202 tokens)

Get All Vendor Incidents

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.

Input parameters:

- `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.

Output parameters:

- `accessLevel` (string)
- `checkedAt` (string|null)
- `dataWindow` (string)
- `incidents` (array)
- `lastUpdated` (string|null)
- `nextAction` (string)
- `success` (boolean)
- `total` (number)
- `vendorId` (string)
- `vendorIncidentsUrl` (string|null)
- `vendorName` (string)

### `get_pricing` (~87 tokens)

Get Pricing

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 75

## Common questions

### 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://mcp.huntertech.io/mcp).

### Is the Huntertech MCP server safe to use?

Huntertech scores 79 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.huntertech.io/mcp
- Website: https://www.huntertech.io/vendor-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-huntertech-vendor-insights/mcp