protect-mcp vs Proof Holdings
protect-mcp is a plugin bundle for AI coding tools published by tomjwxf. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Proof Holdings is an MCP server published by proof.holdings. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  protect-mcp |   Proof Holdings |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.7.1 Downloads/month (npm): 739 Downloads/week (npm): 422 Forks (GitHub): 0 Stars (GitHub): 0 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 | protect-mcp | Proof Holdings |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-26 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.proof.holdings/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/tomjwxf/protect-mcp-plugin | github.com/proofholdings/mcp-server |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days 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
protect-mcp
MCP security gateway that wraps any MCP server with per-tool policies, Ed25519-signed decision receipts, and human approval gates. Shadow mode (default) logs every tool call without blocking. Enforce mode applies per-tool allow/deny/rate-limit/approval policies. Every decision is cryptographically signed and independently verifiable offline. MIT licensed. IETF Internet-Draft published for the receipts protocol.
Proof Holdings
One API, all things verified — control, delegation, human approval, anti-impersonation.
How to run each
protect-mcp As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install protect-mcp@claude-communityProof Holdings As a remote MCP server
claude mcp add --transport http proof-holdings https://api.proof.holdings/mcpRequires: PROOF_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Proof Holdings has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of protect-mcp nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of protect-mcp publish no settings it asks for, so we do not compare settings.
What it can do: protect-mcp · What it can do: Proof Holdings · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.