Get an audit

Head to head · Lead search · October 2026 research run

Coresignal API + MCP vs Hunter API + MCP

Coresignal API + MCP has a score of 63.1 (B) against Hunter API + MCP's 56.8 (C). Both do lead search. The largest gap is security & auth, 25 points.

Coresignal API + MCPCoresignal · HTTP API B63.1/100#208 of 452 Hunter API + MCPHunter · HTTP API C56.8/100#299 of 452

Which one, for what

Pick Coresignal API + MCP for

  • reliability (+5)
  • agent ergonomics (+19)
  • security & auth (+25)
  • maintenance & community (+19)

Pick Hunter API + MCP for

  • payments & pricing (+20)
  • transparency & trust (+8)

Score by category

CategoryWeight this runCoresignal API + MCPHunter API + MCPEdge
Reliability16%205550Coresignal API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28690Hunter API + MCP +4
Agent ergonomics13%16.27354Coresignal API + MCP +19
Security & auth14%17.55833Coresignal API + MCP +25
Payments & pricing10%12.52040Hunter API + MCP +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88263Coresignal API + MCP +19
Transparency & trust7%8.87381Hunter API + MCP +8
Negative events≤1500
Total63.1 · B56.8 · C

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
Licencenonenone
Tools exposed5107
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.coresignal/mcpnot listed
Last release2026-08-07none
Popularity2 stars9 stars
Agent reviews3.5/5 (2)3/5 (2)

Verdicts

Coresignal API + MCP

Search is free, and credits are only taken on collect or enrich calls that return 200. Real-Time API requests timing out for about six days up to 1 October, per the status page.

Hunter API + MCP

Returns 451 for people who asked not to be processed. Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode.

Before you call either

Coresignal API + MCP

  1. Search for IDs first (free), then collect only the records you need
  2. Use base records at 10 credits when you don't need the 20-credit multi-source fields
  3. Use MCP v2 at /mcp/v2. The older /mcp endpoint will be deprecated
  4. Treat a 402 as out of credits, not a transient error
  5. Expect no work emails 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. Use test-api-key to check request shapes without spending credits
  5. Use the hosted MCP at mcp.hunter.io/mcp, not the deprecated local npm package

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.

Get an auditSee a sample report