# Lusha API + MCP vs Retriever (slim)

> Lusha scores 64.8 (B) to Retriever's 32 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/lusha-vs-retriever.md (~4,650 tokens) · this version ~1,030 tokens · JSON https://www.anchorterminal.com/compare/lusha-vs-retriever.json · canonical https://www.anchorterminal.com/compare/lusha-vs-retriever
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Lusha API + MCP: B 64.8, rank #566 of 1557 · https://www.anchorterminal.com/tools/lusha.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- Lusha API + MCP, good 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.
- Retriever, good 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.

| Category | Lusha API + MCP | Retriever |
| --- | --- | --- |
| Reliability (16%) | 85 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 82 |
| Agent ergonomics (13%) | 51 | 75 |
| Security & auth (14%) | 59 | 23 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 5 |
| Transparency & trust (7%) | 80 | 49 |

| Fact (where they differ) | Lusha API + MCP | Retriever |
| --- | --- | --- |
| Vendor | Lusha | Retriever |
| Hosted endpoint | `https://api.lusha.com` | `https://api.retriever.run/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Pricing | Freemium | Paid |
| Tools exposed | 50 | 67 |
| Read-only variant documented | no | yes |
| MCP registry | `com.lusha.mcp/mcp` | not listed |
| Last release | 2026-10-29 | none |
| Terms last updated | no date given | 2026-08-30 |
| Privacy policy last updated | 2026-09-01 | 2026-08-30 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Maintenance & community, Lusha API + MCP +77: Lusha API + MCP 82 (Version 2.20.1 on 2026-10-29 (30).); 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).)
- 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).); Retriever 45 (No status page found, linked from neither the site nor the docs (0), so no incident history to read (5).)
- Security & auth, Lusha API + MCP +36: Lusha API + MCP 59 (REST takes an `api_key` header.); 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 (2…)
- Transparency & trust, Lusha API + MCP +31: Lusha API + MCP 80 (Closed service with terms naming Lusha Systems Inc.); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Payments & pricing, Lusha API + MCP +30: Lusha API + MCP 60 (No x402, MPP or L402 (0).); Retriever 30 (No x402, MPP or L402 (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).); 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…)
