Ext Ops Panel
Open dashboard
Comparison

protect-mcp vs Attest

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). Attest is an MCP server published by dev-prathap. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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

Where each is published
Marketplaceprotect-mcpAttest
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.0
Downloads/month (PyPI): 206
Downloads/week (PyPI): 22
Forks (GitHub): 0
Stars (GitHub): 1
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

protect-mcp vs Attest
Factprotect-mcpAttest
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (attestlayer)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published11, secrets among them: 7
Hooks it runs (differs)1Not published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/tomjwxf/protect-mcp-plugingithub.com/dev-prathap/attest
Changes in the last 7 days00
First seen2026-10-112026-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

In its own words, on Claude Code: claude-plugins-community:

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.

Attest

In its own words, on Official MCP Registry:

Decide by policy, gate behind a human, verify by read-back, record a hash-chained ledger.

How to run each

protect-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install protect-mcp@claude-community

Attest As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GMAIL_TOKEN=<YOUR_GMAIL_TOKEN>" --env "GOOGLE_TOKEN=<YOUR_GOOGLE_TOKEN>" --env "GRAPH_TOKEN=<YOUR_GRAPH_TOKEN>" --env "HUBSPOT_TOKEN=<YOUR_HUBSPOT_TOKEN>" --env "LINEAR_API_KEY=<YOUR_LINEAR_API_KEY>" --env "NOTION_TOKEN=<YOUR_NOTION_TOKEN>" --env "SLACK_BOT_TOKEN=<YOUR_SLACK_BOT_TOKEN>" --transport stdio attest -- uvx attestlayer

Requires: GMAIL_TOKEN (secret), GOOGLE_TOKEN (secret), GRAPH_TOKEN (secret), HUBSPOT_TOKEN (secret), LINEAR_API_KEY (secret), NOTION_TOKEN (secret), SLACK_BOT_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: Attest · 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.

Where the data comes from: how the catalog is built