Remote MCP · Endpoint

Outage.Me MCP server

No. Outage.Me answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://outage.me/mcp

The last check completed an MCP handshake.

Registry name
io.github.marcioyoshida/outage-me
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
343 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA
Listing
From the official MCP registry (active).
Recent checks of Outage.Me
CheckedResultHandshake
1 day agoHandshake completed343 ms
3 days agoHandshake completed385 ms
5 days agoHandshake completed408 ms
7 days agoHandshake completed403 ms
9 days agoHandshake completed356 ms
11 days agoHandshake completed333 ms
12 days agoHandshake completed342 ms
13 days agoHandshake completed201 ms
14 days agoHandshake completed228 ms
17 days agoHandshake completed220 ms
19 days agoHandshake completed188 ms
20 days agoHandshake completed56 ms
21 days agoHandshake completed186 ms
22 days agoHandshake completed167 ms

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

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