Runvouch is a remote MCP server that gives an AI agent 7 tools, among them runvouch_ack, runvouch_alerts, runvouch_run_end. It answers at https://api.runvouch.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
The watchdog for unattended AI agents: agent health, alerts, run reports with evidence and cost.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
runvouch_ack | Acknowledge an alert by id. Inputs: alert_id |
runvouch_alerts | Open (un-acknowledged) alerts: MISSED, FAILED, NO_EVIDENCE, BUDGET_RUN, BUDGET_DAY, RETRY_STORM, DRIFT, STALLED. |
runvouch_run_end | Report that a run ended, with status and evidence dict (name -> bool or {type:'url',url}). Green run without evidence alerts. Inputs: run_id, status, cost, tokens, evidence |
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. Inputs: run_id |
runvouch_run_start | Report that a run of `agent` started. Returns run_id. Inputs: agent, source |
runvouch_runs | Recent runs of one agent. Inputs: agent, limit |
runvouch_status | Health of all watched agents: state (ok/alert/failed/unproven/running/waiting), last run, 24h cost, open alerts. |
Every block below points at https://api.runvouch.com/mcp. Pick your client and copy.
claude mcp add --transport http runvouch https://api.runvouch.com/mcp
{
"mcpServers": {
"runvouch": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.runvouch.com/mcp"]
}
}
}{
"mcpServers": {
"runvouch": {
"url": "https://api.runvouch.com/mcp"
}
}
}{
"servers": {
"runvouch": {
"type": "http",
"url": "https://api.runvouch.com/mcp"
}
}
}{
"context_servers": {
"runvouch": {
"url": "https://api.runvouch.com/mcp"
}
}
}{
"mcpServers": {
"runvouch": {
"serverUrl": "https://api.runvouch.com/mcp"
}
}
}{
"mcpServers": {
"runvouch": {
"url": "https://api.runvouch.com/mcp"
}
}
}name: Runvouch
version: 0.0.1
schema: v1
mcpServers:
- name: Runvouch
type: streamable-http
url: https://api.runvouch.com/mcp{
"mcpServers": {
"runvouch": {
"httpUrl": "https://api.runvouch.com/mcp"
}
}
}{
"mcpServers": {
"runvouch": {
"type": "http",
"url": "https://api.runvouch.com/mcp"
}
}
}{
"mcpServers": {
"runvouch": {
"url": "https://api.runvouch.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.runvouch.com%2Fmcp&type=streamable_http&id=runvouch&name=Runvouch
It answered our last check on 18 October 2026 in 132 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by runvouch.com and served from api.runvouch.com, the vendor's own domain: https://api.runvouch.com/mcp.
7, as returned by the server's own tools/list on 31 August 2026: runvouch_ack, runvouch_alerts, runvouch_run_end, runvouch_run_proof, runvouch_run_start, runvouch_runs, runvouch_status.
It answered our last check on 18 October 2026 in 132 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.runvouch.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.runvouch. Endpoint host: api.runvouch.com. ARD identifier: urn:air:com.runvouch:mcp:runvouch.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.