# io.github.IronSecCo/ironclaw (oci · ghcr.io/ironsecco/ironclaw-mcp:v0.1.530) Sandboxed shell exec for MCP clients: run untrusted agent commands in a gVisor container. - Trust score: 36/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-21 ## Components - oci · `ghcr.io/ironsecco/ironclaw-mcp:v0.1.530`: 36/100 (this document), [markdown](https://verifymcp.io/servers/ironsecco-ironclaw/ghcr-io-ironsecco-ironclaw-mcp-v0-1-530.md), [page](https://verifymcp.io/servers/ironsecco-ironclaw/ghcr-io-ironsecco-ironclaw-mcp-v0-1-530) ## Channel facts - Registry: `oci` - Package: `ghcr.io/ironsecco/ironclaw-mcp:v0.1.530` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-21. - **Supply Chain Security**: 0/100 - Malware scan not yet available for this package. - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it. - **Provenance & Transparency**: 35/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - License check failed: no license is declared. - Actively maintained (last published 1 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 83/100 - AI-judged instruction clarity (excellent). - Tool/resource definitions use about 197 tokens (~197/item across 1 items; 1 tools + 0 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 75/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "sandbox_exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 40/100 - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. **Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the io.github.IronSecCo/ironclaw MCP server? io.github.IronSecCo/ironclaw runs locally as a container image, launched with docker run --rm -i ghcr.io/ironsecco/ironclaw-mcp:v0.1.530. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add ironsecco-ironclaw -- docker run --rm -i ghcr.io/ironsecco/ironclaw-mcp:v0.1.530 ``` ### Cursor ```json { "mcpServers": { "ironsecco-ironclaw": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/ironsecco/ironclaw-mcp:v0.1.530" ] } } } ``` ### VS Code ```json { "servers": { "ironsecco-ironclaw": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/ironsecco/ironclaw-mcp:v0.1.530" ] } } } ``` ### Codex ```bash codex mcp add ironsecco-ironclaw -- docker run --rm -i ghcr.io/ironsecco/ironclaw-mcp:v0.1.530 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "ironsecco-ironclaw": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/ironsecco/ironclaw-mcp:v0.1.530" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: ironsecco-ironclaw: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/ironsecco/ironclaw-mcp:v0.1.530"] ``` ### Netclaw ```json { "McpServers": { "ironsecco-ironclaw": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/ironsecco/ironclaw-mcp:v0.1.530" ] } } } ``` ### Other ```json { "mcpServers": { "ironsecco-ironclaw": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/ironsecco/ironclaw-mcp:v0.1.530" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-19 (score 36) First indexed and scored. ## MCP tools (1) ### `sandbox_exec` (~197 tokens) Run a shell command (or code snippet via `sh -c`) inside an ephemeral, hardened IronClaw sandbox box and return its stdout, stderr, exit code, and containment status. By default the box runs under gVisor (runsc), which intercepts syscalls in a user-space guest kernel; it has NO network (egress is impossible), drops all Linux capabilities, runs as a non-root user with a read-only root filesystem, no-new-privileges, a restrictive seccomp profile, and is bounded by cpu/memory/pids caps. It is torn down after the command completes. Use this to execute untrusted or model-generated code safely. Input parameters: - `command` (string, required): Command to run inside the sandbox, executed via sh -c. - `image` (string): Optional container image override (default: the server's configured image). - `timeout_seconds` (integer): Optional per-exec timeout override in seconds. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ironsecco-ironclaw/ghcr-io-ironsecco-ironclaw-mcp-v0-1-530#diagnostics ## Score history - 2026-09-21: 36 - 2026-09-20: 36 - 2026-09-19: 36 ## Common questions ### What is the io.github.IronSecCo/ironclaw MCP server? io.github.IronSecCo/ironclaw is an MCP server listed in the public MCP registry as io.github.IronSecCo/ironclaw. Sandboxed shell exec for MCP clients: run untrusted agent commands in a gVisor container. This page covers its container image (ghcr.io/ironsecco/ironclaw-mcp:v0.1.530). ### Is the io.github.IronSecCo/ironclaw MCP server safe to use? io.github.IronSecCo/ironclaw scores 36 out of 100 on VerifyMCP. 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 io.github.IronSecCo/ironclaw MCP server expose? io.github.IronSecCo/ironclaw exposes 1 tool: sandbox_exec. Their descriptions and schemas cost roughly 197 tokens of context every time the server is loaded. ### Is the io.github.IronSecCo/ironclaw MCP server still maintained? io.github.IronSecCo/ironclaw is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Repository: https://github.com/IronSecCo/ironclaw - Website: https://ironclaw.sh/ - Changelog RSS feed: https://verifymcp.io/servers/ironsecco-ironclaw/ghcr-io-ironsecco-ironclaw-mcp-v0-1-530.xml - Changelog JSON feed: https://verifymcp.io/servers/ironsecco-ironclaw/ghcr-io-ironsecco-ironclaw-mcp-v0-1-530.json - HTML version of this page: https://verifymcp.io/servers/ironsecco-ironclaw/ghcr-io-ironsecco-ironclaw-mcp-v0-1-530