Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/studiomeyer-io/mcp-stdio-shellguardWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/studiomeyer-io/mcp-stdio-shellguard/stdio-shellguard)<a href="https://agentmods.dev/mcp/studiomeyer-io/mcp-stdio-shellguard/stdio-shellguard"><img src="https://agentmods.dev/badge/mcp/studiomeyer-io/mcp-stdio-shellguard/stdio-shellguard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/studiomeyer-io/mcp-stdio-shellguard/stdio-shellguard"><img src="https://agentmods.dev/badge/mcp/studiomeyer-io/mcp-stdio-shellguard/stdio-shellguard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stdio-shellguard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"stdio-shellguard": {
"command": "npx",
"args": [
"-y",
"mcp-stdio-shellguard"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 10 lines scan A 8bc0a9dd7ffd
stdio-shellguard is an MCP server published in the GitHub repository studiomeyer-io/mcp-stdio-shellguard (0 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
armor
MCP server "armor" as configured in studiomeyer-io/mcp-armor. Runs in Docker (ghcr.io/studiomeyer-io/mcp-armor:0.8.1).
tenant-pair
Multi-user tenancy library for MCP servers. Pairs, groups, bi-temporal shared state, DSGVO erasure. Runs locally from the mcp-tenant-pair-demo npm package.
mcp-fortress
MCP server "mcp-fortress", hosted remotely at server.smithery.ai, as configured in mcp-fortress/mcp-fortress.
godot-mcp
MCP server for full Godot 4.x engine control with 165 tools for AI-driven game development. Runs locally from the @tugcantopaloglu/godot-mcp npm package.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
claude-octopus
Spawn multiple specialized Claude Code agents as MCP servers, each independently configured. Runs locally from the claude-octopus npm package. Needs 7 environment variables to run.