Is MCP stdio ShellGuard MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highShell command built from a string (injection risk)
How MCP stdio ShellGuard compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 60/100
- higher than 15% of 48,243 servers
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 7 read · 1 create
Release history: 2 versions in the registry since 2026-08-19, latest 2026-11-01, typically one every 74 days.
Public scan report
scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it
1 high1 medium
- Code scan36 source files scanned8/25
- –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 1 days ago15/15
- Maintainer identitynamespace and repository owner differ4/10
Findings (2)
- highShell command built from a string (injection risk)
exec.shell-concatdist/audit/bindings.js: …import cp from "node:child_process"; cp.exec(`ls ${x}`)` * via a default/namespace im… - mediumeval / new Function used
exec.evaldist/audit/patterns.js: … severity: "CRITICAL", label: "eval(...)", test: ({ callee }) => cal…
Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON