Remote MCP · Endpoint
UTC hour 0-23 band MCP server
No. UTC hour 0-23 band answered an MCP handshake 35 minutes ago.
UpLast checked 35 minutes ago
Server URL
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/hour-ok/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.sadri-dridi/hour-ok
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 37 ms
- Tools exposed
- 31 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- UTC hour 0-23 band
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 35 minutes ago | Handshake completed | 37 ms |
| 2 days ago | Handshake completed | 25 ms |
| 4 days ago | Handshake completed | 12 ms |
| 5 days ago | Handshake completed | 14 ms |
| 7 days ago | Handshake completed | 16 ms |
| 8 days ago | Handshake completed | 92 ms |
| 9 days ago | Handshake completed | 15 ms |
| 12 days ago | Handshake completed | 19 ms |
| 13 days ago | Handshake completed | 30 ms |
| 15 days ago | Handshake completed | 31 ms |
| 17 days ago | Handshake completed | 16 ms |
| 18 days ago | Handshake completed | 10 ms |
| 19 days ago | Handshake completed | 20 ms |
| 20 days ago | Handshake completed | 49 ms |
| 20 days ago | Handshake completed | 51 ms |
| 21 days ago | Handshake completed | 17 ms |
| 23 days ago | Handshake completed | 14 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 UTC hour 0-23 band and makes no claim about it beyond what these checks measured.