Capacity Attest MCP Server

What the code does

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

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.

  const match = AGENT_REGISTRY_REF_RE.exec(input.reputationRegistryRef);

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      - name: Update npm (trusted publishing + provenance need npm >= 11.5.1)

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 capacity-attest -- npx -y capacity-attest

{
  "mcpServers": {
    "capacity-attest": {
      "args": [
        "-y",
        "capacity-attest"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.capacity-attest]
command = "npx"
args = ["-y", "capacity-attest"]

{
  "mcpServers": {
    "capacity-attest": {
      "args": [
        "-y",
        "capacity-attest"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "capacity-attest": {
      "args": [
        "-y",
        "capacity-attest"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: CAPACITY_ATTEST_DATA_DIR (Directory the append-only claims ledger (claims.jsonl) is written to and read from. Defaults to ./data inside the package.). The author declared them in the registry entry; get the values from the project itself.