Head to head · Lead search · October 2026 research run
Coresignal API + MCP vs Lusha API + MCP
Lusha API + MCP scores 64.8 (B) on agent readiness against Coresignal API + MCP's 62.1 (B), and leads in 4 of 7 scored categories. Coresignal 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 Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.
Ahead on
- Agent ergonomics, 73 against 51
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Status page shows CDAPI down 4 hours 20 minutes on 24 October and 8 hours 19 minutes on 25 October, with no incident posted
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 60
- Payments & pricing, 60 against 30
- Transparency & trust, 80 against 71
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.
Payments & pricing Lusha API + MCP +30
Coresignal API + MCP 30
No x402, MPP or L402 (0). Every plan price, credit allowance and per-endpoint credit cost is public, and only successful collect or enrich calls are charged (20). 7-day trial with 2,000 credits once per company email domain. The trial docs don't mention a card, and the card requirement rests on the 30 September check (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Lusha API + MCP 60
No x402, MPP or L402 (0). Plan prices, credit allowances and per-item credit costs are public (20). Free plan with 40 credits a month and an API key. It's a free plan, not a trial, and we didn't see a card asked (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Reliability Lusha API + MCP +25
Coresignal API + MCP 60
Better Stack status page at status.coresignal.com with CDAPI, RTAPI and Self-service components (20). On 2 November the page shows per-day bars for 90 days from 5 August, and its feed.rss lists posted incidents back to July, so the window is readable now (the 1 October check could read only from 25 September). One posted incident falls in it, "RTAPI requests failing" from 25 September to 8 October, Real-Time API only, from an upstream source's capacity, which is partial. The bars also show CDAPI "Down for 4 hours and 20 minutes" on 24 October and "Down for 8 hours and 19 minutes" on 25 October, with Self-service down on both days and no incident posted. That is the core Data API down for more than an hour, read as one major (10). Rate limits per plan, 5 to 100 or more requests a second, 50 URLs a minute on Real-time Employee and 10 an hour on Agentic Search reasoning (15). The response-code page defines 429 and says a Real-time Employee 408 can be sent again without charge, with no Retry-After or back-off guidance found (5 of 15). No SLA found (0). The surfaces agents use are generally available (10). 20 + 10 + 15 + 5 + 0 + 10 = 60.
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.
Agent ergonomics Coresignal API + MCP +22
Coresignal API + MCP 73
The hosted MCP has 5 tools, and large results go to a file read back in pages with artifact_read rather than into the context (23 of 25). Search filters and pagination, with search itself free (18 of 20). 402 when credits run out and per-API response codes (14 of 20). The API is read-only apart from webhook subscriptions, credits are only taken on a 200, and MCP v2 pauses to confirm record count and credit cost before large pulls (12 of 20). No official SDKs found, and Elasticsearch DSL is heavy for a simple lookup (6 of 15).
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 +9
Coresignal API + MCP 71
Closed service with published terms, but the terms (last updated 21 February 2022) name Deeptrace Inc. (Delaware) while the privacy policy names Binary House LLC as controller, which leaves the contracting party unclear (10 of 30). The privacy policy (updated 25 August 2026) covers people in the datasets, relies on legitimate interest, lists data sources on a separate page, keeps records up to five years from last collection, and takes requests by web form or email. No DPA found in the policy (20 of 30). Release notes flag breaking changes with dates, including scheduled ones (funding_rounds removed after the 1 December 2026 data dumps, the Base Jobs default schema moving to version 2 around December 2026). The MCP page dates the old /mcp endpoint's deprecation as 3 November 2026 in one place and 1 November in another, and three email fields left the Multi-source Employee API the day the removal was announced (10 of 20). Subprocessors named in the policy (Stripe, SendGrid, Deeptrace, Google, Meta) with US transfers under contractual clauses (15 of 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).
Score by category
| Category | Weight | Coresignal API + MCP | Lusha API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 85 | Lusha API + MCP +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 83 | Coresignal API + MCP +3 |
| Agent ergonomics | 13% | 73 | 51 | Coresignal API + MCP +22 |
| Security & auth | 14% | 58 | 59 | Lusha API + MCP +1 |
| Payments & pricing | 10% | 30 | 60 | Lusha API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 82 | even |
| Transparency & trust | 7% | 71 | 80 | Lusha API + MCP +9 |
| Negative events | ≤15 | -3 | -6 | |
| Total | B 62.1/100 | B 64.8/100 |
Facts side by side
| Fact | Coresignal API + MCP | Lusha API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Coresignal | Lusha |
| Hosted endpoint | https://api.coresignal.com/cdapi | https://api.lusha.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Tools exposed | 5 | 50 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.coresignal/mcp | com.lusha.mcp/mcp |
| Last release | 2026-11-01 | 2026-10-29 |
| Terms last updated | 2022-02-21 | no date given |
| Privacy policy last updated | 2026-08-25 | 2026-09-01 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 2 stars | none |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Coresignal API + MCP higher, the other way from the total score.
| Reviewer | Coresignal API + MCP | Lusha API + MCP |
|---|---|---|
| LedgerCost analyst | 4/5 Free search, then 1 to 20 credits a record | 3/5 Seven credits for one contact, and a miss still costs one |
| WardenSecurity auditor | 3/5 Read-only data, scraped text unmarked | 3/5 Credit caps on admin keys, none on the rest |
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
Coresignal API + MCP
Search is free and credits are taken only on collect or enrich calls that return 200, with every plan and per-endpoint cost public. The status page showed the core Data API down 12 hours 39 minutes across 24 and 25 October with no incident posted, and three email fields left the Multi-source Employee API the day their removal was announced.
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
Coresignal API + MCP
- Search for IDs first (free), then collect only the records you need
- Request only the bundles you need. A multi-source record costs 10 credits for the core bundle and 20 in full
- Use MCP v2 at /mcp/v2. The older /mcp endpoint is deprecated in November 2026
- Treat a 402 as out of credits, not a transient error
- Expect no work emails in Multi-source Employee records since 7 October, and none for EEA and UK people from the MCP email tool
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
Questions
Which is better for AI agents, Coresignal API + MCP or Lusha API + MCP?
Lusha API + MCP scores 64.8 (B) on agent readiness against Coresignal API + MCP's 62.1 (B), and leads in 4 of 7 scored categories. Coresignal API + MCP leads on agent ergonomics.
Do Coresignal API + MCP and Lusha API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Coresignal API + MCP and Lusha API + MCP without installing anything?
Yes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and Lusha API + MCP at https://api.lusha.com.
Other comparisons with Coresignal API + MCP or Lusha API + MCP
- Apollo API + MCP vs Coresignal API + MCP
- Apollo API + MCP vs Lusha API + MCP
- Clay vs Coresignal API + MCP
- Clay vs Lusha API + MCP
- Coresignal API + MCP vs Crustdata API + MCP
- Coresignal API + MCP vs Databar
- Coresignal API + MCP vs Dievio
- Coresignal API + MCP vs Enrich Layer API + MCP
- Coresignal API + MCP vs Explorium AgentSource
- Coresignal API + MCP vs FullEnrich API + MCP
- Coresignal API + MCP vs Fuse MCP
- Coresignal API + MCP vs Gojiberry
- Coresignal API + MCP vs Hunter API + MCP
- Coresignal API + MCP vs LeadMagic API + MCP
- Coresignal API + MCP vs People Data Labs
- Coresignal API + MCP vs Prospeo API + MCP
- Coresignal API + MCP vs Retriever
- Coresignal API + MCP vs RocketReach API
- Coresignal API + MCP vs ZoomInfo API + MCP
- Crustdata API + MCP vs Lusha API + MCP
- Dievio vs Lusha API + MCP
- Enrich Layer API + MCP vs Lusha API + MCP
- Explorium AgentSource vs Lusha API + MCP
- FullEnrich API + MCP vs Lusha API + MCP
- Fuse MCP vs Lusha API + MCP
- Gojiberry vs Lusha API + MCP
- LeadMagic API + MCP vs Lusha API + MCP
- Lusha API + MCP vs People Data Labs
- Lusha API + MCP vs Prospeo API + MCP
- Lusha API + MCP vs Retriever
- Lusha API + MCP vs RocketReach API
- Lusha API + MCP vs ZoomInfo API + MCP
- Clearbit vs Coresignal API + MCP
- Clearbit vs Lusha API + MCP
- Coresignal API + MCP vs Dropcontact API + MCP
- Coresignal API + MCP vs FullContact
- Coresignal API + MCP vs ZeroBounce
- Databar vs Lusha API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- FullContact vs Lusha API + MCP
- Lusha API + MCP vs ZeroBounce
- Hunter API + MCP vs Lusha API + MCP
Machine-readable
- This page as Markdown
/compare/coresignal-vs-lusha.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/coresignal.json·/api/v1/tools/lusha.json - From a terminal
anchor compare coresignal lusha(the CLI) - Over MCP
compare_tools {"a": "coresignal", "b": "lusha"}at/mcp, no key