# DOS — the trust substrate for agent fleets

DOS checks agent claims against Git artifacts, spots file collisions, and flags stalled runs. Use it when several agents work in one repository.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 20
- Author: anthony-chaudhary
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/anthony-chaudhary/dos-kernel
- Updated: 2026-09-27
- HTML: https://affpapa.org/en/nevibecode/mcp/dos-the-trust-substrate-for-agent-fleets

## What it does

DOS tests an agent’s report against the work left behind in Git. `dos verify` returns `SHIPPED` with exit code `0` when a commit supports the claim, or `NOT_SHIPPED` with exit code `1` when nothing landed. It can also surface agents touching the same files and runs that stop making progress.

The MCP server starts with `uvx dos-kernel`. Its workspace can be supplied through `DISPATCH_WORKSPACE`, with ready-made setup commands for Claude Code, Codex, Cursor, GitHub Copilot, and Gemini CLI. For direct repository setup, the project instructions use `dos-kernel`, `dos init --hooks auto`, and `dos doctor`.

DOS works against a Git repository and uses `PyYAML` as its runtime dependency. Set `DISPATCH_WORKSPACE` to the intended directory in the MCP configuration; otherwise the checks point at the wrong workspace.

## Requirements
- Needs: Python and uv (commands run via uvx)
- Environment variables: `DISPATCH_WORKSPACE` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add --env DISPATCH_WORKSPACE=<DISPATCH_WORKSPACE> --transport stdio dos-the-trust-substrate-for-agent-fleets -- uvx dos-kernel
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>

### Codex

**Platform CLI**
```bash
codex mcp add dos-the-trust-substrate-for-agent-fleets --env DISPATCH_WORKSPACE=<DISPATCH_WORKSPACE> -- uvx dos-kernel
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "dos-the-trust-substrate-for-agent-fleets": {
            "command": "uvx",
            "args": [
                "dos-kernel"
            ],
            "env": {
                "DISPATCH_WORKSPACE": "<DISPATCH_WORKSPACE>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "dos-the-trust-substrate-for-agent-fleets": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "dos-kernel"
            ],
            "env": {
                "DISPATCH_WORKSPACE": "<DISPATCH_WORKSPACE>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e DISPATCH_WORKSPACE=<DISPATCH_WORKSPACE> dos-the-trust-substrate-for-agent-fleets uvx dos-kernel
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>

## When to use it
- verify that a claimed change reached Git
- separate backed commits from false completion reports
- spot agents writing over the same files
- flag a run that keeps spinning without progress

## Example prompts
- Check whether claim `AUTH1` actually shipped and report the result with `dos verify`.
- Compare the agents’ claims with the repository commits and find claims that did not land.
- Inspect this workspace for file collisions between active agents.

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md