runvouch MCP server
com.runvouch/runvouchrunvouch.comstreamable-httpv0.3.4Scanned
Watchdog for unattended AI agents: alerts, evidence checks and a verifiable proof per run.
7 tools: 6 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the runvouch MCP server can do
The runvouch MCP server is published by runvouch.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (6 tools: runvouch_alerts, runvouch_ack, runvouch_runs, runvouch_run_start and 2 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 0.3.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 6Claude Code: ask
runvouch_ackAcknowledge an alert by id.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Acknowledge an alert by id.
runvouch_alertsOpen (un-acknowledged) alerts: MISSED, FAILED, NO_EVIDENCE, BUDGET_RUN, BUDGET_DAY, RETRY_STORM, DRIFT, STALLED.1 finding
Why it is in this group
- The description's first verb is "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "runvouch_alerts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The description's first verb is "open": a word for a change.
Description, as the server wrote it Open (un-acknowledged) alerts: MISSED, FAILED, NO_EVIDENCE, BUDGET_RUN, BUDGET_DAY, RETRY_STORM, DRIFT, STALLED.
Annotations the server declares
- readOnlyHint: true
runvouch_run_endReport that a run ended, with status and evidence dict (name -> bool or {type:'url',url}).No findings
Why it is in this group
- The name "runvouch_run_end" says "run": a word for a change.
Description, as the server wrote it Report that a run ended, with status and evidence dict (name -> bool or {type:'url',url}). Green run without evidence alerts.
runvouch_run_proofTamper-evident proof of a finished run: hashed record, Merkle path, day root, chain hash and OpenTimestamps status.1 finding
Why it is in this group
- The name "runvouch_run_proof" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "runvouch_run_proof" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "runvouch_run_proof" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
runvouch_run_startReport that a run of `agent` started.No findings
Why it is in this group
- The name "runvouch_run_start" says "run": a word for a change.
Description, as the server wrote it Report that a run of `agent` started. Returns run_id.
runvouch_runsRecent runs of one agent.1 finding
Why it is in this group
- The name "runvouch_runs" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "runvouch_runs" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "runvouch_runs" says "run": a word for a change.
Description, as the server wrote it Recent runs of one agent.
Annotations the server declares
- readOnlyHint: true
Only reads 1Show 1 read-only tool
runvouch_statusHealth of all watched agents: state (ok/alert/failed/unproven/running/waiting), last run, 24h cost, open alerts.No findings
Why it is in this group
- The name "runvouch_status" says "status": a word for reading.
Description, as the server wrote it Health of all watched agents: state (ok/alert/failed/unproven/running/waiting), last run, 24h cost, open alerts.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.runvouch.com/mcp: tools/list returned 7 tools to an anonymous client, including runvouch_alerts (write), runvouch_ack (write), runvouch_runs (write), runvouch_run_start (write), runvouch_run_end (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
- Warnrunvouch_alerts
The server marks "runvouch_alerts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The description's first verb is "open": a word for a change.
- Warnrunvouch_runs
The server marks "runvouch_runs" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "runvouch_runs" says "run": a word for a change.
The server marks "runvouch_run_proof" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "runvouch_run_proof" says "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.3.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http runvouch https://api.runvouch.com/mcp --header 'X-API-Key: <your-x-api-key>'claude mcp add --transport http runvouch https://api.runvouch.com/mcp --header 'X-API-Key: <your-x-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__runvouch__runvouch_status"
],
"ask": [
"mcp__runvouch__runvouch_alerts",
"mcp__runvouch__runvouch_ack",
"mcp__runvouch__runvouch_runs",
"mcp__runvouch__runvouch_run_start",
"mcp__runvouch__runvouch_run_end",
"mcp__runvouch__runvouch_run_proof"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as runvouch. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.runvouch/runvouch/verify?hash=4a002dfbb19e75c9fb3855dbeded19a1385f26cbf8bb2e61e5add5f4bc4ceecb" | jq -e '.changed == false'Pinned hash 4a002dfbb19e, from Nov 11, 2026, 01:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.runvouch/runvouch/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.runvouch/runvouch)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:02 UTC.
runvouch MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the runvouch MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 6 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the runvouch MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the runvouch MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the runvouch MCP server have?
- 7 tools: 6 write, 1 read. runvouch_alerts, runvouch_ack, runvouch_runs, runvouch_run_start, runvouch_run_end, runvouch_run_proof and runvouch_status.
Does the runvouch MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the runvouch MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the runvouch MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.