Remote MCP · Endpoint

Unix seconds to UTC ISO, value discarded MCP server

No. Unix seconds to UTC ISO, value discarded answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/unix-to-iso/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/unix-to-iso
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
25 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Unix seconds to UTC ISO, value discarded
Listing
From the official MCP registry (active).
Recent checks of Unix seconds to UTC ISO, value discarded
CheckedResultHandshake
2 hours agoHandshake completed25 ms
13 hours agoHandshake completed45 ms
1 day agoHandshake completed18 ms
3 days agoHandshake completed21 ms
4 days agoHandshake completed24 ms
4 days agoHandshake completed24 ms
5 days agoHandshake completed15 ms
7 days agoHandshake completed23 ms
8 days agoHandshake completed17 ms
11 days agoHandshake completed29 ms
14 days agoHandshake completed42 ms
16 days agoHandshake completed30 ms
18 days agoHandshake completed21 ms
20 days agoHandshake completed24 ms
22 days agoHandshake completed27 ms
24 days agoHandshake completed31 ms
26 days agoHandshake completed18 ms
28 days agoHandshake completed25 ms
29 days agoHandshake completed22 ms

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

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 Unix seconds to UTC ISO, value discarded and makes no claim about it beyond what these checks measured.