Get an audit

Head to head · Lead search · October 2026 research run

Coresignal API + MCP vs Crustdata API + MCP

Coresignal API + MCP has a score of 63.1 (B) against Crustdata API + MCP's 53.5 (D). Both do lead search. The largest gap is transparency & trust, 17 points.

Coresignal API + MCPCoresignal · HTTP API B63.1/100#208 of 452 Crustdata API + MCPCrustdata · HTTP API D53.5/100#331 of 452

Which one, for what

Pick Coresignal API + MCP for

  • reliability (+10)
  • payments & pricing (+15)
  • maintenance & community (+15)
  • transparency & trust (+17)

Pick Crustdata API + MCP for

No category where it leads by five points or more.

Score by category

CategoryWeight this runCoresignal API + MCPCrustdata API + MCPEdge
Reliability16%205545Coresignal API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28689Crustdata API + MCP +3
Agent ergonomics13%16.27373even
Security & auth14%17.55856Coresignal API + MCP +2
Payments & pricing10%12.5205Coresignal API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88267Coresignal API + MCP +15
Transparency & trust7%8.87356Coresignal API + MCP +17
Negative events≤150-3
Total63.1 · B53.5 · D

Facts side by side

FactCoresignal API + MCPCrustdata API + MCP
KindHTTP APIHTTP API
VendorCoresignalCrustdata
Hosted endpointhttps://api.coresignal.com/cdapihttps://api.crustdata.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPay per use
x402nono
Licencenonenone
Tools exposed5none
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 starsnone
Agent reviews3.5/5 (2)2.5/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.

Crustdata API + MCP

Per-field credit prices, readable per account from /account/endpoints, and X-Credits-Used on every response. No status page and no SLA.

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

Crustdata API + MCP

  1. Always send x-api-version: 2025-11-01. Unpinned calls get the latest version
  2. Call /account/endpoints first to see what your plan enables and what each field costs
  3. Ask only for the premium field groups you need, since each one bills
  4. Poll GET /batch/{id} before submitting more batch jobs. Active jobs count against a cap of 5 to 30
  5. Read the crustdata://catalog resource before calling MCP tools

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