bots.st/realuptime
RealUptime
Status and outage checks across regions
242 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 7
- Answered
- 4 of the last 4 calls
How to reach it
- MCP, HTTP
https://mcp.realuptime.io/mcpNeeds header Authorization - MCP, HTTP
https://mcp.realuptime.io/public
What it can do
| Tool | What it says it does |
|---|---|
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. This is the regional detail behind is_service_down: use it to answer "is X down in Europe" style… |
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. Returns a per-region count of reports and distinct reporters for the most recent five-minute window, a spike verdict of "spike", "normal" or… |
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.headline` ("2 of 6… |
internet_weather | How the internet looks from RealUptime's check regions right now (https://realuptime.io/outages/internet-weather): for each of the ten regions (iad = US-East, sjc = US-West, fra = Europe, nrt = Asia-Pacific, ord = US-Central, yyz = Canada, lhr = UK, sin = Southeast Asia, syd = Australia, gru =… |
is_service_down | Do RealUptime's own checks of a third-party service currently fail, from named regions? A check is one unauthenticated request to the service's front door; it says whether that check passed or failed, not whether the service works for users. Returns a verdict of "up" (our checks pass), "down" (our… |
is_the_internet_down | Is there a shared-infrastructure incident right now (Cloudflare, an AWS region, a CDN), as inferred from RealUptime's own checks across every service it tracks? Answers one of three levels: "ok" (no shared incident; a count of services whose checks fail travels with the catalog size)… |
list_recent_incidents | Past probe events RealUptime recorded for one catalog service whose status feed we cannot read. For a service whose feed works, `recent_events`, `last_outage` and `reliability` are `available: false` with the reason (the vendor's declared incidents are what count, our probe events are not listed… |
In its maker's words
RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.
- Website
- realuptime.io/docs/api#mcp-server
- Publisher
- realuptime.io
- Listed from
- the official MCP Registry as
io.realuptime/mcp - Version
- 0.1.0, updated 25 Sep 2026
- Kinds of work
- cloud-and-devops, search-and-research, messaging-and-support
The domain it lives on
- realuptime.io
- registered 4 Aug 2026 (3 months ago), at NAMECHEAP INC, its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 242 ms | |
| Answered | 115 ms | |
| Answered | 235 ms | |
| Answered | 235 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.