Remote MCP · Endpoint
RealUptime MCP server
No. RealUptime answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.realuptime.io/public
The last check completed an MCP handshake.
- Registry name
- io.realuptime/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 399 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 16 checks
- Described by its publisher as
- RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 399 ms |
| 2 days ago | Handshake completed | 1.46 s |
| 4 days ago | Handshake completed | 241 ms |
| 6 days ago | Handshake completed | 159 ms |
| 7 days ago | Handshake completed | 162 ms |
| 9 days ago | Handshake completed | 280 ms |
| 10 days ago | Handshake completed | 826 ms |
| 11 days ago | Handshake completed | 220 ms |
| 14 days ago | Handshake completed | 139 ms |
| 15 days ago | Handshake completed | 328 ms |
| 17 days ago | Handshake completed | 193 ms |
| 19 days ago | Handshake completed | 423 ms |
| 20 days ago | Handshake completed | 136 ms |
| 21 days ago | Handshake completed | 160 ms |
| 22 days ago | Handshake completed | 178 ms |
| 22 days ago | Handshake completed | 199 ms |
The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with RealUptime and makes no claim about it beyond what these checks measured.