Head to head · Lead search · October 2026 research run
Lusha API + MCP vs Prospeo API + MCP
Lusha API + MCP scores 64.8 (B) on agent readiness against Prospeo API + MCP's 53.6 (D), and leads in 5 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for Sales teams that want contact and company enrichment, signals and prospecting from one vendor, with a free plan to start.
Ahead on
- Reliability, 85 against 35
- Schema & documentation, 83 against 61
- Security & auth, 59 against 54
- Maintenance & community, 82 against 19
- Transparency & trust, 80 against 60
Watch for
At least 1 credit per request even when nothing matches
Best for An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop.
Ahead on
- Agent ergonomics, 79 against 51
Also in its favour
- Runs on your own machine
- 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 status page, SLA or changelog
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 +63
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.
Prospeo API + MCP 19
The MCP repository, read from a clone, has 1.1.1 tagged on 13 October 2026, which changes only the version, the lockfile, server.json and a new publish workflow, so it is a packaging release that counts half and can't set recency. Code merged on 19 October 2026 (tools loaded from Prospeo's backend at startup) has no version or tag yet. The newest release that changes code is 1.1.0 on 1 June 2026, and the API docs weren't re-read under the terms, so recency rests on 1 June, between 90 and 180 days ago (10). One packaging release in the 90 days from 6 August counts half, under three (0). No changelog, and the MCP repo's commits are all from staff. We couldn't see issue handling from git (5 of 25). server.json names io.prospeo/prospeo-mcp-server and the publish workflow targets the official MCP registry, but a vendor's own file is a claim and no registry page could be read (0, 15 before). The publish workflow runs the vitest tests before each manual release, with one tag so far (4 of 10). 10 + 0 + 5 + 0 + 4 = 19.
Reliability Lusha API + MCP +50
Lusha API + MCP 85
Atlassian Statuspage at status.lusha.com with a Lusha API component and AWS us-east-1 components (20). The history feed (history.atom) lists one incident from 4 August to 2 November 2026, errors and incomplete results in Prospecting company search for some users on 7 August (20:44 to 21:33 IDT), partial and so minor; the 3 August API error incident falls just outside the window (20). Limits per plan, from 40 a minute and 100 a day on Free to 300 a minute and 50,000 a day on Scale (15). 429 documented with advice to back off exponentially, no Retry-After mentioned (10 of 15). The trust centre states a 99.95 per cent uptime SLA (10). Generally available (10). 20+20+15+10+10+10 = 85.
Prospeo API + MCP 35
Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No status page found, and status.prospeo.io doesn't resolve in DNS as of 2 October (0). No incident history to read (5). Limits per plan and endpoint, enrichment 5 a second and 2,000 a day on Starter up to 30 a second and 500,000 a day on Pro, search 1 to 5 a second, with x-daily-request-left and x-minute-request-left headers (15). 429 on rate limits, but the search reference lists invalid keys, missing credits and internal errors all as HTTP 400, so a client can't tell a retryable failure from its own mistake by status code. No Retry-After or back-off guidance found (5 of 15). No SLA found (0). Generally available (10).
Agent ergonomics Prospeo API + MCP +28
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).
Prospeo API + MCP 79
Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. 8 MCP tools, but their filter schemas come from 44 kB of zod source, so tools/list is heavier than the count suggests. Bulk enrichment returns a compact record per person (20 of 25). 25 results a page, up to 1,000 pages, 20+ filters, and a free search_suggestions tool that resolves canonical filter values (20). Body error codes such as INSUFFICIENT_CREDITS, PLAN_REQUIRED and INVALID_FILTERS, mapped to plain messages by the MCP (13 of 20). Repeated searches within 30 days and re-enrichment within 90 days are free, and every MCP tool is annotated readOnlyHint true, destructiveHint false (18 of 20). At least one include filter is required. The MCP package is the only official client (8 of 15).
Schema & documentation Lusha API + MCP +22
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).
Prospeo API + MCP 61
Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No OpenAPI file for the REST API. The MCP tools carry full JSON Schema inputs generated from zod (15 of 25). No llms.txt found (0). The MCP tool descriptions each say when to use it, when to use another tool instead, the credit cost and the order of calls (20). Typed filters with documented limits, such as 500 company names a query (13 of 15). Reference examples and body error_code values, undercut by HTTP 400 for most failures (10 of 15). No changelog or versioning. The docs carry 'last updated 11 June 2026' (3 of 15).
Transparency & trust Lusha API + MCP +20
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).
Prospeo API + MCP 60
The MCP server is MIT. The API is closed, run by Defastra Tech Inc. doing business as Prospeo per the 30 September reading of the privacy policy (18 of 30). The terms, read on 4 November 2026 from the page's own data, make Prospeo a controller for its dataset and a processor for customer uploads under a DPA they incorporate, answer rights requests within a month, remove uploads from active systems within 90 days of account closure, and refresh the dataset within about 24 months. They also take a perpetual, irrevocable licence to ingest and retain uploaded contact data, which stays in the dataset after an account closes. The privacy policy and DPA weren't re-read (18 of 30). The terms promise at least 90 days' notice of breaking changes to public API endpoints, a written policy with a notice period (20). They say Prospeo is a Canadian company with primary hosting on AWS us-east-1 and sub-processors in the United States and other countries, with change notices at least 30 days ahead, but no named sub-processor list was read (10 of 20). 18 + 18 + 20 + 10 = 66.
Security & auth Lusha API + MCP +5
Lusha API + MCP 59
REST takes an api_key header. Every user gets a key, admins can mint more and cap each one's monthly credits, and a key a user makes for themselves has no cap of its own. OAuth for the MCP in Claude, ChatGPT and Codex, x-api-key elsewhere. No endpoint scopes found (22 of 30). Credit caps limit damage, but the MCP isn't read-only and writes to workspace tables and CRM exports (8 of 20). Signals and conversation data carry some free text, no injection guidance found (5 of 15). Usage endpoint, no per-call log found (8 of 15). SOC 2 Type II and five ISO certifications claimed in the trust centre, ISO 27701 named in the privacy notice, security.txt valid (Expires 1 May 2027, read on 2 November), no bug bounty found (16 of 20).
Prospeo API + MCP 54
Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. Keys in the X-KEY header, several keys per account. The hosted MCP takes OAuth or the same header (22 of 30). Every tool reads, and the MCP marks them so (16 of 20). Results are structured profile and company fields with little free text (8 of 15). Rate-limit headers, an account endpoint and a free flag on responses that shows whether credits were spent. No per-call log found (8 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). No 2025 or 2026 record in the CVE list names Prospeo. 22 + 16 + 8 + 8 + 0 = 54.
Score by category
| Category | Weight | Lusha API + MCP | Prospeo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 35 | Lusha API + MCP +50 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 83 | 61 | Lusha API + MCP +22 |
| Agent ergonomics | 13% | 51 | 79 | Prospeo API + MCP +28 |
| Security & auth | 14% | 59 | 54 | Lusha API + MCP +5 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 19 | Lusha API + MCP +63 |
| Transparency & trust | 7% | 80 | 60 | Lusha API + MCP +20 |
| Negative events | ≤15 | -6 | 0 | |
| Total | B 64.8/100 | D 53.6/100 |
Facts side by side
| Fact | Lusha API + MCP | Prospeo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Lusha | Prospeo |
| Hosted endpoint | https://api.lusha.com | https://api.prospeo.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 50 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | com.lusha.mcp/mcp | io.prospeo/prospeo-mcp-server |
| Last release | 2026-10-29 | 2026-10-13 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2026-09-01 | couldn't be read |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | none | 0 stars, 641 npm/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Prospeo API + MCP higher, the other way from the total score.
| Reviewer | Lusha API + MCP | Prospeo API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 Seven credits for one contact, and a miss still costs one | 4/5 $0.0245 an email, and a miss costs nothing |
| WardenSecurity auditor | 3/5 Credit caps on admin keys, none on the rest | 3/5 Eight read-only tools and a perpetual licence |
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
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.
Prospeo API + MCP
MCP tool descriptions say when to use each tool, its credit cost and the next call, and the terms promise 90 days' notice of breaking API changes. There is no status page, SLA or changelog, the newest code release dates from 1 June 2026, and uploaded contact data enters Prospeo's dataset under a perpetual licence.
Before you call either
Lusha API + MCP
- Batch up to 25 contacts a request. A single bulk request costs 1 credit, not 1 per contact
- Ask for phones only when needed. A phone is 5 credits against 1 for an email
- Use the Buying Group endpoint. Decision Makers was retired on 2026-09-04
- When Enrich Contacts returns a
job, pollGET /v3/contacts/jobs/{jobId}everyretryAfterseconds untilcomplete,expiredorfailed. Polling costs no credits - Back off exponentially on 429. Free keys stop at 100 requests a day
Prospeo API + MCP
- Call
search_suggestionsbefore using location, technology or industry filters, or the search returns nothing - Pass
person_idvalues from search intobulk_enrich_person, 25 at a time - Branch on the body
error_code, not the HTTP status, which is 400 for most failures - Set
enrich_mobileonly when needed. A mobile costs 10 credits against 1 for an email - Use Enrich Person. The old Email Finder endpoint was removed in March 2026
Questions
Which is better for AI agents, Lusha API + MCP or Prospeo API + MCP?
Lusha API + MCP scores 64.8 (B) on agent readiness against Prospeo API + MCP's 53.6 (D), and leads in 5 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics.
Do Lusha API + MCP and Prospeo API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Lusha API + MCP and Prospeo API + MCP without installing anything?
Yes. Lusha API + MCP has a hosted endpoint at https://api.lusha.com and Prospeo API + MCP at https://api.prospeo.io.
Other comparisons with Lusha API + MCP or Prospeo API + MCP
- Apollo API + MCP vs Lusha API + MCP
- Apollo API + MCP vs Prospeo API + MCP
- Clay vs Lusha API + MCP
- Clay vs Prospeo API + MCP
- Coresignal API + MCP vs Lusha API + MCP
- Coresignal API + MCP vs Prospeo API + MCP
- Crustdata API + MCP vs Lusha API + MCP
- Crustdata API + MCP vs Prospeo API + MCP
- Dievio vs Lusha API + MCP
- Dievio vs Prospeo API + MCP
- Enrich Layer API + MCP vs Lusha API + MCP
- Enrich Layer API + MCP vs Prospeo API + MCP
- Explorium AgentSource vs Lusha API + MCP
- Explorium AgentSource vs Prospeo API + MCP
- FullEnrich API + MCP vs Lusha API + MCP
- FullEnrich API + MCP vs Prospeo API + MCP
- Fuse MCP vs Lusha API + MCP
- Fuse MCP vs Prospeo API + MCP
- Gojiberry vs Lusha API + MCP
- Gojiberry vs Prospeo API + MCP
- LeadMagic API + MCP vs Lusha API + MCP
- LeadMagic API + MCP vs Prospeo API + MCP
- Lusha API + MCP vs People Data Labs
- Lusha API + MCP vs Retriever
- Lusha API + MCP vs RocketReach API
- Lusha API + MCP vs ZoomInfo API + MCP
- People Data Labs vs Prospeo API + MCP
- Prospeo API + MCP vs Retriever
- Prospeo API + MCP vs RocketReach API
- Prospeo API + MCP vs ZoomInfo API + MCP
- Clearbit vs Lusha API + MCP
- Clearbit vs Prospeo API + MCP
- Databar vs Lusha API + MCP
- Databar vs Prospeo API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- Dropcontact API + MCP vs Prospeo API + MCP
- FullContact vs Lusha API + MCP
- FullContact vs Prospeo API + MCP
- Lusha API + MCP vs ZeroBounce
- Prospeo API + MCP vs ZeroBounce
- Hunter API + MCP vs Lusha API + MCP
- Hunter API + MCP vs Prospeo API + MCP
Machine-readable
- This page as Markdown
/compare/lusha-vs-prospeo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lusha.json·/api/v1/tools/prospeo.json - From a terminal
anchor compare lusha prospeo(the CLI) - Over MCP
compare_tools {"a": "lusha", "b": "prospeo"}at/mcp, no key