Remote MCP · Endpoint

ChronoKey MCP server

No. ChronoKey answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://bot.chronokey.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Dyln01/chronokey
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
464 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
MCP tools: timestamps, UUID v4, gas prices, domain WHOIS, text extraction, and persistent memory.
Listing
From the official MCP registry (active).
Recent checks of ChronoKey
CheckedResultHandshake
18 minutes agoHandshake completed464 ms
9 days agoHandshake completed223 ms
9 days agoHandshake completed331 ms
11 days agoHandshake completed135 ms
12 days agoHandshake completed275 ms
13 days agoHandshake completed256 ms
14 days agoHandshake completed154 ms
14 days agoHandshake completed271 ms
16 days agoHandshake completed113 ms
19 days agoHandshake completed243 ms
21 days agoHandshake completed179 ms
24 days agoHandshake completed444 ms
26 days agoHandshake completed129 ms
28 days agoHandshake completed57 ms

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

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 ChronoKey and makes no claim about it beyond what these checks measured.