Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.IronSecCo/ironclaw

OCI · GHCR.IO/IRONSECCO/IRONCLAW-MCP

Sandboxed shell exec for MCP clients: run untrusted agent commands in a gVisor container.

Available components

oci · ghcr.io/ironsecco/ironclaw-mcp 56
+4 this week 56 Trust /100

Last scanned (1 hour ago)

Scores higher than 96% of OCI servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • CVE check failed: a known advisory affects this package; its severity couldn't be graded. See how to fix → View diagnostics → Fail
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency87
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to IronSecCo/ironclaw). View diagnostics → Pass
  • License check failed: no license is declared. See how to fix → Fail
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 197 tokens (~197/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 18 Oct 26 +1
    • CVE-2026-32288 affects this package: none ▼ security
    • CVE-2026-94439 affects this package: none ▼ security
    • CVE-2026-42505 affects this package: none ▼ security
    • CVE-2026-25679 affects this package: none ▼ security
    • CVE-2026-42507 affects this package: none ▼ security
    • CVE-2026-78663 affects this package: none ▼ security
    • CVE-2026-33811 affects this package: none ▼ security
    • CVE-2025-61726 affects this package: none ▼ security
    • CVE-2025-58189 affects this package: none ▼ security
    • CVE-2026-56859 affects this package: none ▼ security
    • CVE-2026-39825 affects this package: none ▼ security
    • CVE-2026-33814 affects this package: none ▼ security
    • CVE-2026-39822 affects this package: none ▼ security
    • CVE-2025-68121 affects this package: none ▼ security
    • CVE-2025-58183 affects this package: none ▼ security
    • CVE-2025-58188 affects this package: none ▼ security
    • CVE-2025-58186 affects this package: none ▼ security
    • CVE-2026-42499 affects this package: none ▼ security
    • CVE-2026-39820 affects this package: none ▼ security
    • CVE-2026-78667 affects this package: none ▼ security
    • CVE-2026-97032 affects this package: none ▼ security
    • CVE-2026-97031 affects this package: none ▼ security
    • CVE-2026-56857 affects this package: none ▼ security
    • CVE-2026-42504 affects this package: none ▼ security
    • CVE-2026-56858 affects this package: none ▼ security
    • CVE-2026-32289 affects this package: none ▼ security
    • CVE-2025-61725 affects this package: none ▼ security
    • CVE-2026-27139 affects this package: none ▼ security
    • CVE-2026-39826 affects this package: none ▼ security
    • CVE-2026-78669 affects this package: none ▼ security
    • CVE-2026-56866 affects this package: none ▼ security
    • CVE-2026-32283 affects this package: none ▼ security
    • CVE-2026-39821 affects this package: none ▼ security
    • CVE-2026-94440 affects this package: none ▼ security
    • CVE-2026-32280 affects this package: none ▼ security
    • CVE-2025-58187 affects this package: none ▼ security
    • CVE-2026-56853 affects this package: none ▼ security
    • CVE-2026-27145 affects this package: none ▼ security
    • CVE-2026-56860 affects this package: none ▼ security
    • CVE-2026-56862 affects this package: none ▼ security
    • CVE-2026-27142 affects this package: none ▼ security
    • CVE-2026-32282 affects this package: none ▼ security
    • CVE-2026-94448 affects this package: none ▼ security
    • CVE-2026-39823 affects this package: none ▼ security
    • CVE-2026-33818 affects this package: none ▼ security
    • CVE-2025-61723 affects this package: none ▼ security
    • CVE-2026-97030 affects this package: none ▼ security
    • CVE-2025-47912 affects this package: none ▼ security
    • CVE-2025-61724 affects this package: none ▼ security
    • CVE-2025-58185 affects this package: none ▼ security
    • CVE-2025-61727 affects this package: none ▼ security
    • CVE-2026-78660 affects this package: none ▼ security
    • CVE-2025-61730 affects this package: none ▼ security
    • CVE-2026-32281 affects this package: none ▼ security
    • CVE-2026-78659 affects this package: none ▼ security
    • CVE-2026-39836 affects this package: none ▼ security
    • CVE-2025-61729 affects this package: none ▼ security
    • CVE-2025-61728 affects this package: none ▼ security
  • 17 Oct 26 0
    • CVE-2025-61728 affects this package: none ▼ security
    • CVE-2025-61729 affects this package: none ▼ security
    • CVE-2026-39836 affects this package: none ▼ security
    • CVE-2025-61727 affects this package: none ▼ security
    • CVE-2026-78660 affects this package: none ▼ security
    • CVE-2025-61730 affects this package: none ▼ security
    • CVE-2026-32281 affects this package: none ▼ security
    • CVE-2026-94439 affects this package: none ▼ security
    • CVE-2026-42505 affects this package: none ▼ security
    • CVE-2026-25679 affects this package: none ▼ security
    • CVE-2026-42507 affects this package: none ▼ security
    • CVE-2026-78663 affects this package: none ▼ security
    • CVE-2026-33811 affects this package: none ▼ security
    • CVE-2025-61726 affects this package: none ▼ security
    • CVE-2025-58189 affects this package: none ▼ security
    • CVE-2026-56859 affects this package: none ▼ security
    • CVE-2026-39825 affects this package: none ▼ security
    • CVE-2026-33814 affects this package: none ▼ security
    • CVE-2026-39822 affects this package: none ▼ security
    • CVE-2025-68121 affects this package: none ▼ security
    • CVE-2025-58183 affects this package: none ▼ security
    • CVE-2025-58188 affects this package: none ▼ security
    • CVE-2025-58186 affects this package: none ▼ security
    • CVE-2026-42499 affects this package: none ▼ security
    • CVE-2026-39820 affects this package: none ▼ security
    • CVE-2026-78667 affects this package: none ▼ security
    • CVE-2026-97032 affects this package: none ▼ security
    • CVE-2026-78659 affects this package: none ▼ security
    • CVE-2026-97031 affects this package: none ▼ security
    • CVE-2026-56857 affects this package: none ▼ security
    • CVE-2026-42504 affects this package: none ▼ security
    • CVE-2026-56858 affects this package: none ▼ security
    • CVE-2026-32288 affects this package: none ▼ security
    • CVE-2026-32289 affects this package: none ▼ security
    • CVE-2025-61725 affects this package: none ▼ security
    • CVE-2026-27139 affects this package: none ▼ security
    • CVE-2026-39826 affects this package: none ▼ security
    • CVE-2026-78669 affects this package: none ▼ security
    • CVE-2026-56866 affects this package: none ▼ security
    • CVE-2026-32283 affects this package: none ▼ security
    • CVE-2026-39821 affects this package: none ▼ security
    • CVE-2026-94440 affects this package: none ▼ security
    • CVE-2026-32280 affects this package: none ▼ security
    • CVE-2025-58187 affects this package: none ▼ security
    • CVE-2026-56853 affects this package: none ▼ security
    • CVE-2026-27145 affects this package: none ▼ security
    • CVE-2026-56860 affects this package: none ▼ security
    • CVE-2026-56862 affects this package: none ▼ security
    • CVE-2026-27142 affects this package: none ▼ security
    • CVE-2026-32282 affects this package: none ▼ security
    • CVE-2026-94448 affects this package: none ▼ security
    • CVE-2026-39823 affects this package: none ▼ security
    • CVE-2026-33818 affects this package: none ▼ security
    • CVE-2025-61723 affects this package: none ▼ security
    • CVE-2026-97030 affects this package: none ▼ security
    • CVE-2025-47912 affects this package: none ▼ security
    • CVE-2025-61724 affects this package: none ▼ security
    • CVE-2025-58185 affects this package: none ▼ security
  • 16 Oct 26 +1
    • CVE-2026-39836 affects this package: none ▼ security
    • CVE-2026-94439 affects this package: none ▼ security
    • CVE-2026-42505 affects this package: none ▼ security
    • CVE-2026-25679 affects this package: none ▼ security
    • CVE-2026-42507 affects this package: none ▼ security
    • CVE-2026-78663 affects this package: none ▼ security
    • CVE-2026-33811 affects this package: none ▼ security
    • CVE-2025-61726 affects this package: none ▼ security
    • CVE-2025-58189 affects this package: none ▼ security
    • CVE-2026-56859 affects this package: none ▼ security
    • CVE-2026-39825 affects this package: none ▼ security
    • CVE-2026-33814 affects this package: none ▼ security
    • CVE-2026-39822 affects this package: none ▼ security
    • CVE-2025-68121 affects this package: none ▼ security
    • CVE-2025-58183 affects this package: none ▼ security
    • CVE-2025-58188 affects this package: none ▼ security
    • CVE-2025-58186 affects this package: none ▼ security
    • CVE-2026-42499 affects this package: none ▼ security
    • CVE-2026-39820 affects this package: none ▼ security
    • CVE-2026-78667 affects this package: none ▼ security
    • CVE-2026-97032 affects this package: none ▼ security
    • CVE-2026-97031 affects this package: none ▼ security
    • CVE-2026-56857 affects this package: none ▼ security
    • CVE-2026-42504 affects this package: none ▼ security
    • CVE-2026-56858 affects this package: none ▼ security
    • CVE-2026-32288 affects this package: none ▼ security
    • CVE-2026-32289 affects this package: none ▼ security
    • CVE-2025-61725 affects this package: none ▼ security
    • CVE-2026-27139 affects this package: none ▼ security
    • CVE-2026-39826 affects this package: none ▼ security
    • CVE-2026-78669 affects this package: none ▼ security
    • CVE-2026-56866 affects this package: none ▼ security
    • CVE-2026-32283 affects this package: none ▼ security
    • CVE-2026-39821 affects this package: none ▼ security
    • CVE-2026-94440 affects this package: none ▼ security
    • CVE-2026-32280 affects this package: none ▼ security
    • CVE-2025-58187 affects this package: none ▼ security
    • CVE-2026-56853 affects this package: none ▼ security
    • CVE-2026-27145 affects this package: none ▼ security
    • CVE-2026-56860 affects this package: none ▼ security
    • CVE-2026-56862 affects this package: none ▼ security
    • CVE-2026-27142 affects this package: none ▼ security
    • CVE-2026-32282 affects this package: none ▼ security
    • CVE-2026-94448 affects this package: none ▼ security
    • CVE-2026-39823 affects this package: none ▼ security
    • CVE-2026-33818 affects this package: none ▼ security
    • CVE-2025-61723 affects this package: none ▼ security
    • CVE-2026-97030 affects this package: none ▼ security
    • CVE-2025-47912 affects this package: none ▼ security
    • CVE-2025-61724 affects this package: none ▼ security
    • CVE-2025-58185 affects this package: none ▼ security
    • CVE-2025-61727 affects this package: none ▼ security
    • CVE-2026-78660 affects this package: none ▼ security
    • CVE-2025-61730 affects this package: none ▼ security
    • CVE-2026-32281 affects this package: none ▼ security
    • CVE-2026-78659 affects this package: none ▼ security
    • CVE-2025-61729 affects this package: none ▼ security
    • CVE-2025-61728 affects this package: none ▼ security
  • 15 Oct 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2025-61726 affects this package: none ▼ security
    • CVE-2026-42507 affects this package: none ▼ security
    • CVE-2026-78663 affects this package: none ▼ security
    • CVE-2026-33811 affects this package: none ▼ security
    • CVE-2025-58189 affects this package: none ▼ security
    • CVE-2026-56859 affects this package: none ▼ security
    • CVE-2026-39825 affects this package: none ▼ security
    • CVE-2026-33814 affects this package: none ▼ security
    • CVE-2026-39822 affects this package: none ▼ security
    • CVE-2025-68121 affects this package: none ▼ security
    • CVE-2025-58183 affects this package: none ▼ security
    • CVE-2025-58188 affects this package: none ▼ security
    • CVE-2025-58186 affects this package: none ▼ security
    • CVE-2026-42499 affects this package: none ▼ security
    • CVE-2026-39820 affects this package: none ▼ security
    • CVE-2026-78667 affects this package: none ▼ security
    • CVE-2026-97032 affects this package: none ▼ security
    • CVE-2026-97031 affects this package: none ▼ security
    • CVE-2026-56857 affects this package: none ▼ security
    • CVE-2026-42504 affects this package: none ▼ security
    • CVE-2026-56858 affects this package: none ▼ security
    • CVE-2026-94439 affects this package: none ▼ security
    • CVE-2026-42505 affects this package: none ▼ security
    • CVE-2026-25679 affects this package: none ▼ security
  • 14 Oct 26 +37

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 12 Oct 26 −35

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 10 Oct 26 +6

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 28 Sept 26 46

    First indexed and scored.

Diagnostics

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 18 Oct 2026 · Analysed oci/ghcr.io/ironsecco/ironclaw-mcp@v0.1.547

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem oci
Reason Verified
Discovered via OCI referrers API
Source repo IronSecCo/ironclaw
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/IronSecCo/ironclaw/.github/workflows/image.yml@refs/heads/main
Rekor log index 3244852214
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:1f6d6479e80849386a1d35a0b4fc6115e9f47379c3db0301d519835ac2e86de5

Background: How many MCP packages publish verified provenance →

Vulnerabilities 58 findings
ID CVE Severity Vector Fix available
GO-2025-4006 CVE-2025-61725 none yes
GO-2025-4007 CVE-2025-58187 none yes
GO-2025-4008 CVE-2025-58189 none yes
GO-2025-4009 CVE-2025-61723 none yes
GO-2025-4010 CVE-2025-47912 none yes
GO-2025-4011 CVE-2025-58185 none yes
GO-2025-4012 CVE-2025-58186 none yes
GO-2025-4013 CVE-2025-58188 none yes
GO-2025-4014 CVE-2025-58183 none yes
GO-2025-4015 CVE-2025-61724 none yes
GO-2025-4155 CVE-2025-61729 none yes
GO-2025-4175 CVE-2025-61727 none yes
GO-2026-4337 CVE-2025-68121 none yes
GO-2026-4340 CVE-2025-61730 none yes
GO-2026-4341 CVE-2025-61726 none yes
GO-2026-4342 CVE-2025-61728 none yes
GO-2026-4601 CVE-2026-25679 none yes
GO-2026-4602 CVE-2026-27139 none yes
GO-2026-4603 CVE-2026-27142 none yes
GO-2026-4864 CVE-2026-32282 none yes
GO-2026-4865 CVE-2026-32289 none yes
GO-2026-4869 CVE-2026-32288 none yes
GO-2026-4870 CVE-2026-32283 none yes
GO-2026-4918 CVE-2026-33814 none yes
GO-2026-4946 CVE-2026-32281 none yes
GO-2026-4947 CVE-2026-32280 none yes
GO-2026-4970 CVE-2026-39822 none yes
GO-2026-4971 CVE-2026-39836 none yes
GO-2026-4976 CVE-2026-39825 none yes
GO-2026-4977 CVE-2026-42499 none yes
GO-2026-4980 CVE-2026-39826 none yes
GO-2026-4981 CVE-2026-33811 none yes
GO-2026-4982 CVE-2026-39823 none yes
GO-2026-4986 CVE-2026-39820 none yes
GO-2026-5026 CVE-2026-39821 none yes
GO-2026-5037 CVE-2026-27145 none yes
GO-2026-5038 CVE-2026-42504 none yes
GO-2026-5039 CVE-2026-42507 none yes
GO-2026-5856 CVE-2026-42505 none yes
GO-2026-5972 CVE-2026-33818 none yes
GO-2026-6088 CVE-2026-56859 none yes
GO-2026-6089 CVE-2026-56853 none yes
GO-2026-6090 CVE-2026-56862 none yes
GO-2026-6091 CVE-2026-56858 none yes
GO-2026-6218 CVE-2026-56860 none yes
GO-2026-6599 CVE-2026-94448 none yes
GO-2026-6600 CVE-2026-97030 none yes
GO-2026-6603 CVE-2026-78659 none yes
GO-2026-6604 CVE-2026-56857 none yes
GO-2026-6605 CVE-2026-56866 none yes

Showing 50 of 58 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

MCP tools · 1 exposed · ~197 tokens

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 →

Tool Tokens
sandbox_exec ~197

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.

NameTypeReqDescription
commandstringyesCommand to run inside the sandbox, executed via sh -c.
imagestring–Optional container image override (default: the server's configured image).
timeout_secondsinteger–Optional per-exec timeout override in seconds.

No output schema declared.

No examples provided.

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 -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.547. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/ironsecco/ironclaw-mcp

# add to Claude Code
claude mcp add ironsecco-ironclaw -- docker run --rm -i -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.547

This image reads IRONCLAW_CONTROLPLANE_URL and IRONCLAW_API_TOKEN. Set them in your client's env block for this server; docker run -e passes each one through to the container.

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).

Is the io.github.IronSecCo/ironclaw MCP server safe to use?

io.github.IronSecCo/ironclaw scores 56 out of 100 on VerifyMCP. We recorded 58 known advisories against it as of 18 October 2026. Its build provenance is signed and verified. 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 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.