MCP stdio ShellGuard
NPM · MCP-STDIO-SHELLGUARD
Defense-in-depth for MCP stdio servers: shell-injection guard, AST audit CLI, RCE blocking.
Available components
Last scanned (10 hours ago)
Scores higher than 42% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security94
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via @typescript-eslint/typescript-estree > minimatch. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 130 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 518 tokens (~64/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management68
- Stability check failed: the tool surface changed between 0.1.2 and 0.1.3: 0 tool removals, 2 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 88 to 64.
- 1 Nov 26 +2
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- CVE-2023-54404 no longer affects this package ▲ security
- Known CVEs: CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via @typescript-eslint/typescript-estree > minimatch. A fixed version is available. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.1.2 → 0.1.3 functional
- 31 Oct 26 0
- CVE-2026-118764 affects this package: high ▼ security
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: partial → fail ▼ security
- CVE-2026-93687 no longer affects this package ▲ security
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/mcp-stdio-shellguard@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 130 packages
| Packages resolved | 130 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_report ~38
Format an AuditScanResult as markdown / json / sarif. Pure pass-through transformer.
| Name | Type | Req | Description |
|---|---|---|---|
| findings | – | – | – |
| format | string | yes | – |
No output schema declared.
No examples provided.
audit_source ~69
Scan a TypeScript / JavaScript path for unsanitised child_process.exec / spawn / execFile calls and other shell-injection anti-patterns. Returns AuditFinding[] + summary.
| Name | Type | Req | Description |
|---|---|---|---|
| ignoreGlobs | array | – | – |
| path | string | yes | – |
| severityFloor | string | – | – |
No output schema declared.
No examples provided.
guard_exec ~93
Defended replacement for child_process.exec. Forces an args[] vector, runs through allowlist + sandbox + replay window. Returns stdout/stderr/exitCode.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | – |
| blockOnReplay | boolean | – | – |
| command | string | yes | – |
| cwd | string | – | – |
| env | object | – | – |
| timeoutMs | integer | – | – |
| toolName | string | yes | – |
No output schema declared.
No examples provided.
guard_spawn ~85
Defended replacement for child_process.spawn. Returns stdout/stderr SHA-256 hashes instead of full bodies. Rejects shell:true.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | – |
| cwd | string | – | – |
| env | object | – | – |
| fdBudget | integer | – | – |
| file | string | yes | – |
| shell | boolean | – | – |
| toolName | string | yes | – |
No output schema declared.
No examples provided.
register_allowlist ~78
Register a tool name with its allowed executable + args regex patterns. Without registration the default-deny applies and guard_exec/guard_spawn refuse to run.
| Name | Type | Req | Description |
|---|---|---|---|
| argsPatterns | array | yes | – |
| cwdPattern | string | – | – |
| executable | string | yes | – |
| sandboxProfile | string | – | – |
| toolName | string | yes | – |
No output schema declared.
No examples provided.
replay_check ~68
Compute the canonical SHA-256 hash for an invocation and report whether the same hash is already in the LRU sliding window.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | – |
| cwd | string | – | – |
| env | object | – | – |
| executable | string | yes | – |
| record | boolean | – | – |
No output schema declared.
No examples provided.
sandbox_status ~45
Report the active sandbox profile + concrete limits (timeout, byte caps, fd budget, cgroup-v2 active flag) for a registered tool.
| Name | Type | Req | Description |
|---|---|---|---|
| toolName | string | – | – |
No output schema declared.
No examples provided.
trust_tier ~42
Derive the LOW / MEDIUM / HIGH / CRITICAL trust tier for a registered tool plus improvement hints to lift it.
| Name | Type | Req | Description |
|---|---|---|---|
| toolName | string | yes | – |
No output schema declared.
No examples provided.
How do I install the MCP stdio ShellGuard server?
MCP stdio ShellGuard runs locally as an npm package, launched with npx -y mcp-stdio-shellguard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-stdio-shellguard
claude mcp add io-studiomeyer-stdio-shellguard -- npx -y mcp-stdio-shellguard
What is the MCP stdio ShellGuard server?
MCP stdio ShellGuard is listed in the public MCP registry as io.studiomeyer/stdio-shellguard. Defense-in-depth for MCP stdio servers: shell-injection guard, AST audit CLI, RCE blocking. This page covers its npm package (mcp-stdio-shellguard).
Is the MCP stdio ShellGuard server safe to use?
MCP stdio ShellGuard scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP stdio ShellGuard server expose?
MCP stdio ShellGuard exposes 8 tools: guard_exec, guard_spawn, register_allowlist, audit_source, audit_report, and 3 more. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.
Is the MCP stdio ShellGuard server still maintained?
MCP stdio ShellGuard is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP stdio ShellGuard server under?
MCP stdio ShellGuard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.