protect-mcp vs Palisade
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). Palisade is an MCP server published by palisade.email. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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 |   Palisade |
|---|---|---|
| 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.0.6 Downloads/month (npm): 96 054 Downloads/week (npm): 6 366 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.2.1 Downloads/month (npm): 96 054 Downloads/week (npm): 6 366 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 | Palisade |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| 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 | MIT | MIT |
| Repository (differs) | github.com/tomjwxf/protect-mcp-plugin | github.com/palisadeemail/palisade-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-25 |
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.
Palisade
Monitor and manage email authentication (SPF, DKIM, DMARC, MTA-STS, BIMI) for your domains.
How to run each
protect-mcp As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install protect-mcp@claude-communityPalisade As a remote MCP server
claude mcp add --transport http palisade https://api.palisade.email/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Palisade 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
Neither one's marketplaces publish the settings it asks for.
What it can do: protect-mcp · What it can do: Palisade · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.