Is the Runvouch MCP server down?

mcp-registry/com.runvouch/runvouch · v0.3.0

Also listed as github/runvouch/runvouch

healthy
Last checked 2026-10-17 06:05 UTC · handshake 2.5s

As of 2026-10-17 06:05 UTC, the Runvouch MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
100%
checks observed
3,601
outages (90d)
2
tools
7

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

Install Runvouch MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http runvouch-mcp-server https://api.runvouch.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (67/100)

D (67/100): 0 error(s), 3 warning(s) across 7 tool(s); ~474 tokens of tool definitions.
Scores higher than 2% of 15,244 MCP servers Glimind has audited.
Its tool list costs an agent ~474 tokens per session — more than 5% of servers.
no tool-poisoning patterns
Schemas100
Descriptions40
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

6 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.

Tools: runvouch_ack, runvouch_alerts, runvouch_run_end, runvouch_run_proof, runvouch_run_start and 1 more

11 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: runvouch_ack, runvouch_run_end, runvouch_run_proof, runvouch_run_start, runvouch_runs

Handshake + tools/list takes ~2,211 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.

3 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.

Tools: runvouch_ack, runvouch_run_end, runvouch_run_start

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.runvouch%2Frunvouch/fixes

runvouch_ack 1 change
{
  "name": "runvouch_ack",
  "description": "Acknowledge an alert by id.",
  "inputSchema": {
    "type": "object",
    "required": [
      "alert_id"
    ],
    "properties": {
      "alert_id": {
        "type": "integer"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
runvouch_run_end 1 change
{
  "name": "runvouch_run_end",
  "description": "Report that a run ended, with status and evidence dict (name -> bool or {type:'url',url}). Green run without evidence alerts.",
  "inputSchema": {
    "type": "object",
    "required": [
      "run_id"
    ],
    "properties": {
      "cost": {
        "type": "number"
      },
      "run_id": {
        "type": "string"
      },
      "status": {
        "enum": [
          "ok",
          "fail"
        ],
        "type": "string"
      },
      "tokens": {
        "type": "integer"
      },
      "evidence": {
        "type": "object"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
runvouch_run_start 1 change
{
  "name": "runvouch_run_start",
  "description": "Report that a run of `agent` started. Returns run_id.",
  "inputSchema": {
    "type": "object",
    "required": [
      "agent"
    ],
    "properties": {
      "agent": {
        "type": "string"
      },
      "source": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.runvouch/runvouch"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.runvouch/runvouch"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.runvouch%2Frunvouch.svg)](https://glimind.com/server/mcp-registry%2Fcom.runvouch%2Frunvouch?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.runvouch%2Frunvouch?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.runvouch%2Frunvouch.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.runvouch%2Frunvouch.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.runvouch%2Frunvouch?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6e5f02d0879e292e…, first seen 2026-10-17, included at leaf 551 of 17,012. Version history · verify what your client received.

Tools (7)

Compare: most reliable devops servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Runvouch MCP server down right now?

As of 2026-10-17 06:05 UTC, the Runvouch MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Runvouch MCP server provide?

Runvouch MCP server advertises 7 tools, including runvouch_ack, runvouch_alerts, runvouch_run_end, runvouch_run_proof, runvouch_run_start.

How do I install Runvouch MCP server?

Point your MCP client at this streamable-http endpoint: https://api.runvouch.com/mcp

Is the Runvouch MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Runvouch MCP server?

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.