Remote MCP · Endpoint

Whether current UTC month is DST-heavy in the US MCP server

No. Whether current UTC month is DST-heavy in the US answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/dst-hint-utc/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/dst-hint-utc
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
48 ms
Tools exposed
30 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Whether current UTC month is DST-heavy in the US
Listing
From the official MCP registry (active).
Recent checks of Whether current UTC month is DST-heavy in the US
CheckedResultHandshake
1 hour agoHandshake completed48 ms
21 hours agoHandshake completed132 ms
2 days agoHandshake completed16 ms
3 days agoHandshake completed36 ms
4 days agoHandshake completed16 ms
5 days agoHandshake completed22 ms
6 days agoHandshake completed70 ms
8 days agoHandshake completed18 ms
11 days agoHandshake completed28 ms
13 days agoHandshake completed42 ms
16 days agoHandshake completed37 ms
18 days agoHandshake completed16 ms
20 days agoHandshake completed16 ms
22 days agoHandshake completed13 ms
24 days agoHandshake completed17 ms
26 days agoHandshake completed17 ms
27 days agoHandshake completed15 ms
29 days agoHandshake completed18 ms

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

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 Whether current UTC month is DST-heavy in the US and makes no claim about it beyond what these checks measured.