Remote MCP · Endpoint

dev.fly.looper-products/statuspage-incidents MCP server

No. dev.fly.looper-products/statuspage-incidents answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://looper-products.fly.dev/mcp-statuspage/

The last check completed an MCP handshake.

Registry name
dev.fly.looper-products/statuspage-incidents
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
24 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Read-only: recent incidents from public Atlassian Statuspage pages. Free, no API key.
Listing
From the official MCP registry (active).
Recent checks of dev.fly.looper-products/statuspage-incidents
CheckedResultHandshake
1 day agoHandshake completed24 ms
5 days agoHandshake completed35 ms
16 days agoHandshake completed24 ms
17 days agoHandshake completed55 ms
17 days agoHandshake completed3.88 s
19 days agoHandshake completed3.94 s
20 days agoHandshake completed24 ms
21 days agoHandshake completed4.16 s
22 days agoHandshake completed165 ms
23 days agoHandshake completed39 ms
25 days agoHandshake completed13 ms

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

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 dev.fly.looper-products/statuspage-incidents and makes no claim about it beyond what these checks measured.