Remote MCP · Endpoint

CountLink MCP server

No. CountLink answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://countlink.app/mcp

The last check completed an MCP handshake.

Registry name
app.countlink/countdown
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
119 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Shared countdown timers that stay in sync on every screen — no account, any number of viewers.
Listing
From the official MCP registry (active).
Recent checks of CountLink
CheckedResultHandshake
6 hours agoHandshake completed119 ms
2 days agoHandshake completed96 ms
4 days agoHandshake completed66 ms
5 days agoHandshake completed88 ms
7 days agoHandshake completed153 ms
8 days agoHandshake completed147 ms
9 days agoHandshake completed101 ms
12 days agoHandshake completed71 ms
13 days agoHandshake completed52 ms
15 days agoHandshake completed117 ms
16 days agoHandshake completed51 ms
17 days agoHandshake completed59 ms
18 days agoHandshake completed52 ms
19 days agoHandshake completed43 ms
20 days agoHandshake completed140 ms
21 days agoHandshake completed62 ms
22 days agoHandshake completed86 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 CountLink and makes no claim about it beyond what these checks measured.