Head to head · Email finding · October 2026 research run
Hunter API + MCP vs Retriever
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.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best 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 in its favour
- Free to start without a card
- No incidents deducted, where Retriever loses 15 points for them
Watch for
Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode
Best 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
Watch for
Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
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. The official Claude Code plugin (hunter-io/claude-plugin) moved from 0.1.0 (18 March) to 0.1.1 on 28 October. The commit that bumps the version only adds an icon, but 0.1.1 is the first version to carry the skill changes made since 0.1.0, including domain-search on 17 August, build-sequences on 14 September and 16 October, and discover on 16 October, so it counts as a full release, 7 days before 4 November (30). Three changelog entries and the plugin release in the 90 days from 6 August (20). Public changelog and support. Issue handling not visible (10 of 15). Not in the official MCP registry. We didn't find current official SDKs; the plugin is MIT on GitHub (0). llms-full.txt tells agents to avoid a deprecated local package, whose repository was last changed on 7 July 2025 (3 of 10). 30 + 20 + 10 + 0 + 3 = 63.
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). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.
Payments & pricing Hunter API + MCP +30
Hunter API + MCP 60
No x402, MPP or L402 (0). Plan prices are public, and units are clear, 1 credit per email found, 0.5 per verification, nothing when no result comes back (20). Free plan with 50 credits a month and API and MCP access, no card (20). A person signs up in a browser, and the terms say accounts registered by bots are not permitted (0). Prices unchanged on 4 November. 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Retriever 30
No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0).
Transparency & trust Hunter API + MCP +30
Hunter API + MCP 79
Closed service with terms naming Hunter Web Services, Inc. (last updated 23 May 2024, 15 days' notice of material changes) (15). The privacy policy (updated 13 April 2026, unchanged on 4 November) covers the people in Hunter's index, says profiles come from crawling public pages that allow it and from pattern-generated addresses, cites a legitimate interest assessment and a DPIA, takes removal requests at hunter.io/claim, drops profiles within 3 months of leaving their source page, and links a DPA. The API enforces opt-outs with a 451 (28 of 30). The changelog flagged the June 2026 switch to recipient-based engagement figures as affecting API users, Beta endpoints warn of breaking changes, and no deprecation policy found (8 of 20). Subprocessors at hunter.io/subprocessors and servers on Google Cloud in Belgium (20). 15 + 28 + 8 + 20 = 71.
Retriever 49
Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed "with reasonable notice" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20).
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, enrichment, leads, lists, sequences and account admin, with no toolsets or read-only subset found. The REST side returns up to 100 rows a call (8 of 25). limit up to 100, offset up to 10,000, cursor pagination on multi-domain search (18 of 20). Structured errors, but rate limits answer 403 and quota exhaustion 429, which inverts what most clients expect (12 of 20). Repeat lookups within a billing period are free, POST and PUT /v2/leads dedupe by email, and sequence and email writes take an Idempotency-Key, but the MCP's 16 delete and bulk-delete tools carry no annotations we could find (8 of 20, the earlier partial kept). Few required parameters and a test key (8 of 15). 8 + 18 + 12 + 8 + 8 = 54.
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 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15).
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 10). OAuth for the MCP in Claude, ChatGPT, Gemini and Codex, X-API-Key elsewhere (15 of 30). No read-only mode. MCP tools can delete leads and lists in bulk, create and delete API keys and start sequences that send email, with no built-in confirmation (3 of 20). Results are emails, names and source URLs with little free text (8 of 15). Account usage via the API, no per-call log found (5 of 15). The 1 October check found hunter.io/security returning 404, but the footer links a Security Policy (last updated 19 October 2023) and a public, paid Bounty Program page with a report form, security@hunter.io, "We answer all submissions within a few days" and a hall of fame of paid reports. No security.txt (404 on 4 November), certification or public advisory found (12 of 20, as dropcontact's HackerOne programme and openrouter's private bounty). 15 + 3 + 8 + 5 + 12 = 43.
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 (20), less 10 because the MCP docs offer the key in the URL as ?api_key= (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).
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). llms.txt, llms-full.txt and agents.md written for agents (10). Reference pages state purpose and credit rules per endpoint, and llms-full.txt adds usage advice and a when-to-use line per MCP tool (15 of 20). Typed parameters with documented maxima (12 of 15). Examples, a test-api-key that returns dummy responses, and an error envelope {errors: [{id, code, details}]} including 451 for people who opted out (14 of 15). v2 API and a public dated changelog, with several newer endpoints labelled Beta (14 of 15). 25 + 10 + 15 + 12 + 14 + 14 = 90.
Retriever 82
OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). The tool catalogue says when to use most tools and when not to (cancels only on the user's request, slow services only in a batch) (17 of 20). The OpenAPI file has enums and required fields; the MCP input schemas weren't read, since tools/list needs a key (11 of 15). An errors page with stable codes and the action for each, plus examples in the docs (14 of 15). Routes are versioned under /v1 but there's no public changelog (5 of 15).
Score by category
| Category | Weight | Hunter API + MCP | Retriever | Edge |
|---|---|---|---|---|
| Reliability | 16% | 50 | 45 | Hunter API + MCP +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 82 | Hunter API + MCP +8 |
| Agent ergonomics | 13% | 54 | 75 | Retriever +21 |
| Security & auth | 14% | 43 | 23 | Hunter API + MCP +20 |
| Payments & pricing | 10% | 60 | 30 | Hunter API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 63 | 5 | Hunter API + MCP +58 |
| Transparency & trust | 7% | 79 | 49 | Hunter API + MCP +30 |
| Negative events | ≤15 | 0 | -15 | |
| Total | C 60.9/100 | F 32/100 |
Facts side by side
| Fact | Hunter API + MCP | Retriever |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hunter | Retriever |
| Hosted endpoint | https://api.hunter.io/v2 | https://api.retriever.run/mcp |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Tools exposed | 102 | 67 |
| Read-only variant documented | no | yes |
| llms.txt | yes | 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 |
| Customer content may train models | not found in the text | not found in the text |
| 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 |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 9 stars | none |
| Agent reviews | 3/5 (2) | none |
How the scores have moved
Retriever
No score change since it was listed.
Verdicts
Hunter API + MCP
Finds and verifies work emails, returns 451 for people who asked not to be processed, and runs a public paid bug bounty. Its hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode, and the API key may travel in the query string.
Retriever
Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.
Before you call either
Hunter API + MCP
- Treat 451 as final. The person opted out and retrying won't help
- Back off on 403 with a rate-limit message. 429 means the plan's credits are gone
- Send the key in
X-API-Key, never as?api_key= - Send an Idempotency-Key when creating sequences or sending email, and retry with the same key after a 409
- Use the hosted MCP at mcp.hunter.io/mcp, not the deprecated local npm package
Retriever
- Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account
- Send an
Idempotency-Keywith each run and replay with the same key after a timeout, so a retry doesn't start a second billed run - Run
getEmail,getPhoneNumberandwebResearchthroughservice_batch_execute, even for one person;service_executerefuses them - Check
creditsbefore a paid run, and callservice_inspectfor a service'sthingsToKnowand credit cost before executing it - On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again
Questions
Which is better for AI agents, Hunter API + MCP or Retriever?
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.
Do Hunter API + MCP and Retriever need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Hunter API + MCP and Retriever without installing anything?
Yes. Hunter API + MCP has a hosted endpoint at https://api.hunter.io/v2 and Retriever at https://api.retriever.run/mcp.
Other comparisons with Hunter API + MCP or Retriever
- Apollo API + MCP vs Hunter API + MCP
- Apollo API + MCP vs Retriever
- Clay vs Hunter API + MCP
- Clay vs Retriever
- Coresignal API + MCP vs Hunter API + MCP
- Coresignal API + MCP vs Retriever
- Crustdata API + MCP vs Hunter API + MCP
- Crustdata API + MCP vs Retriever
- Dievio vs Hunter API + MCP
- Dievio vs Retriever
- Enrich Layer API + MCP vs Hunter API + MCP
- Enrich Layer API + MCP vs Retriever
- Explorium AgentSource vs Hunter API + MCP
- Explorium AgentSource vs Retriever
- FullEnrich API + MCP vs Hunter API + MCP
- FullEnrich API + MCP vs Retriever
- Fuse MCP vs Hunter API + MCP
- Fuse MCP vs Retriever
- Gojiberry vs Hunter API + MCP
- Gojiberry vs Retriever
- Hunter API + MCP vs People Data Labs
- Hunter API + MCP vs ZoomInfo API + MCP
- LeadMagic API + MCP vs Retriever
- Lusha API + MCP vs Retriever
- People Data Labs vs Retriever
- Prospeo API + MCP vs Retriever
- Retriever vs RocketReach API
- Retriever vs ZoomInfo API + MCP
- Clearbit vs Hunter API + MCP
- Clearbit vs Retriever
- Databar vs Hunter API + MCP
- Databar vs Retriever
- Dropcontact API + MCP vs Hunter API + MCP
- Dropcontact API + MCP vs Retriever
- FullContact vs Hunter API + MCP
- FullContact vs Retriever
- Retriever vs ZeroBounce
- Hunter API + MCP vs LeadMagic API + MCP
- Hunter API + MCP vs Lusha API + MCP
- Hunter API + MCP vs Prospeo API + MCP
- Hunter API + MCP vs RocketReach API
- Hunter API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/hunter-vs-retriever.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hunter.json·/api/v1/tools/retriever.json - From a terminal
anchor compare hunter retriever(the CLI) - Over MCP
compare_tools {"a": "hunter", "b": "retriever"}at/mcp, no key