Remote MCP · Endpoint

World Time MCP server

No. World Time answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://invokera.com/r/world-time

The last check completed an MCP handshake.

Registry name
com.invokera/world-time
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
681 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Current time in any IANA time zone, plus the full time-zone list. Via timeapi.io.
Listing
From the official MCP registry (active).
Recent checks of World Time
CheckedResultHandshake
1 hour agoHandshake completed681 ms
2 days agoHandshake completed147 ms
4 days agoHandshake completed140 ms
5 days agoHandshake completed139 ms
7 days agoHandshake completed161 ms
8 days agoHandshake completed478 ms
9 days agoHandshake completed134 ms
12 days agoHandshake completed125 ms
13 days agoHandshake completed172 ms
15 days agoHandshake completed92 ms
17 days agoHandshake completed100 ms
18 days agoHandshake completed90 ms
19 days agoHandshake completed91 ms
20 days agoHandshake completed91 ms
20 days agoHandshake completed97 ms
21 days agoHandshake completed94 ms
23 days agoHandshake completed103 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 World Time and makes no claim about it beyond what these checks measured.