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.

Exec Sandbox

OCI · DOCKER.IO/IDCONSTRUCT/MCP-EXEC:V0.5.4 · SCANNED AUG 3

Single exec tool running caller Python in a network-isolated locked-down sandbox.

−4 this week 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 Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 387 tokens (~387/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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 · docker.io/idconstruct/mcp-exec:v0.5.4

# add to Claude Code
claude mcp add inhuman-mcp-exec -- docker run --rm -i docker.io/idconstruct/mcp-exec:v0.5.4
# add to Codex CLI
codex mcp add inhuman-mcp-exec -- docker run --rm -i docker.io/idconstruct/mcp-exec:v0.5.4
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "inhuman-mcp-exec": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "docker.io/idconstruct/mcp-exec:v0.5.4"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  inhuman-mcp-exec:
    command: "docker"
    args: ["run", "--rm", "-i", "docker.io/idconstruct/mcp-exec:v0.5.4"]
// mcp.json
{
  "mcpServers": {
    "inhuman-mcp-exec": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/idconstruct/mcp-exec:v0.5.4"
      ]
    }
  }
}
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.

  • 31 Jul 26 −4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 +30
    • Tool coverage: unverified → 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • First check of Tool coverage: 100 functional
  • 26 Jul 26 8

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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/docker.io/idconstruct/mcp-exec:v0.5.4

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

MCP tools — 1 exposed · ~387 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
exec ~387

Execute Python code in a network-isolated sandbox and return its output. Environment: Python 3 with stdlib plus PyYAML and Jinja2. Limits: no network; wall-clock timeout defaults to 30s (max 300s); combined stdout+stderr is capped at 1048576 bytes then truncated; stdin is capped at 1048576 bytes. A non-zero exit_code or timed_out=true is a NORMAL result, not a tool error. INPUT CONTRACT — follow exactly: • `code`: Python source as a single string, newlines as \n. Top-level statements MUST start at column 0 — NO leading spaces/tabs. Indent ONLY bodies of blocks (after a line ending with ':'). Wrong: "import json\n d=json.load(...)" (leading space → IndentationError). Right: "import json\nd=json.load(...)". • `stdin`: a STRING piped to the program's stdin (read it with sys.stdin). To pass JSON, pass it AS a string — do not pass a parsed object/map. • Read input from sys.stdin, print results to stdout. Example: code="import json,sys\nd=json.load(sys.stdin)\nprint(len(d['items']))", stdin="{\"items\":[1,2,3]}" → stdout "3".

NameTypeReqDescription
codestringyesPython source as one string (\n for newlines). Top-level statements MUST start at column 0 (no leading spaces); indent only block bodies after a line ending in ':'. Read sys.stdin, print to stdout.
stdinstringSTRING piped to the program's stdin (max 1 MiB). To pass JSON, pass it as a string — not a parsed object.
timeout_sintegerwall-clock timeout in seconds (default 30, clamped to [1,300])
NameTypeReqDescription
duration_msintegeryes
exit_codeintegeryes
stderrstringyes
stdoutstringyes
timed_outbooleanyes
truncatedbooleanyes

No examples provided.