protect-mcp vs node9
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). node9 is an MCP server published by node9-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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 | ||
|---|---|---|
| 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: 2.26.2 Forks (GitHub): 21 Stars (GitHub): 220 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 | node9 |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 220 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 21 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (node9-ai) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| 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/node9-ai/node9-proxy |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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.
node9
Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call
How to run each
protect-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
node9 As a local MCP server: npm package
claude mcp add --transport stdio node9 -- npx -y node9-aiCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: protect-mcp · What it can do: node9 · 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.