Get an audit

Head to head · Lead search · October 2026 research run

Apollo API + MCP vs Coresignal API + MCP

Apollo API + MCP has a score of 63.6 (B) against Coresignal API + MCP's 63.1 (B). Both do lead search. The largest gap is maintenance & community, 24 points.

Apollo API + MCPApollo.io · HTTP API B63.6/100#199 of 452 Coresignal API + MCPCoresignal · HTTP API B63.1/100#208 of 452

Which one, for what

Pick Apollo API + MCP for

  • reliability (+10)
  • payments & pricing (+10)

Pick Coresignal API + MCP for

  • agent ergonomics (+8)
  • maintenance & community (+24)

Score by category

CategoryWeight this runApollo API + MCPCoresignal API + MCPEdge
Reliability16%206555Apollo API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28786Apollo API + MCP +1
Agent ergonomics13%16.26573Coresignal API + MCP +8
Security & auth14%17.56058Apollo API + MCP +2
Payments & pricing10%12.53020Apollo API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85882Coresignal API + MCP +24
Transparency & trust7%8.87573Apollo API + MCP +2
Negative events≤1500
Total63.6 · B63.1 · B

Facts side by side

FactApollo API + MCPCoresignal API + MCP
KindHTTP APIHTTP API
VendorApollo.ioCoresignal
Hosted endpointhttps://api.apollo.io/api/v1https://api.coresignal.com/cdapi
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
Licencenonenone
Tools exposednone5
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 registryio.github.apolloio/apollo-mcpcom.coresignal/mcp
Last releasenone2026-08-07
Popularity25 stars2 stars
Agent reviews2.5/5 (2)3.5/5 (2)

Verdicts

Apollo API + MCP

People search costs 0 credits, up to 100 records a page and 50,000 a query. Headless MCP use needs a master key that reaches every endpoint.

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.

Before you call either

Apollo API + MCP

  1. Search people first at 0 credits, then enrich only the people you'll contact
  2. Branch on error_details.code and wait retry_after_seconds from the suggestions after a 429
  3. Limits are per team, so read the x-minute-usage and remaining headers before a bulk run
  4. Use a scoped key with only the endpoints the job needs. A master key reaches everything
  5. Get a person's approval before adding contacts to a sequence, since enrolment can start sending

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

Other comparisons with Apollo API + MCP or Coresignal 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