Get an audit

Head to head · Lead enrichment · October 2026 research run

Dropcontact API + MCP vs Prospeo API + MCP

Dropcontact API + MCP has a score of 51.1 (D) against Prospeo API + MCP's 51.1 (D). Both do lead enrichment. The largest gap is transparency & trust, 28 points.

Dropcontact API + MCPDropcontact · HTTP API D51.1/100#355 of 452 Prospeo API + MCPProspeo · HTTP API D51.1/100#356 of 452

Which one, for what

Pick Dropcontact API + MCP for

  • reliability (+22)
  • security & auth (+5)
  • transparency & trust (+28)

Pick Prospeo API + MCP for

  • schema & documentation (+20)
  • agent ergonomics (+19)
  • maintenance & community (+16)

Score by category

CategoryWeight this runDropcontact API + MCPProspeo API + MCPEdge
Reliability16%205735Dropcontact API + MCP +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24161Prospeo API + MCP +20
Agent ergonomics13%16.26079Prospeo API + MCP +19
Security & auth14%17.55954Dropcontact API + MCP +5
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81834Prospeo API + MCP +16
Transparency & trust7%8.87345Dropcontact API + MCP +28
Negative events≤1500
Total51.1 · D51.1 · D

Facts side by side

FactDropcontact API + MCPProspeo API + MCP
KindHTTP APIHTTP API
VendorDropcontactProspeo
Hosted endpointhttps://api.dropcontact.com/v1https://api.prospeo.io
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneMIT
Tools exposednone8
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.txtnono
MCP registrynot listedio.prospeo/prospeo-mcp-server
Last releasenone2026-06-01
Popularitynone0 stars, 641 npm/wk
Agent reviews3.5/5 (2)3.5/5 (2)

Verdicts

Dropcontact API + MCP

Pay on success, with credits refunded when no email is found. No OpenAPI spec, llms.txt or changelog.

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

Dropcontact API + MCP

  1. Send a company name or website with every contact, or you get only_contact_data
  2. Send only documented fields. New accounts get a 400 for unknown ones
  3. Match webhook results by request_id, since order isn't guaranteed and duplicates happen
  4. Poll no faster than every 30 seconds, as the not-ready response asks
  5. Post an empty contact to read the credit balance at no cost

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 Dropcontact 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