RunVouch MCP server

Which servers in the official MCP registry are RunVouch's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-12

← Back to RunVouch

Whose server it is

Registry namecom.runvouch/runvouchverified in the MCP registry

The registry name sits under runvouch.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-12

Stateanswerschecked 2026-10-12
Tools7
Server calls itselfrunvouch
Server version0.3.0
Protocol version2025-06-18

On 2026-10-12 the server answered initialize and tools/list without a sign-in. First answer in 525 ms.

Tools it offers7 tools · read 2026-10-12

runvouch_status
Health of all watched agents: state (ok/alert/failed/unproven/running/waiting), last run, 24h cost, open alerts.
runvouch_alerts
Open (un-acknowledged) alerts: MISSED, FAILED, NO_EVIDENCE, BUDGET_RUN, BUDGET_DAY, RETRY_STORM, DRIFT, STALLED.
runvouch_ack
Acknowledge an alert by id.
runvouch_runs
Recent runs of one agent.
runvouch_run_start
Report that a run of `agent` started. Returns run_id.
runvouch_run_end
Report that a run ended, with status and evidence dict (name -> bool or {type:'url',url}). Green run without evidence alerts.
runvouch_run_proof
Tamper-evident proof of a finished run: hashed record, Merkle path, day root, chain hash and OpenTimestamps status. Verify offline with templates/verify_proof.py.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "runvouch": {
      "type": "http",
      "url": "https://api.runvouch.com/mcp"
    }
  }
}

OpenAPI spec

41 paths, read 2026-10-12. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.