DOS — the trust substrate for agent fleets MCP Server

What the code does

We read the source, 12 h ago · rules 3dff92dd89df

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

            r = subprocess.run(

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    out = subprocess.run(

    return os.path.join(cwd, path) if cwd else path

            shell=True,

        env = dict(os.environ)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add dos-kernel -- uvx dos-kernel

{
  "mcpServers": {
    "dos-kernel": {
      "args": [
        "dos-kernel"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.dos-kernel]
command = "uvx"
args = ["dos-kernel"]

{
  "mcpServers": {
    "dos-kernel": {
      "args": [
        "dos-kernel"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "dos-kernel": {
      "args": [
        "dos-kernel"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: DISPATCH_WORKSPACE (Path of the git workspace the server should adjudicate (defaults to its working directory; every tool also takes a per-call `workspace` argument).). The author declared them in the registry entry; get the values from the project itself.