Outage MCP vs RealUptime
A side-by-side look at the Outage MCP and RealUptime MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RealUptimeMonitoringRealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.37FairAuth: not declaredVerdict: choose Outage MCP for monitoring work as a local process; choose RealUptime for monitoring. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Outage MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You want tools like
whats_down, check_service, get_incident.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R RealUptime | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 48/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Outage MCP | View RealUptime |
Tools & capabilities
Outage MCP tools 5
whats_down"What's broken right now?" Active incidents first, then recently resolved.check_service"Is Stripe down?" Status and recent history for one service.get_incidentFull detail for one incident, including AI root-cause analysis when available.outage_stats"What broke most this week?" Leaderboard and totals.list_servicesThe 100+ services being monitored.
RealUptime 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.
Outage MCP
{
"mcpServers": {
"outage-mcp": {
"command": "npx",
"args": [
"-y",
"outage-mcp"
]
}
}
}
RealUptime
No confirmed install command for RealUptime yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Outage MCP is categorized under Monitoring and uses a local stdio subprocess. RealUptime belongs to Monitoring and uses an install path we have not confirmed yet. Pick Outage MCP for monitoring work and RealUptime 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. RealUptime has no confirmed install command yet — follow its own setup instructions.
Outage MCP has no declared pricing — check the project's own site. RealUptime 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 outage-mcp and realuptime as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Outage MCP has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. RealUptime has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
