Ironclaw

Name: Ironclaw
Author: IronSecCo

作者：IronSecCo版本 0.1.569i★ –i在你的电脑上运行

注册名称io.github.IronSecCo/ironclaw

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具
你需要填写：IRONCLAW_CONTROLPLANE_URL, IRONCLAW_API_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： IRONCLAW_CONTROLPLANE_URL, IRONCLAW_API_TOKEN

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "ironclaw": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "IRONCLAW_CONTROLPLANE_URL",
        "-e",
        "IRONCLAW_API_TOKEN",
        "ghcr.io/ironsecco/ironclaw-mcp:v0.1.569"
      ],
      "env": {
        "IRONCLAW_CONTROLPLANE_URL": "your-value",
        "IRONCLAW_API_TOKEN": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add ironclaw --env IRONCLAW_CONTROLPLANE_URL=your-value --env IRONCLAW_API_TOKEN=your-value -- docker run -i --rm -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.569

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "ironclaw": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "IRONCLAW_CONTROLPLANE_URL",
        "-e",
        "IRONCLAW_API_TOKEN",
        "ghcr.io/ironsecco/ironclaw-mcp:v0.1.569"
      ],
      "env": {
        "IRONCLAW_CONTROLPLANE_URL": "your-value",
        "IRONCLAW_API_TOKEN": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "ironclaw": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "IRONCLAW_CONTROLPLANE_URL",
        "-e",
        "IRONCLAW_API_TOKEN",
        "ghcr.io/ironsecco/ironclaw-mcp:v0.1.569"
      ],
      "env": {
        "IRONCLAW_CONTROLPLANE_URL": "your-value",
        "IRONCLAW_API_TOKEN": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

IRONCLAW_CONTROLPLANE_URL 必填 env
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 t…
IRONCLAW_API_TOKEN 机密必填 env
Bearer token for the control-plane API (the value the control-plane was started with).

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 IronSecCo 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 5566 个服务器的 0%
发布到注册中心的时间比此分类中其他 5566 个服务器的 76% 更新
基础检查结果等于或优于此分类中其他 5566 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Ironclaw 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：IRONCLAW_CONTROLPLANE_URL, IRONCLAW_API_TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.569）于6天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

作者：github广泛使用★ 3.4万5天前更新

电脑或云端

安装

Desktop Commander

MCP server for terminal commands, file operations, and process management

作者：wonderwhy-er广泛使用↓ 71万/周★ 1万17天前更新

在你的电脑上运行

安装

Cloudflare MCP

Cloudflare MCP servers

作者：cloudflare广泛使用★ 444614个月前更新

在云端运行✓ mcp.cloudflare.com

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Self-hosted AI agents you do not have to trust.

Each one runs sealed in a sandbox that provably cannot phone home, read your host, or rewrite its own rules.

IronClaw runs autonomous AI agents on infrastructure you control, reached through the chat apps you already use. Each agent can read, write, schedule, and reply like any assistant, but it lives inside a sealed sandbox with network=none: it reaches the model only through a host proxy, and it cannot change its own configuration. It is for anyone who wants what agents can do without handing an autonomous program the keys to their machine.

Now on the GitHub Marketplace. The ironctl scan containment grader ships as a

GitHub Action: drop one

line into a workflow and every pull request gets a 0 to 100 sandbox isolation scorecard as

a sticky comment. Local, read-only, credential-free.

`yaml

# .github/workflows/scan.yml

- uses: IronSecCo/ironclaw@v1

with:

target: my-container # a container, compose service, or k8s manifest

`

Report-only by default; set min-score: 90 to gate merges. See scan in CI.

Watch it catch a real escape. A fully-jailbroken agent inside a real sandbox tries to phone home, read the host filesystem, and seize the host through the Docker socket. Each attempt is denied at the isolation boundary, then a containment summary prints. One command, zero credentials, reduced-motion friendly. examples/live-containment/run.sh

⭐ Like the idea of agents you do not have to trust? [Star the repo](https://github.com/IronSecCo/ironclaw) so it is one click to follow along and easier for the next person to find. Then run the exact demo above in 30 seconds, no signup and no API key.

Try it in 30 seconds (zero credentials)

Make sure the Docker daemon is running (start Docker Desktop, or sudo systemctl start docker on Linux), then paste one block:

git clone https://github.com/IronSecCo/ironclaw.git && cd ironclaw

examples/live-containment/run.sh # builds the sandbox once, engages a real sandbox, proves it holds

That single command runs the whole secured path on your laptop: it starts the offline mock-agent control-plane (no API key), engages a real per-session sandbox, lets a jailbroken agent try to break out, and prints the containment summary you saw above. Want to chat with an agent in a browser first? Run hello-ironclaw or the zero-credential quickstart. Production seals each sandbox with gVisor and network=none.

[!WARNING]

Alpha software, work in progress. Please read before relying on it.

- It's an alpha. Flags, the on-disk format, and the HTTP/contract surfaces can still change without notice or a migration path. Don't point it at anything you can't afford to lose.

- Not every feature is tested end-to-end. The control-plane, gateway, and encrypted-queue core have real coverage (800+ Go tests plus a black-box parity suite); channel adapters, some tools, multi-provider routing, and a live sandbox launch are exercised more lightly. Treat anything outside the tested core as experimental.

macOS gets a weaker sandbox boundary than Linux+gVisor, and native Windows can't run the agent sandbox at all (use WSL2). See Platform support.

The security model, in one line: each sandboxed agent runs with network=none, reaches the

model only through a host proxy, and cannot change its own configuration. Every capability

change is held at a gateway for a human decision. The full design is in the

architecture overview and the threat model.

See the whole journey, end to end

Zero credentials, one command. The offline mock-agent runs the full chat to per-session sandbox to reply path with no API key. Production seals each sandbox with gVisor and network=none . Quickstart

Zero-cred demo, connect a real provider, first approved task. The one credential step keeps the key host-side; every agent change is held at the gateway for a human, then written to the append-only audit log. Animation freezes on the final frame under prefers-reduced-motion . Quickstart

Get running in under two minutes

One command installs the two host binaries (ironctl + ironclaw-controlplane); in dev mode the control-plane serves its API at `http://127.0.0.1:8787`. From a cold machine, you'll have a capability change waiting at the security gateway in under two minutes:

# 1. Install — detects your OS/arch and verifies the SHA-256 checksum before installing

curl -fsSL https://raw.githubusercontent.com/IronSecCo/ironclaw/main/scripts/install.sh | sh

2. Start the control-plane in dev mode — API base URL: http://127.0.0.1:8787

export IRONCLAW_API_TOKEN=$(openssl rand -hex 32) ironclaw-controlplane --dev --api-addr 127.0.0.1:8787 &

3. Your first command — submit a change; it is HELD at the gateway for a human decision

ironctl change submit --kind persona --group dev-agent --by you ironctl change pending # see it waiting ironctl change approve --by you # apply it

On Windows, irm https://raw.githubusercontent.com/IronSecCo/ironclaw/main/scripts/install.ps1 | iex installs the host binaries (ironclaw-controlplane.exe + ironctl.exe) and --dev runs, but the agent sandbox needs WSL2 or Linux — see Windows via WSL2. Version pinning, system-wide installs, and building from source are all in Installation.

One-click cloud deploy

Run the hardened control-plane on a PaaS in ~2 minutes with zero local tooling — the approval gateway, encrypted per-session queues, host-side credential custody, and the web console:

These PaaS paths run the control-plane only — a single container has no gVisor and

no Docker socket, so agent sandboxes don't launch there (same boundary as the

hardened Compose path). For full agent isolation use

a gVisor host or k8s node. Details + env in the

deployment guide (Path D).

CLI-first and API-first

This is a feature, not a missing dashboard. Every capability is a documented HTTP endpoint and an ironctl subcommand, so IronClaw is scriptable, auditable, and CI-frien

只显示了开头部分；其余内容请在仓库中阅读