# Leadsets vs Retriever (slim)

> Leadsets scores 62.9 (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/leadsets-vs-retriever.md (~5,000 tokens) · this version ~1,030 tokens · JSON https://www.anchorterminal.com/compare/leadsets-vs-retriever.json · canonical https://www.anchorterminal.com/compare/leadsets-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-22
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Leadsets scores 62.9 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and schema & documentation. Both do lead search.

- Leadsets: B 62.9, rank #661 of 1571 · https://www.anchorterminal.com/tools/leadsets.min.md
- Retriever: F 32, rank #1467 of 1571 · https://www.anchorterminal.com/tools/retriever.min.md
- Leadsets, good for Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits. Ahead on Agent ergonomics, 90 against 75; Security & auth, 67 against 23; Payments & pricing, 50 against 30; Maintenance & community, 80 against 5; Transparency & trust, 67 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 Reliability, 45 against 40; Schema & documentation, 82 against 58.

| Category | Leadsets | Retriever |
| --- | --- | --- |
| Reliability (16%) | 40 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 58 | 82 |
| Agent ergonomics (13%) | 90 | 75 |
| Security & auth (14%) | 67 | 23 |
| Payments & pricing (10%) | 50 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 5 |
| Transparency & trust (7%) | 67 | 49 |

| Fact (where they differ) | Leadsets | Retriever |
| --- | --- | --- |
| Vendor | Leadsets | Retriever |
| Hosted endpoint | `https://mcp.leadsets.ai` | `https://api.retriever.run/mcp` |
| Pricing | Freemium | Paid |
| Tools exposed | 8 | 67 |
| Read-only variant documented | no | yes |
| MCP registry | `io.github.leadsets/leadsets` | not listed |
| Last release | 2026-11-22 | none |
| Terms last updated | 2026-11-15 | 2026-08-30 |
| Privacy policy last updated | 2026-11-19 | 2026-08-30 |
| Terms restrict automated access | not found in the text | yes |

Why the edge:
- Maintenance & community, Leadsets +75: Leadsets 80 (The product is about two weeks old.); 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).)
- Security & auth, Leadsets +44: Leadsets 67 (Bearer keys with a full, data or read access level, an expiry of never, 30, 90 or 365 days, hashed storage, revocation within a minute and a documented rotation…); 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…)
- Schema & documentation, Retriever +24: Leadsets 58 (No OpenAPI file or other machine-readable contract found in the docs or llms.txt, and the MCP server answers `initialize` with 401 without a key, so its tool sc…); Retriever 82 (OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25).)
- Payments & pricing, Leadsets +20: Leadsets 50 (No x402, MPP or L402. An exhausted Free meter answers 402 `free_records_exhausted` with no payment requirements (0).); Retriever 30 (No x402, MPP or L402 (0).)
- Transparency & trust, Leadsets +18: Leadsets 67 (Closed service with terms naming Mobylogix LLC under Texas law.); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Agent ergonomics, Leadsets +15: Leadsets 90 (Eight MCP tools per the docs, with sizes unread, and REST responses sized by `limit` and a `count_only` mode that returns only a count, but no field selection f…); 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…)
