runvouch
Server Details
Watchdog for unattended AI agents: alerts, evidence checks and a verifiable proof per run.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- runvouch/runvouch
- GitHub Stars
- 0
- Server Listing
- runvouch
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 7 tools
Tools target distinct resources (alerts, runs, status, proofs), but runvouch_alerts and runvouch_status both surface open alerts, and runvouch_runs overlaps somewhat with runvouch_status's run-history display. Descriptions are specific enough to prevent serious misselection.
All tools share the runvouch_ prefix, but the style mixes bare verbs (runvouch_ack), noun lists (runvouch_alerts, runvouch_runs), and noun-verb compounds (runvouch_run_start, runvouch_run_end). The names are readable, but there is no single consistent verb_noun convention.
Seven tools is a well-scoped size for a run-vouching/alerting server. Each tool serves a clear operational purpose: starting/ending runs, retrieving proof/history, and managing alerts.
The core lifecycle is covered: start run, end run with evidence, retrieve proof, list runs, check status, list/ack alerts. Minor gaps exist such as no detailed alert/run getter or evidence modification, but agents can complete main workflows without dead ends.
Available Tools
7 toolsrunvouch_ackCInspect
Acknowledge an alert by id.
Inputs: alert_id (required).
runvouch_alertsBRead-onlyInspect
Open (un-acknowledged) alerts: MISSED, FAILED, NO_EVIDENCE, BUDGET_RUN, BUDGET_DAY, RETRY_STORM, DRIFT, STALLED.
Inputs: no named parameters.
runvouch_run_endCInspect
Report that a run ended, with status and evidence dict (name -> bool or {type:'url',url}). Green run without evidence alerts.
Inputs: run_id (required), cost, status, tokens, +1 more.
runvouch_run_proofARead-onlyInspect
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 (required).
runvouch_runsBRead-onlyInspect
Recent runs of one agent.
Inputs: agent (required), limit.
runvouch_run_startCInspect
Report that a run of agent started. Returns run_id.
Inputs: agent (required), source.
runvouch_statusARead-onlyInspect
Health of all watched agents: state (ok/alert/failed/unproven/running/waiting), last run, 24h cost, open alerts.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Check, limit, record and prove AI agent actions with 2-of-3 validators and onchain proofs.
Checks AI agent actions before they run. Signed, RFC 3161 timestamped evidence for audits.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Policy-aware AI execution, verification, cost, and trajectory evidence for agents.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceCaptures AI agent runs and turns them into tamper-evident execution records showing tool use, timing, failures, recoveries, and human interventions. Records can be inspected, exported, and verified offline.MIT
- AlicenseAqualityBmaintenanceMonitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.503MIT
- AlicenseAqualityAmaintenanceProof-of-behavior enforcement for AI agents. Declare behavioral constraints, enforce at runtime, produce SHA-256 hash-chained audit trails. Supports covenants (permit/forbid/require), real-time verification, and cross-agent trust handshakes.440MIT
- AlicenseNot gradedqualityBmaintenanceTamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.329 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.