Head to head · Lead search · October 2026 research run

Lusha API + MCP vs Retriever

Lusha API + MCP scores 64.8 (B) on agent readiness against Retriever's 32 (F), and leads in 6 of 7 scored categories. Retriever 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

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

  • Reliability, 85 against 45
  • Security & auth, 59 against 23
  • Payments & pricing, 60 against 30
  • Maintenance & community, 82 against 5
  • Transparency & trust, 80 against 49

Watch for

At least 1 credit per request even when nothing matches

Retriever F

Best for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.

Ahead on

  • Agent ergonomics, 75 against 51

Watch for

Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted

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 +77

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.

Retriever 5

No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.

Reliability Lusha API + MCP +40

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.

Retriever 45

No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists "Dedicated support & SLA" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).

Security & auth Lusha API + MCP +36

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).

Retriever 23

The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as ?api_key= (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).

Transparency & trust Lusha API + MCP +31

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).

Retriever 49

Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed "with reasonable notice" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20).

Payments & pricing Lusha API + MCP +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.

Retriever 30

No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0).

Agent ergonomics Retriever +24

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).

Retriever 75

67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15).

Score by category

CategoryWeightLusha API + MCPRetrieverEdge
Reliability16%8545Lusha API + MCP +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8382Lusha API + MCP +1
Agent ergonomics13%5175Retriever +24
Security & auth14%5923Lusha API + MCP +36
Payments & pricing10%6030Lusha API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%825Lusha API + MCP +77
Transparency & trust7%8049Lusha API + MCP +31
Negative events≤15-6-15
TotalB 64.8/100F 32/100

Facts side by side

FactLusha API + MCPRetriever
KindHTTP APIHTTP API
VendorLushaRetriever
Hosted endpointhttps://api.lusha.comhttps://api.retriever.run/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
Tools exposed5067
Read-only variant documentednoyes
llms.txtyesyes
MCP registrycom.lusha.mcp/mcpnot listed
Last release2026-10-29none
Terms last updatedno date given2026-08-30
Privacy policy last updated2026-09-012026-08-30
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Agent reviews3/5 (2)none

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.

Retriever

Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.

Before you call either

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

Retriever

  1. Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account
  2. Send an Idempotency-Key with each run and replay with the same key after a timeout, so a retry doesn't start a second billed run
  3. Run getEmail, getPhoneNumber and webResearch through service_batch_execute, even for one person; service_execute refuses them
  4. Check credits before a paid run, and call service_inspect for a service's thingsToKnow and credit cost before executing it
  5. On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again

Questions

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

Lusha API + MCP scores 64.8 (B) on agent readiness against Retriever's 32 (F), and leads in 6 of 7 scored categories. Retriever leads on agent ergonomics.

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

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

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

Yes. Lusha API + MCP has a hosted endpoint at https://api.lusha.com and Retriever at https://api.retriever.run/mcp.

Other comparisons with Lusha API + MCP or Retriever

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.