@reclaimprotocol/agent vs Breach402 — Email Data-Breach Check
@reclaimprotocol/agent is an MCP server published by reclaimprotocol. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Breach402 — Email Data-Breach Check is an MCP server published by bmcxiv.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.1.43 Downloads/month (npm): 2 243 Downloads/week (npm): 1 516 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.6 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | @reclaimprotocol/agent | Breach402 — Email Data-Breach Check |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | 2026-11-04 | Not published |
| Where it runs (differs) | On your machine (@reclaimprotocol/agent) | Remote server (breach402.bmcxiv.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/reclaimprotocol/builder | Not stated |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
@reclaimprotocol/agent
Reclaim Protocol tools for AI coding agents. Reclaim lets your app verify data points about its users, such as a follower count, an account balance, or an order history. This package is the Reclaim MCP server: it gives your agent the tools to find, build,
Breach402 — Email Data-Breach Check
Data-breach & credential-exposure check for one owner-approved email. $1 USDC on Solana (x402).
How to run each
@reclaimprotocol/agent
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Breach402 — Email Data-Breach Check As a remote MCP server
claude mcp add --transport http breach402-owner-protection https://breach402.bmcxiv.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Breach402 — Email Data-Breach Check has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of @reclaimprotocol/agent nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: @reclaimprotocol/agent · What it can do: Breach402 — Email Data-Breach Check · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.