Skip to main content
Glama

Server Details

Watchdog for unattended AI agents: alerts, evidence checks and a verifiable proof per run.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
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

B3.3/5.0

Scored across 7 tools

Disambiguation4/5

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.

Naming Consistency3/5

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.

Tool Count5/5

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.

Completeness4/5

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 tools
runvouch_ackCInspect

Acknowledge an alert by id.

Inputs: alert_id (required).

runvouch_alertsB
Read-only
Inspect

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_proofA
Read-only
Inspect

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_runsB
Read-only
Inspect

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_statusA
Read-only
Inspect

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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Captures 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
    • A
      license
      A
      quality
      A
      maintenance
      Proof-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.
      4
      40
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Tamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.
      3
      29 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.