# Hunter API + MCP vs Retriever (slim)

> Hunter scores 60.9 (C) to Retriever's 32 (F) for email finding. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/hunter-vs-retriever.md (~5,050 tokens) · this version ~1,130 tokens · JSON https://www.anchorterminal.com/compare/hunter-vs-retriever.json · canonical https://www.anchorterminal.com/compare/hunter-vs-retriever
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Hunter API + MCP scores 60.9 (C) on agent readiness against Retriever's 32 (F), and leads in 6 of 7 scored categories. Retriever leads on agent ergonomics. Both do email finding.

- Hunter API + MCP: C 60.9, rank #751 of 1557 · https://www.anchorterminal.com/tools/hunter.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- Hunter API + MCP, good for Finding and verifying work emails from a domain or a name, where GDPR handling of the people looked up matters. Ahead on Reliability, 50 against 45; Schema & documentation, 90 against 82; Security & auth, 43 against 23; Payments & pricing, 60 against 30; Maintenance & community, 63 against 5; Transparency & trust, 79 against 49. Also Free to start without a card; No incidents deducted, where Retriever loses 15 points for them.
- Retriever, good for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex. Ahead on Agent ergonomics, 75 against 54.

| Category | Hunter API + MCP | Retriever |
| --- | --- | --- |
| Reliability (16%) | 50 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 90 | 82 |
| Agent ergonomics (13%) | 54 | 75 |
| Security & auth (14%) | 43 | 23 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 63 | 5 |
| Transparency & trust (7%) | 79 | 49 |

| Fact (where they differ) | Hunter API + MCP | Retriever |
| --- | --- | --- |
| Vendor | Hunter | Retriever |
| Hosted endpoint | `https://api.hunter.io/v2` | `https://api.retriever.run/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Pricing | Freemium | Paid |
| Tools exposed | 102 | 67 |
| Read-only variant documented | no | yes |
| Last release | 2026-09-30 | none |
| Terms last updated | no date given | 2026-08-30 |
| Privacy policy last updated | no date given | 2026-08-30 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | 9 stars | none |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Maintenance & community, Hunter API + MCP +58: Hunter API + MCP 63 (Newest changelog entries are three dated 30 September 2026 (the ChatGPT app, saved searches and AI tool setup paths), 35 days before 4 November.); Retriever 5 (No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0).)
- Payments & pricing, Hunter API + MCP +30: Hunter API + MCP 60 (No x402, MPP or L402 (0).); Retriever 30 (No x402, MPP or L402 (0).)
- Transparency & trust, Hunter API + MCP +30: Hunter API + MCP 79 (Closed service with terms naming Hunter Web Services, Inc.); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Agent ergonomics, Retriever +21: Hunter API + MCP 54 (The hosted MCP exposes about 100 tools (102 by our count of llms-full.txt on 4 November, 96 on 1 October, 107 in the 30 September check) across search, enrichme…); Retriever 75 (67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10…)
- Security & auth, Hunter API + MCP +20: Hunter API + MCP 43 (API keys can be created and deleted, and the docs accept the key in a header, as a bearer token or in the `api_key` query string, which puts it in logs (20 less…); Retriever 23 (The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (2…)
- Schema & documentation, Hunter API + MCP +8: Hunter API + MCP 90 (OpenAPI 3.0.3 JSON at hunter.io/openapi.json, version 2.0.0, 101 paths and 182 operations on 4 November (25).); Retriever 82 (OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25).)
