# Dropcontact API + MCP vs Retriever (slim)

> Dropcontact scores 61.6 (C) to Retriever's 32 (F) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md (~5,100 tokens) · this version ~1,030 tokens · JSON https://www.anchorterminal.com/compare/dropcontact-vs-retriever.json · canonical https://www.anchorterminal.com/compare/dropcontact-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)

Dropcontact API + MCP scores 61.6 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema & documentation and agent ergonomics. Both do lead enrichment.

- Dropcontact API + MCP: C 61.6, rank #722 of 1557 · https://www.anchorterminal.com/tools/dropcontact.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- Dropcontact API + MCP, good for European teams cleaning and completing contact lists where GDPR handling matters more than coverage. Ahead on Reliability, 85 against 45; Security & auth, 59 against 23; Payments & pricing, 60 against 30; Maintenance & community, 15 against 5; Transparency & trust, 72 against 49. Also Free to start without a card; No incidents deducted, where Retriever loses 15 points for them.
- 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 Schema & documentation, 82 against 54; Agent ergonomics, 75 against 64.

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

| Fact (where they differ) | Dropcontact API + MCP | Retriever |
| --- | --- | --- |
| Vendor | Dropcontact | Retriever |
| Hosted endpoint | `https://api.dropcontact.com/v1` | `https://api.retriever.run/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Tools exposed | none | 67 |
| Read-only variant documented | no | yes |
| Terms last updated | 2025-08-01 | 2026-08-30 |
| Privacy policy last updated | 2020-06-04 | 2026-08-30 |
| Terms restrict automated access | not found in the text | yes |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Reliability, Dropcontact API + MCP +40: Dropcontact API + MCP 85 (Atlassian Statuspage at status.dropcontact.com with a Dropcontact API component beside the app, file, CRM and website 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, Dropcontact API + MCP +36: Dropcontact API + MCP 59 (One API key per account in the `X-Access-Token` header, no scopes found.); 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…)
- Payments & pricing, Dropcontact API + MCP +30: Dropcontact API + MCP 60 (No x402, MPP or L402 (0).); Retriever 30 (No x402, MPP or L402 (0).)
- Schema & documentation, Retriever +28: Dropcontact API + MCP 54 (No OpenAPI file or other machine-readable contract published (0).); Retriever 82 (OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25).)
- Transparency & trust, Dropcontact API + MCP +23: Dropcontact API + MCP 72 (Closed service with terms (updated 5 August 2025) naming Dropcontact SAS, registered in Bobigny, no.); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Agent ergonomics, Retriever +11: 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 RE…); 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…)
