Hunter MCP (remote)

55/100
Last tested 2026-11-03 (Fresh: tested within 30 days) Needs key API key

Advisories: not checked (remote-only)

Security review: not tested

Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology

  • Install20/20
  • Handshake5/30
  • Maintenance15/25
  • Docs15/15
  • License0/10

Vendor-hosted
Hunter's hosted endpoint https://mcp.hunter.io/mcp answered HTTP 401 'Unauthorized: a Hunter API key is required' with no WWW-Authenticate/OAuth metadata (test run results, Nov 3, 2026), so no tools were listed and the key label is 'Needs key'. Not tested with a key.
Hunter-hosted MCP; needs a Hunter account (API key or sign-in). Our keyless probe got HTTP 401 'Unauthorized: a Hunter API key is required' with no OAuth challenge. Listed under the vendor-hosted rule (Our review, Nov 2, 2026).
Sources: https://hunter.io/mcp · https://hunter.io/changelog/tag/mcp/

Transport: Streamable HTTP · not tested

Token cost (estimate): the figure is pending. We have no tools/list capture to estimate from.

Permissions: tool permissions pending · Auth: OAuth · Rate limit: unknown · Pricing unit: unknown

Auth: OAuth. Rate limit: unknown. Pricing unit: unknown.

HTTP 401 'Unauthorized: a Hunter API key is required', no WWW-Authenticate/OAuth metadata

Score 55/100 · Tools 0 · Token cost pending · Compare · Last tested 2026-11-03 · Server version not reported · Remote endpoint https://mcp.hunter.io/mcp (streamable-http)

Summary: Hunter MCP (remote) requires credentials or a backing service before it will list tools.

Evidence summary

Handshake
auth-gated
Tools listed
0
Context cost
Pending The token cost figure is pending. ranking
Login
Needs a key
Tested
2026-11-03

Test results

TestResultPointsEvidence
installpass20Endpoint https://mcp.hunter.io/mcp reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers.
handshakeauth-gated5Auth-gated: HTTP 401 without credentials. We do not sign in; not counted as working.
maintenancepartial15Vendor-hosted rule: scored from dated Hunter changelog entry 2026-09-30 (https://hunter.io/changelog/tag/mcp/), 34 days before test. Registry: Not found in the official MCP registry (search 'hunter', 2026-11-03 UTC).
docspass15official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://hunter.io/mcp).
licensefail0Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source).

Local-model readiness

Not tested

Not yet tested (no tools/list response without credentials).

What we tested and what we didn't

Tested on 2026-11-03

  • We attempted an MCP initialize to the vendor's hosted endpoint with no credentials and got HTTP 401, so we never reached the tool list (Method details: initialize POST answered 401; tools/list not sent)
  • Auth response: HTTP 401 'Unauthorized: a Hunter API key is required', no WWW-Authenticate/OAuth metadata. It needs an API key; we did not test with one
  • Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15)
  • Maintenance: dated vendor source, dated Hunter changelog entry 2026-09-30 (15/25)
  • License: a hosted service has no license to cite (0/10)
  • Token cost (estimate)

Not tested

  • Security: not audited (hosted service; no code to review, no permission or data-flow analysis)
  • Behaviour after signing in, or with a real account
  • Source code, repository activity or an open-source license (none published for the hosted service)
  • Performance, rate limits or load
  • Real tasks (no functional task runs yet)

Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that giving it access to your data carries no risk.

Known security issues

Not checked (remote-only): hosted endpoint, version unknown.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.

Raw test record (JSON)
{
  "name": "hunter-remote",
  "version": null,
  "registry": "remote",
  "status": "auth-gated",
  "tested": "2026-11-03",
  "tools_count": null,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://mcp.hunter.io/mcp reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers."
    ],
    "handshake": [
      "auth-gated",
      5,
      "Auth-gated: HTTP 401 without credentials. We do not sign in; not counted as working."
    ],
    "maintenance": [
      "partial",
      15,
      "Vendor-hosted rule: scored from dated Hunter changelog entry 2026-09-30 (https://hunter.io/changelog/tag/mcp/), 34 days before test. Registry: Not found in the official MCP registry (search 'hunter', 2026-11-03 UTC)."
    ],
    "docs": [
      "pass",
      15,
      "official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://hunter.io/mcp)."
    ],
    "license": [
      "fail",
      0,
      "Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
    ]
  }
}

Install

https://mcp.hunter.io/mcp

Tools listed

Not available (handshake did not complete without credentials).

Quick config

{
  "mcpServers": {
    "hunter-mcp-remote": {
      "type": "http",
      "url": "https://mcp.hunter.io/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

Without credentials it said (verbatim): HTTP 401 without credentials

  1. Install. No install step: it is a remote server at https://mcp.hunter.io/mcp.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
  "mcpServers": {
    "hunter-mcp-remote": {
      "type": "http",
      "url": "https://mcp.hunter.io/mcp"
    }
  }
}

Not tested with credentials We have not tested this with real credentials.

Test history

Follow this server (RSS) · Monthly changelog

Related: Troubleshooting: 401 Unauthorized on remote servers · MCP servers that need an API key · How to protect AI API keys

FAQ

Is Hunter MCP deprecated?

No. hunter-remote was not deprecated or archived when we last tested it on 2026-11-03.

What replaces Hunter MCP?

Nothing; Hunter MCP (remote) is not deprecated as of 2026-11-03.

Does Hunter MCP need an API key?

Yes. Needs key: the endpoint returned HTTP 401 'Unauthorized: a Hunter API key is required', no WWW-Authenticate/OAuth metadata and listed no tools.

Embed the badge

TestedMCP: 55/100, tested 2026-11-03

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue