Head to head · Lead search · October 2026 research run

Coresignal API + MCP vs Hunter API + MCP

Coresignal API + MCP scores 62.1 (B) on agent readiness against Hunter API + MCP's 60.9 (C), and leads in 4 of 7 scored categories. Hunter API + MCP leads on payments & pricing and transparency & trust. Both do lead search.

Best lead, contact and company data APIs for AI agents · All 253 leads comparisons

Which one, for what

Coresignal API + MCP B

Best for Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.

Ahead on

  • Reliability, 60 against 50
  • Agent ergonomics, 73 against 54
  • Security & auth, 58 against 43
  • Maintenance & community, 82 against 63

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

Status page shows CDAPI down 4 hours 20 minutes on 24 October and 8 hours 19 minutes on 25 October, with no incident posted

Hunter API + MCP C

Best for Finding and verifying work emails from a domain or a name, where GDPR handling of the people looked up matters.

Ahead on

  • Payments & pricing, 60 against 30
  • Transparency & trust, 79 against 71

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Coresignal API + MCP loses 3 points for them

Watch for

Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode

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.

Payments & pricing Hunter API + MCP +30

Coresignal API + MCP 30

No x402, MPP or L402 (0). Every plan price, credit allowance and per-endpoint credit cost is public, and only successful collect or enrich calls are charged (20). 7-day trial with 2,000 credits once per company email domain. The trial docs don't mention a card, and the card requirement rests on the 30 September check (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 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.

Agent ergonomics Coresignal API + MCP +19

Coresignal API + MCP 73

The hosted MCP has 5 tools, and large results go to a file read back in pages with artifact_read rather than into the context (23 of 25). Search filters and pagination, with search itself free (18 of 20). 402 when credits run out and per-API response codes (14 of 20). The API is read-only apart from webhook subscriptions, credits are only taken on a 200, and MCP v2 pauses to confirm record count and credit cost before large pulls (12 of 20). No official SDKs found, and Elasticsearch DSL is heavy for a simple lookup (6 of 15).

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.

Maintenance & community Coresignal API + MCP +19

Coresignal API + MCP 82

Release notes have dated entries to 1 November 2026 (30). 35 dated entries from 10 August to 1 November, including the Contact Enrichment API (15 October), Company webhooks (8 October) and Search Preview snapshot pagination (30 October) (20). Public, detailed release notes, and we didn't test support (12 of 15). Listed in the official MCP registry as com.coresignal/mcp 2.0.0, a domain-verified namespace, published 7 August 2026 (15). No SDK packages to judge (5 of 10). 30 + 20 + 12 + 15 + 5 = 82.

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.

Security & auth Coresignal API + MCP +15

Coresignal API + MCP 58

apikey header on REST. MCP v2 signs in with OAuth 2.1 through the dashboard and keeps the key server-side. We found no key scopes (22 of 30). Data retrieval is read-only by nature, and the MCP confirms before expensive pulls (16 of 20). Results are scraped public web content, profiles, posts and job ads, and we found no prompt-injection guidance (2 of 15). Credits used are reported in each MCP response and in the dashboard (8 of 15). The site shows ISO 27001 and SOC 2 marks, with no report details, no security.txt (coresignal.com/.well-known/security.txt answers 404 on 2 November) and no bug bounty found (10 of 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.

Reliability Coresignal API + MCP +10

Coresignal API + MCP 60

Better Stack status page at status.coresignal.com with CDAPI, RTAPI and Self-service components (20). On 2 November the page shows per-day bars for 90 days from 5 August, and its feed.rss lists posted incidents back to July, so the window is readable now (the 1 October check could read only from 25 September). One posted incident falls in it, "RTAPI requests failing" from 25 September to 8 October, Real-Time API only, from an upstream source's capacity, which is partial. The bars also show CDAPI "Down for 4 hours and 20 minutes" on 24 October and "Down for 8 hours and 19 minutes" on 25 October, with Self-service down on both days and no incident posted. That is the core Data API down for more than an hour, read as one major (10). Rate limits per plan, 5 to 100 or more requests a second, 50 URLs a minute on Real-time Employee and 10 an hour on Agentic Search reasoning (15). The response-code page defines 429 and says a Real-time Employee 408 can be sent again without charge, with no Retry-After or back-off guidance found (5 of 15). No SLA found (0). The surfaces agents use are generally available (10). 20 + 10 + 15 + 5 + 0 + 10 = 60.

Hunter API + MCP 50

A status page at status.hunter.io (a Checkly dashboard) exists per the 30 September check, but it renders client-side and both the page and its incidents feed came back empty on 1 October, so components were never confirmed (15 of 20, the earlier partial kept). On 4 November its robots.txt answered with the dashboard's app page, so the host was not read further and no history is readable (5). Per-endpoint limits published, from 5 a second and 50 a minute on Discover to 15 a second and 500 a minute on Domain Search and Email Finder (15). Hitting a rate limit returns 403, while 429 means the plan's usage is spent, and no Retry-After or back-off guidance for either was found. The API reference now documents an Idempotency-Key on sequence and email writes (409 with Retry-After 2 while a request with the same key runs) and calls POST and PUT /v2/leads retry-safe, but with no overload guidance the line stays at the earlier partial (5 of 15). No SLA found (0). Generally available (10). 15 + 5 + 15 + 5 + 0 + 10 = 50.

Transparency & trust Hunter API + MCP +8

Coresignal API + MCP 71

Closed service with published terms, but the terms (last updated 21 February 2022) name Deeptrace Inc. (Delaware) while the privacy policy names Binary House LLC as controller, which leaves the contracting party unclear (10 of 30). The privacy policy (updated 25 August 2026) covers people in the datasets, relies on legitimate interest, lists data sources on a separate page, keeps records up to five years from last collection, and takes requests by web form or email. No DPA found in the policy (20 of 30). Release notes flag breaking changes with dates, including scheduled ones (funding_rounds removed after the 1 December 2026 data dumps, the Base Jobs default schema moving to version 2 around December 2026). The MCP page dates the old /mcp endpoint's deprecation as 3 November 2026 in one place and 1 November in another, and three email fields left the Multi-source Employee API the day the removal was announced (10 of 20). Subprocessors named in the policy (Stripe, SendGrid, Deeptrace, Google, Meta) with US transfers under contractual clauses (15 of 20).

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.

Score by category

CategoryWeightCoresignal API + MCPHunter API + MCPEdge
Reliability16%6050Coresignal API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8690Hunter API + MCP +4
Agent ergonomics13%7354Coresignal API + MCP +19
Security & auth14%5843Coresignal API + MCP +15
Payments & pricing10%3060Hunter API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8263Coresignal API + MCP +19
Transparency & trust7%7179Hunter API + MCP +8
Negative events≤15-30
TotalB 62.1/100C 60.9/100

Facts side by side

FactCoresignal API + MCPHunter API + MCP
KindHTTP APIHTTP API
VendorCoresignalHunter
Hosted endpointhttps://api.coresignal.com/cdapihttps://api.hunter.io/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Tools exposed5102
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.coresignal/mcpnot listed
Last release2026-11-012026-09-30
Terms last updated2022-02-21no date given
Privacy policy last updated2026-08-25no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2 stars9 stars
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Coresignal API + MCP

Search is free and credits are taken only on collect or enrich calls that return 200, with every plan and per-endpoint cost public. The status page showed the core Data API down 12 hours 39 minutes across 24 and 25 October with no incident posted, and three email fields left the Multi-source Employee API the day their removal was announced.

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.

Before you call either

Coresignal API + MCP

  1. Search for IDs first (free), then collect only the records you need
  2. Request only the bundles you need. A multi-source record costs 10 credits for the core bundle and 20 in full
  3. Use MCP v2 at /mcp/v2. The older /mcp endpoint is deprecated in November 2026
  4. Treat a 402 as out of credits, not a transient error
  5. Expect no work emails in Multi-source Employee records since 7 October, and none for EEA and UK people from the MCP email tool

Hunter API + MCP

  1. Treat 451 as final. The person opted out and retrying won't help
  2. Back off on 403 with a rate-limit message. 429 means the plan's credits are gone
  3. Send the key in X-API-Key, never as ?api_key=
  4. Send an Idempotency-Key when creating sequences or sending email, and retry with the same key after a 409
  5. Use the hosted MCP at mcp.hunter.io/mcp, not the deprecated local npm package

Questions

Which is better for AI agents, Coresignal API + MCP or Hunter API + MCP?

Coresignal API + MCP scores 62.1 (B) on agent readiness against Hunter API + MCP's 60.9 (C), and leads in 4 of 7 scored categories. Hunter API + MCP leads on payments & pricing and transparency & trust.

Do Coresignal API + MCP and Hunter API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Coresignal API + MCP and Hunter API + MCP without installing anything?

Yes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and Hunter API + MCP at https://api.hunter.io/v2.

Other comparisons with Coresignal API + MCP or Hunter API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.