Aperion Shield vs MCP Security Guard
Aperion Shield is an MCP server published by AperionAI. Marketplaces we read that list it: 1 (Official MCP Registry). MCP Security Guard is an MCP server published by petrovicistefan. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-22. 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 |  Aperion Shield |  MCP Security Guard |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 1 Stars (GitHub): 11 Not marked · First seen |
Listed Version: 0.9.1 Downloads/month (npm): 718 Downloads/week (npm): 659 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.9.1 Downloads/month (npm): 718 Downloads/week (npm): 659 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 | Aperion Shield | MCP Security Guard |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 11 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | On your machine (ghcr.io/aperionai/shield:shield-v1.0.1) | On your machine (mcp-security-guard) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/aperionai/shield | github.com/petrovicistefan/mcp-security-guard |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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
Aperion Shield
Local guardrail proxy that blocks destructive MCP tool calls, rug pulls, and tool poisoning
MCP Security Guard
Audit MCP servers for tool poisoning, rug pulls and supply-chain risk (OWASP MCP Top 10).
How to run each
Aperion Shield As a local MCP server: Docker image
claude mcp add --transport stdio shield -- docker run -i --rm ghcr.io/aperionai/shield:shield-v1.0.1MCP Security Guard As a local MCP server: npm package
claude mcp add --transport stdio mcp-security-guard -- npx -y mcp-security-guardCommands 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: Aperion Shield · What it can do: MCP Security Guard · Compare two other plugins
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.