INDIVIDUAL MCP TOOL
is_service_down
Is a third-party service currently down, as measured by RealUptime's own probes from up to four named regions?
LIVE ENDPOINT
https://mcp.realuptime.io/public
Connect to this endpoint to inspect the live schema for is_service_down and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.realuptime-outages]
url = "https://mcp.realuptime.io/public"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"realuptime-outages": {
"type": "http",
"url": "https://mcp.realuptime.io/public"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: realuptime-outages
Remote MCP URL: https://mcp.realuptime.io/public
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"realuptime-outages": {
"url": "https://mcp.realuptime.io/public"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"realuptime-outages": {
"type": "http",
"url": "https://mcp.realuptime.io/public"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "realuptime-outages",
"transport": "streamable-http",
"url": "https://mcp.realuptime.io/public"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_regional_readings— Every current per-region reading RealUptime holds for one catalog service, both endpoint roles, with per-region status, latency, measurement timestamp, and whether each reading is still fresh.get_report_volume— How many people are reporting problems with one catalog service right now, by region, and whether that is unusual against its own trailing baseline.list_recent_incidents— Past outages RealUptime detected for one catalog service.get_stack— One "my stack" page: a named set of RealUptime-tracked services, each with the SAME plate level its own page shows (down / partially_down / degraded / partially_degraded / blocked / no_data / partially_unverified / up, with label and clause), plus the stack's roll-up: `summary.internet_weather— How the internet looks from RealUptime's probe regions right now (https://realuptime.is_the_internet_down— Is there a shared-infrastructure incident right now (Cloudflare, an AWS region, a CDN), as inferred from RealUptime's own probes across every service it tracks?