protect-mcp vs writ
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). writ is an MCP server published by AvenueDAdmin. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  writ |
|---|---|---|
| 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: 0.1.2 Downloads/month (PyPI): 488 Downloads/week (PyPI): 39 Forks (GitHub): 0 Stars (GitHub): 2 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 | writ |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (writ-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 2 |
| 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/avenuedadmin/pywrit |
| 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.
writ
Commit-time policy checks for AI agent writes (ALLOW/DENY/STEP_UP) with a tamper-evident audit log.
How to run each
protect-mcp As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install protect-mcp@claude-communitywrit As a local MCP server: PyPI package
claude mcp add --env "WRIT_API_KEY=<YOUR_WRIT_API_KEY>" --env "WRIT_SPONSOR_TOKEN=<YOUR_WRIT_SPONSOR_TOKEN>" --transport stdio writ -- uvx writ-mcpRequires: WRIT_API_KEY (secret), WRIT_SPONSOR_TOKEN (secret)
Commands 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
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: writ · 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.