Remote MCP · Endpoint

OhSnap uptime monitoring MCP server

No. OhSnap uptime monitoring answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.ohsnap.io/mcp

The last check completed an MCP handshake.

Registry name
io.ohsnap/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
205 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check if a website is down, add websites to monitor, read outage history and send test alerts.
Listing
From the official MCP registry (active).
Recent checks of OhSnap uptime monitoring
CheckedResultHandshake
1 hour agoHandshake completed205 ms
9 days agoHandshake completed175 ms
10 days agoHandshake completed247 ms
11 days agoHandshake completed218 ms
12 days agoHandshake completed127 ms
14 days agoHandshake completed232 ms
14 days agoHandshake completed688 ms
15 days agoHandshake completed136 ms
17 days agoHandshake completed162 ms
19 days agoHandshake completed145 ms
21 days agoHandshake completed141 ms
24 days agoHandshake completed138 ms
26 days agoHandshake completed169 ms
28 days agoHandshake completed131 ms

The last 14 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 OhSnap uptime monitoring and makes no claim about it beyond what these checks measured.