ironclaw
Sandboxed shell exec for MCP clients: run untrusted agent commands in a gVisor container.
Connect
Review any command before running it. Package names and URLs come from the server's own registry entry.
Package (oci)
docker run -i --rm -e IRONCLAW_CONTROLPLANE_URL=<YOUR_VALUE> -e IRONCLAW_API_TOKEN=<YOUR_VALUE> ghcr.io/ironsecco/ironclaw-mcp:v0.1.569
Or add to your MCP client config:
{
"mcpServers": {
"ironclaw": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"IRONCLAW_CONTROLPLANE_URL=<YOUR_VALUE>",
"-e",
"IRONCLAW_API_TOKEN=<YOUR_VALUE>",
"ghcr.io/ironsecco/ironclaw-mcp:v0.1.569"
]
}
}
}
IRONCLAW_CONTROLPLANE_URLrequired — Base URL of your running IronClaw control-plane, e.g. http://127.0.0.1:8787. This image is a thin client with no host privilege: it delegates every sandbox_exec run to the control-plane, which owns the hardened gVisor launch. Unset means no backend and the tool fails closed.IRONCLAW_API_TOKENrequired secret — Bearer token for the control-plane API (the value the control-plane was started with).
This server takes extra arguments — see its repository.
Related servers
REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
browser-use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
paperclip
Trending hip-hop artist momentum scores across four cultural dimensions.
World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Ruflo
Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.
Front-End Checklist
Review frontend code and live pages against 386 quality-gated web development rules.
Data from the Official MCP Registry