Get an audit

Head to head · Lead search · October 2026 research run

Coresignal API + MCP vs Prospeo API + MCP

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

Coresignal API + MCPCoresignal · HTTP API B63.1/100#208 of 452 Prospeo API + MCPProspeo · HTTP API D51.1/100#356 of 452

Which one, for what

Pick Coresignal API + MCP for

  • reliability (+20)
  • schema & documentation (+25)
  • maintenance & community (+48)
  • transparency & trust (+28)

Pick Prospeo API + MCP for

  • agent ergonomics (+6)
  • payments & pricing (+20)

Score by category

CategoryWeight this runCoresignal API + MCPProspeo API + MCPEdge
Reliability16%205535Coresignal API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28661Coresignal API + MCP +25
Agent ergonomics13%16.27379Prospeo API + MCP +6
Security & auth14%17.55854Coresignal API + MCP +4
Payments & pricing10%12.52040Prospeo API + MCP +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88234Coresignal API + MCP +48
Transparency & trust7%8.87345Coresignal API + MCP +28
Negative events≤1500
Total63.1 · B51.1 · D

Facts side by side

FactCoresignal API + MCPProspeo API + MCP
KindHTTP APIHTTP API
VendorCoresignalProspeo
Hosted endpointhttps://api.coresignal.com/cdapihttps://api.prospeo.io
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneMIT
Tools exposed58
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.txtyesno
MCP registrycom.coresignal/mcpio.prospeo/prospeo-mcp-server
Last release2026-08-072026-06-01
Popularity2 stars0 stars, 641 npm/wk
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.

Prospeo API + MCP

MCP tool descriptions say when to use each tool, its credit cost and the next call. No status page, SLA or changelog.

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

Prospeo API + MCP

  1. Call search_suggestions before using location, technology or industry filters, or the search returns nothing
  2. Pass person_id values from search into bulk_enrich_person, 25 at a time
  3. Branch on the body error_code, not the HTTP status, which is 400 for most failures
  4. Set enrich_mobile only when needed. A mobile costs 10 credits against 1 for an email
  5. Use Enrich Person. The old Email Finder endpoint was removed in March 2026

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