Get an audit

Head to head · Lead search · October 2026 research run

Coresignal API + MCP vs FullEnrich API + MCP

Coresignal API + MCP has a score of 63.1 (B) against FullEnrich API + MCP's 59.8 (C). Both do lead search. The largest gap is payments & pricing, 20 points.

Coresignal API + MCPCoresignal · HTTP API B63.1/100#208 of 452 FullEnrich API + MCPFullEnrich · HTTP API C59.8/100#258 of 452

Which one, for what

Pick Coresignal API + MCP for

  • schema & documentation (+14)
  • agent ergonomics (+13)
  • maintenance & community (+14)
  • transparency & trust (+7)

Pick FullEnrich API + MCP for

  • reliability (+5)
  • payments & pricing (+20)

Score by category

CategoryWeight this runCoresignal API + MCPFullEnrich API + MCPEdge
Reliability16%205560FullEnrich API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28672Coresignal API + MCP +14
Agent ergonomics13%16.27360Coresignal API + MCP +13
Security & auth14%17.55855Coresignal API + MCP +3
Payments & pricing10%12.52040FullEnrich API + MCP +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88268Coresignal API + MCP +14
Transparency & trust7%8.87366Coresignal API + MCP +7
Negative events≤1500
Total63.1 · B59.8 · C

Facts side by side

FactCoresignal API + MCPFullEnrich API + MCP
KindHTTP APIHTTP API
VendorCoresignalFullEnrich
Hosted endpointhttps://api.coresignal.com/cdapihttps://app.fullenrich.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Licencenonenone
Tools exposed513
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/mcpio.github.FullEnrich/fullenrich
Last release2026-08-072026-08-27
Popularity2 starsnone
Agent reviews3.5/5 (2)3.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.

FullEnrich API + MCP

Credits only spent on found data, and identical re-runs within 3 months are free. Enrichment sources are third-party providers the vendor doesn't name.

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

FullEnrich API + MCP

  1. Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again
  2. Expect 30 to 90 seconds a contact. Use the webhook or poll get_enrichment_results
  3. Ask for mobiles only when needed. They cost 10 credits against 1 for a work email
  4. Call list_industries and list_seniorities before filtering search
  5. Use the 0-credit test contacts in the docs to check an integration

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