Attest proxy MCP Server

What the code does

We read the source, 8 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.

        subprocess.run(["git", "-C", str(self.repo), "add", str(f.relative_to(self.repo))], check=True, capture_output=True)

   "host": "api.telegram.org",

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 attest-proxy -- uvx attestlayer

{
  "mcpServers": {
    "attest-proxy": {
      "args": [
        "attestlayer"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.attest-proxy]
command = "uvx"
args = ["attestlayer"]

{
  "mcpServers": {
    "attest-proxy": {
      "args": [
        "attestlayer"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "attest-proxy": {
      "args": [
        "attestlayer"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: ATTEST_POLICY (Path to a policy YAML), ATTEST_LEDGER (Ledger SQLite path (default .attest/ledger.sqlite)), ATTEST_INBOX_URL (URL of the confirm inbox (attest serve) linked from Slack cards), SLACK_BOT_TOKEN (Slack bot token for confirm cards), ATTEST_SLACK_CHANNEL (Slack channel for confirm cards). The author declared them in the registry entry; get the values from the project itself.