io.github.AperionAI/shield
Aperion Shield
Is the Aperion Shield MCP server down? No. It is up and needs args, probed 2026-10-29.
Local guardrail proxy that blocks destructive MCP tool calls, rug pulls, and tool poisoning
needs args probed 2026-11-14 · unchanged since 2026-10-29
MCP error -32000: Connection closed Error: no upstream MCP server given. Usage: aperion-shield [--rules PATH] [--shadow] -- <upstream-mcp> [args...] (std
- Run it
- docker run -i --rm ghcr.io/aperionai/shield:shield-v1.0.1 (stdio, probed in a container with the network off)
- Host
- ghcr.io
- Repository
- https://github.com/AperionAI/shield
- Website
- https://docs.aperion.ai/aperion-shield.html
- Registry
- active, updated 2026-06-11 · registry entry
Compare this server with others.
More servers
Other registry entries on ghcr.io, the ones next to this name; all of them.
- Data Prism io.github.AindriuB/data-prism · not probed
- ImmunoGraph MCP io.github.Ajey95/immunograph · alive
- App Console: Google Play, App Store Connect, AdMob io.github.Alekla0126/app-console-mcp · alive
- A2H: ask a human io.github.AndreaAcanfora/a2h-gateway · needs env
- Applire io.github.Applire/applire · needs env
- Nahuali io.github.Arakiss/nahuali · alive
- yt io.github.ArasanDev/yt · alive
- Flutter MCP Toolkit io.github.Arenukvern/flutter-mcp-toolkit · alive
Servers that mention shield.
- app.decibelshield/decibel-shield · alive
- app.vercel.triageshield/triageshield · alive
- com.clauxel.tracepiishield/tracepiishield-mcp · no DNS
- com.craftedtrust/mcp-shield · alive
- com.edgethirteen.www/triageshield · not found
- MandateShield AI Payment Evidence com.mandateshield/payment-authority · alive
- dev.horizonshield/horizon-shield · alive
- Execute adversarial-prompt-shield-mcp io.github.Evozim/adversarial-prompt-shield-mcp · paid (402)
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server needs command line arguments that the registry entry does not list. Add them to the package arguments in the registry entry.