Remote MCP · Endpoint

OneUptime MCP server

No. OneUptime answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://oneuptime.com/mcp

The last check completed an MCP handshake.

Registry name
com.oneuptime/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
408 ms
Tools exposed
352 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
Listing
From the official MCP registry (active).
Recent checks of OneUptime
CheckedResultHandshake
34 minutes agoHandshake completed408 ms
8 days agoHandshake completed84 ms
9 days agoHandshake completed63 ms
11 days agoHandshake completed67 ms
12 days agoHandshake completed86 ms
12 days agoHandshake completed79 ms
14 days agoHandshake completed65 ms
14 days agoHandshake completed68 ms
16 days agoHandshake completed104 ms
19 days agoHandshake completed71 ms
21 days agoHandshake completed75 ms
24 days agoHandshake completed98 ms
26 days agoHandshake completed66 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

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 OneUptime and makes no claim about it beyond what these checks measured.