Remote MCP · Endpoint

Time & Astronomy MCP server

No. Time & Astronomy answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://time.memoryapi.org/mcp

The last check completed an MCP handshake.

Registry name
org.memoryapi/time
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
464 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Current time by timezone, astronomy events, and moon phases
Listing
From the official MCP registry (active).
Recent checks of Time & Astronomy
CheckedResultHandshake
5 hours agoHandshake completed464 ms
2 days agoHandshake completed400 ms
4 days agoHandshake completed79 ms
5 days agoHandshake completed79 ms
7 days agoHandshake completed91 ms
8 days agoHandshake completed92 ms
9 days agoHandshake completed91 ms
12 days agoHandshake completed71 ms
13 days agoHandshake completed67 ms
15 days agoHandshake completed130 ms
16 days agoHandshake completed81 ms
17 days agoHandshake completed58 ms
18 days agoHandshake completed74 ms
19 days agoHandshake completed65 ms
20 days agoHandshake completed75 ms
21 days agoHandshake completed100 ms
22 days agoHandshake completed167 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 Time & Astronomy and makes no claim about it beyond what these checks measured.