Aperion Shield MCP server
io.github.AperionAI/shield·v1.0.1·11 starsLocal guardrail proxy that blocks destructive MCP tool calls, rug pulls, and tool poisoning
11 stars
Reviews
Write oneNobody has reviewed Aperion Shield yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Aperion Shield tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 5 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Aperion Shield compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
- GitHub stars
- 11
- more than 88% of 28,688 servers
Install Aperion Shield in Claude Code, Cursor or VS Code
claude mcp add shield -- docker run -i --rm ghcr.io/aperionai/shield:shield-v1.0.1
What the publisher says
From the Aperion Shield repository's README, as published. We do not edit it. Read it on GitHub
aperion-shield — local MCP guardrail for AI coding agents
Works with:
### ⭐ Star this repo if you think AI agents shouldn't touch prod unsupervised
aperion-shield is the free reference implementation of consequence-level control for AI coding agents — the layer that stops a destructive tools/call before it lands, not a log you read after the damage is done. It's transparent insurance: you don't notice it until the day it saves you.
If that's a problem you take seriously, a ⭐ is the fastest way to help other engineers in regulated and high-stakes shops find it before they need it → Star aperion-shield on GitHub
aperion-shield is a tiny, local MCP guardrail that sits between your AI coding agent (Cursor, Claude Code, …) and the real MCP servers your agent talks to (postgres, github, shell, filesystem, …) — local stdio servers and, since v0.9, remote Streamable HTTP ones. On every tools/call it evaluates 65+ adaptive safety rules (plus an optional 40-rule community pack) across destructive surfaces — SQL, git, filesystem, secrets exfiltration, supply-chain RCE, reverse shells, sudo / privilege escalation, cloud (AWS/GCP/Azure), Kubernetes, Docker, IAM / cloud privilege escalation, anti-forensics (audit & log tampering), NoSQL / cache / search (Mongo, Redis, Elasticsearch, Cassandra), disabling host security controls, and Windows / PowerShell — and either blocks the call, prompts you for approval, or lets it through with a warning banner. And since v0.9 it watches the other direction too: tool catalogs are TOFU-pinned against rug pulls, descriptions are scanned for tool poisoning, and tool results are scanned for prompt injection. v1.0 completes the story before install and below the protocol: --scan audits an MCP server before you ever wire it in, and --sandbox confines the server process at the OS level. And since v1.4, reversible secret cloaking lets your agent reference a real credential as a {{cloak:NAME}} placeholder — the secret is substituted in only on the frame Shield forwards upstream and scrubbed back out of any result, so it never enters the model's context, transcript, or prompt cache. v1.5 adds the seam the August 2026 market actually demos: native Cursor / Claude Code PreToolUse hooks (fail-closed), --scan-ide for TrustFall project MCP + Skills, and curl -fsSL https://shield-get.aperion.ai | sh.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Aperion Shield: common questions
- Is Aperion Shield MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Aperion Shield safety report
- How do I install Aperion Shield?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Aperion Shield need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Aperion Shield maintained?
- The last commit was 43 days ago (2026-09-22). The latest release is v1.0.1.
- What can I use instead of Aperion Shield?
- Servers from other publishers that do the same job: node9 MCP server.
- How does Aperion Shield compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,255 servers); github stars 11 (more than 88% of 28,688 servers). Full comparison.
Alternatives to Aperion Shield
Same job from other publishers: the closest match first, then the best rated.
- node9Access control for AI agents and MCP servers: allow, hold for approval, or block each tool callnot reviewedEstablishedA
