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

io.github.IronSecCo/ironclaw

OCI · GHCR.IO/IRONSECCO/IRONCLAW-MCP:V0.1.499 · SCANNED AUG 3

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

34 Trust /100
Trust breakdown (6 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 →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • CVE data not yet available for this package.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency-health data not yet available.Unverified
Provenance & Transparency32
Schema Quality & AI Usability77
  • 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail

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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/ironsecco/ironclaw-mcp:v0.1.499

# add to Claude Code
claude mcp add ironsecco-ironclaw -- docker run --rm -i ghcr.io/ironsecco/ironclaw-mcp:v0.1.499
# add to Codex CLI
codex mcp add ironsecco-ironclaw -- docker run --rm -i ghcr.io/ironsecco/ironclaw-mcp:v0.1.499
// 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.499"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  ironsecco-ironclaw:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/ironsecco/ironclaw-mcp:v0.1.499"]
// mcp.json
{
  "mcpServers": {
    "ironsecco-ironclaw": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ironsecco/ironclaw-mcp:v0.1.499"
      ]
    }
  }
}
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.

  • 3 Aug 26 +28
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
  • 2 Aug 26 6

    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 3 Aug 2026 · Analysed oci/ghcr.io/ironsecco/ironclaw-mcp:v0.1.499

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

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.

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.
imagestringOptional container image override (default: the server's configured image).
timeout_secondsintegerOptional per-exec timeout override in seconds.

No output schema declared.

No examples provided.