ReplyLayer vs Proton Safe MCP
ReplyLayer is an MCP server published by replylayer.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Proton Safe MCP is an MCP server published by fbossiere. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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 |  ReplyLayer |  Proton Safe MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.15.1 Downloads/month (npm): 1 934 Downloads/week (npm): 97 Not marked · First seen |
Listed Version: 2.3.1 Downloads/month (PyPI): 1 085 Downloads/week (PyPI): 63 Forks (GitHub): 0 Stars (GitHub): 6 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 | ReplyLayer | Proton Safe MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 6 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (api.replylayer.ai/v1/mcp) | On your machine (proton-safe-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 4 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/fbossiere/proton-safe-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago, requires a key | no remote endpoint we check |
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
ReplyLayer
Safe email for AI agents: a mailbox with inbound scanning, outbound checks and human review.
Proton Safe MCP
Read Proton Mail, extract bounded attachment text, and create explicitly confirmed drafts.
How to run each
ReplyLayer As a remote MCP server
claude mcp add --transport http replylayer https://api.replylayer.ai/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: REPLYLAYER_API_KEY (secret), Authorization header
Proton Safe MCP As a local MCP server: PyPI package
claude mcp add --env "PROTON_BRIDGE_USER=<YOUR_PROTON_BRIDGE_USER>" --transport stdio proton-safe-mcp -- uvx proton-safe-mcp serveRequires: PROTON_BRIDGE_USER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ReplyLayer has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only ReplyLayer asks for
REPLYLAYER_API_KEY (secret)
Only Proton Safe MCP asks for
PROTON_BRIDGE_USERPROTON_IMAP_PORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: ReplyLayer · What it can do: Proton Safe MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.