Other · Remote MCP server
RealUptime
RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.realuptime/mcp- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- io.realuptime
- Namespace
- Namespace verified by the MCP Registry via the domain realuptime.io · how
- Website
- realuptime.io/docs/api#mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.realuptime.io/mcp | Authorization (required, secret) |
| Streamable HTTP | https://mcp.realuptime.io/public | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://mcp.realuptime.io/mcp(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://mcp.realuptime.io/public(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- realuptime-outages 0.1.0 · protocol 2025-06-18
- Tools discovered
- 7:
is_service_down,get_regional_readings,get_report_volume,list_recent_incidents,get_stack,internet_weather,is_the_internet_down - Checked on
- 2026-10-05
How to connect RealUptime
RealUptime is a remote MCP server: there is nothing to install. Its endpoints are https://mcp.realuptime.io/mcp and https://mcp.realuptime.io/public, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| RealeventsCreate and manage events in seconds from your AI assistant. No account needed. | Local · stdio |
| realhands - Real Desktop Computer UseLets Claude drive your REAL mouse, keyboard and screen - works in your own logged-in apps. | Local · stdio |
| Reality Next Door WalkWalk a cited post-extraction Seattle as an MCP world: go(), talk_to(), do(). Read-only, untracked. | Local · stdio |
| Realtime Sports APIScores, play-by-play, schedules, box scores and odds: NFL, college football, NBA, MLB, NHL, soccer. | Remote · HTTPLive check: ✓ handshake |
| RealurlsWhich domain officially belongs to which software product or company. Ownership only, never safety. | Local · stdio |
| RealWorldAPIsEvidence-first registry of real-world APIs for AI agents, with verified metadata and comparison. | Remote · HTTPLive check: ✓ handshake |
| REAPER MCPLets an AI assistant work in your open REAPER project: mixing, MIDI, routing and rendering. | Local · stdio |
| ReasonGateProvenance gateway for stdio MCP servers: blocks tool calls fed by untrusted tool results. | Local · stdio |