Remote MCP · Endpoint

Pingoru status MCP server

No. Pingoru status answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://pingoru.io/api/mcp-public/

The last check completed an MCP handshake.

Registry name
io.pingoru/status
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
163 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live status, incidents and maintenance windows for 8,000+ cloud and SaaS status pages.
Listing
From the official MCP registry (active).
Recent checks of Pingoru status
CheckedResultHandshake
42 minutes agoHandshake completed163 ms
3 days agoHandshake completed304 ms
12 days agoHandshake completed165 ms
12 days agoHandshake completed263 ms
14 days agoHandshake completed270 ms
15 days agoHandshake completed152 ms
16 days agoHandshake completed273 ms
17 days agoHandshake completed164 ms
18 days agoHandshake completed284 ms
19 days agoHandshake completed547 ms
22 days agoHandshake completed128 ms
25 days agoHandshake completed266 ms
27 days agoHandshake completed360 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 Pingoru status and makes no claim about it beyond what these checks measured.