MCP Registry Monitor vs Runvouch
A side-by-side look at the MCP Registry Monitor and Runvouch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Registry Monitor for monitoring work over a hosted endpoint; choose Runvouch for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Registry Monitor when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
MCP_WATCH_DATABASE_URL. - You want tools like
list_mcp_servers, search_mcp_servers.
Choose Runvouch when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RUNVOUCH_KEY, RUNVOUCH_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 53/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | MCP_WATCH_DATABASE_URL | RUNVOUCH_KEYRUNVOUCH_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 30 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View MCP Registry Monitor | View Runvouch |
Tools & capabilities
MCP Registry Monitor tools 2
list_mcp_serversList popular MCP serverssearch_mcp_serversSearch MCP servers
Runvouch tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Registry Monitor
{
"mcpServers": {
"mcp-registry-monitor": {
"url": "https://modelcontextprotocol.name/mcp/mcp-notify"
}
}
}
Runvouch
{
"mcpServers": {
"runvouch-2": {
"command": "uvx",
"args": [
"runvouch"
],
"env": {
"RUNVOUCH_KEY": "YOUR_RUNVOUCH_KEY_HERE",
"RUNVOUCH_URL": "YOUR_RUNVOUCH_URL_HERE"
}
}
}
}
Frequently asked questions
MCP Registry Monitor is categorized under Monitoring and uses a remote HTTP/SSE transport. Runvouch belongs to Monitoring and uses a local stdio subprocess. Pick MCP Registry Monitor for monitoring work and Runvouch for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Registry Monitor has no declared pricing — check the project's own site. Runvouch has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-registry-monitor and runvouch-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Registry Monitor has a quality signal of 53/100 (Good) with 0 views, 0 installs and 30 GitHub stars. Runvouch has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.