Remote MCP · Endpoint

io.github.Cocabadger/tick-mcp MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://tick-mcp-production.up.railway.app/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.Cocabadger/tick-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
64.7% from 17 checks
Described by its publisher as
A time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies.
Listing
From the official MCP registry (active).
Recent checks of io.github.Cocabadger/tick-mcp
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoHandshake completed115 ms
12 days agoHandshake completed121 ms
13 days agoHandshake completed116 ms
15 days agoHandshake completed117 ms
17 days agoHandshake completed121 ms
18 days agoHandshake completed123 ms
19 days agoHandshake completed104 ms
20 days agoHandshake completed107 ms
20 days agoHandshake completed131 ms
21 days agoHandshake completed118 ms
23 days agoHandshake completed110 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 io.github.Cocabadger/tick-mcp and makes no claim about it beyond what these checks measured.