Head to head · Lead enrichment · October 2026 research run

Dropcontact API + MCP vs Lusha API + MCP

Lusha API + MCP scores 64.8 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 3 of 7 scored categories. Dropcontact API + MCP leads on agent ergonomics. Both do lead enrichment.

Best lead, contact and company data APIs for AI agents · All 253 leads comparisons

Which one, for what

Dropcontact API + MCP C

Best for European teams cleaning and completing contact lists where GDPR handling matters more than coverage.

Ahead on

  • Agent ergonomics, 64 against 51

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where Lusha API + MCP loses 6 points for them

Watch for

No OpenAPI file or changelog

Lusha API + MCP B

Best for Sales teams that want contact and company enrichment, signals and prospecting from one vendor, with a free plan to start.

Ahead on

  • Schema & documentation, 83 against 54
  • Maintenance & community, 82 against 15
  • Transparency & trust, 80 against 72

Watch for

At least 1 credit per request even when nothing matches

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Lusha API + MCP +67

Dropcontact API + MCP 15

No changelog. The newest dated API change found is the API_ERROR option, on by default for accounts created since 1 June 2026, which answers 400 when every record in a request has an error. That is between 90 and 180 days ago (10). The rebuilt docs carry no dated entries, so none fall in the 90 days from 6 August (0). Email support on every plan and no public changelog (5 of 15). No official SDKs and no registry entry we could read (0). No packages to judge (0, an in-between 3 with nothing behind it before). 10 + 0 + 5 + 0 + 0 = 15.

Lusha API + MCP 82

Version 2.20.1 on 2026-10-29 (30). Fourteen dated versions from 2.7.0 on 5 August to 2.20.1 on 29 October 2026 (20). Detailed public changelog and support, issue handling not visible (12 of 15). Listed in the official MCP registry as com.lusha.mcp/mcp 1.0.0, a domain-verified namespace, active since 18 June 2026 (15). No packages to judge (5 of 10). 30+20+12+15+5 = 82.

Schema & documentation Lusha API + MCP +29

Dropcontact API + MCP 54

No OpenAPI file or other machine-readable contract published (0). llms.txt and llms-full.txt list Markdown copies of every docs page in English and French (10). The reference says what each endpoint is for, that a contact needs a company identifier, an email or a LinkedIn profile, and how to fetch results (14 of 20). Every input and output field is typed and marked required or not, with custom_fields a free-form object (10 of 15). Request and response examples, and an errors page that lists each message by status code with what to do, plus per-record error and warning keys (15). /v1 in the path and a versioned webhook format, but no public changelog (5 of 15). 0 + 10 + 14 + 10 + 15 + 5 = 54.

Lusha API + MCP 83

OpenAPI files per the 30 September check (25). llms.txt (10). Reference pages explain credit use per call with worked examples (15 of 20). Typed inputs (12 of 15). Standard HTTP codes and examples, no error catalogue found (10 of 15). Semantic versioning with a support matrix and a dated changelog. Version numbers run out of order (2.8.0 dated after 2.12.0), and breaking changes shipped in minor versions (11 of 15).

Agent ergonomics Dropcontact API + MCP +13

Dropcontact API + MCP 64

The MCP has a handful of tools (enrich from a name and company or a LinkedIn URL, validate an email, check credits, then fetch the result by request ID), and REST takes up to 250 contacts a call. No field selection (20 of 25). No search, so little to page or filter. forceResults=true returns the records already enriched (10 of 20). The errors page gives each message with a fix, and per-record keys such as only_contact_data say what to add (20). Asynchronous jobs keyed by request_id and pay on success, but no idempotency key, and webhooks can arrive out of order or twice (8 of 20). Few required fields and no official SDKs (6 of 15). 20 + 10 + 20 + 8 + 6 = 64.

Lusha API + MCP 51

The hosted MCP has 50 tools across enrichment, prospecting, signals, lookalikes, buying groups, tables, CRM export and account, with no toolsets found (5). Bulk calls take up to 25 records (8 of 25). Prospecting filters with a per-company cap and exact totals (18 of 20). Standard codes and back-off advice for 429 (12 of 20). Every request costs at least 1 credit even with no match, so retries aren't free, and the MCP writes to tables and CRM exports with no annotations found (6 of 20). No official SDKs found (7 of 15).

Transparency & trust Lusha API + MCP +8

Dropcontact API + MCP 72

Closed service with terms (updated 5 August 2025) naming Dropcontact SAS, registered in Bobigny, no. 823 752 647 (15). The personal data charter (updated 5 August 2025) keeps prospecting data 3 years after the relationship plus 4 in intermediate storage, takes rights requests at data@dropcontact.io, says data may be collected from publicly accessible information and hosted in the EU with some subcontractors in the United States under standard contractual clauses, and a DPA is published. The pricing page says processing runs only on Dropcontact's own algorithms on EU servers with no reliance on non-compliant third-party providers, and that it uses no contact databases. It now also says mobile numbers come from signature extraction within internal email flows, with five years of history, which the charter doesn't mention (22 of 30). One dated change for new accounts (1 June 2026) and no deprecation policy (8 of 20). EU hosting and US subcontractors stated, no named subprocessor list found (10 of 20). 15 + 22 + 8 + 10 = 55.

Lusha API + MCP 80

Closed service with terms naming Lusha Systems Inc. (15). The privacy notice (September 2026) covers people in the database, names its sources, including a community programme in which members share contacts from their CRM, email headers and calendars, plus data brokers and public APIs, relies on legitimate interest, names a DPO and an EU and UK representative, and takes removal requests at lusha.com/privacy-center/request-removal. Retention for contacts has no period (24 of 30). A support matrix exists, but the Decision Makers API was removed 88 days after launch with no notice period found (8 of 20). Subprocessor list published and data stored on AWS in the US (20).

Score by category

CategoryWeightDropcontact API + MCPLusha API + MCPEdge
Reliability16%8585even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5483Lusha API + MCP +29
Agent ergonomics13%6451Dropcontact API + MCP +13
Security & auth14%5959even
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1582Lusha API + MCP +67
Transparency & trust7%7280Lusha API + MCP +8
Negative events≤150-6
TotalC 61.6/100B 64.8/100

Facts side by side

FactDropcontact API + MCPLusha API + MCP
KindHTTP APIHTTP API
VendorDropcontactLusha
Hosted endpointhttps://api.dropcontact.com/v1https://api.lusha.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Tools exposednone50
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.lusha.mcp/mcp
Last releasenone2026-10-29
Terms last updated2025-08-01no date given
Privacy policy last updated2020-06-042026-09-01
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Dropcontact API + MCP higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Dropcontact API + MCP

Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.

Lusha API + MCP

API key on every plan, including Free with 40 credits a month, and a semantic-versioned changelog with frequent dated releases. At least 1 credit is charged per request even when nothing matches, and since 5 October 2026 Enrich Contacts can return partial waterfall results with a job to poll, a change announced the day it shipped.

Before you call either

Dropcontact API + MCP

  1. Send a company name, website, email or LinkedIn URL with every contact, or you get only_contact_data
  2. Read success on every 200. A result still processing answers 200 with success: false
  3. Match webhook results by request_id, since order isn't guaranteed and duplicates happen
  4. Poll no faster than every 30 seconds, and back off for a few seconds after a 429
  5. Call Get Credits to read the balance at no cost

Lusha API + MCP

  1. Batch up to 25 contacts a request. A single bulk request costs 1 credit, not 1 per contact
  2. Ask for phones only when needed. A phone is 5 credits against 1 for an email
  3. Use the Buying Group endpoint. Decision Makers was retired on 2026-09-04
  4. When Enrich Contacts returns a job, poll GET /v3/contacts/jobs/{jobId} every retryAfter seconds until complete, expired or failed. Polling costs no credits
  5. Back off exponentially on 429. Free keys stop at 100 requests a day

Questions

Which is better for AI agents, Dropcontact API + MCP or Lusha API + MCP?

Lusha API + MCP scores 64.8 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 3 of 7 scored categories. Dropcontact API + MCP leads on agent ergonomics.

Do Dropcontact API + MCP and Lusha API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Dropcontact API + MCP and Lusha API + MCP without installing anything?

Yes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and Lusha API + MCP at https://api.lusha.com.

Other comparisons with Dropcontact API + MCP or Lusha 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.