mcpbeat

Tick MCP Server

io.github.Cocabadger/tick-mcp
answering

Tick MCP is answering right now. Last checked 3 min ago. It exposes 2 tools. Last commit 13 Jul 2026.

A time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies.

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
211 ms
Response time
average over 24h
4
Stars
last commit 13 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add tick-mcp --transport http https://tick-mcp-production.up.railway.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "tick-mcp": {
      "url": "https://tick-mcp-production.up.railway.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.tick-mcp]
url = "https://tick-mcp-production.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "tick-mcp": {
      "url": "https://tick-mcp-production.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "tick-mcp": {
      "url": "https://tick-mcp-production.up.railway.app/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

now
now
Get the REAL current date and time. Call this at the start of a reply and before using any relative time words (yesterday, tomorrow, tonight, next week). Never guess time from context. NEVER write a clock time in your reply that did not come from this tool's output in THIS turn — a timestamp without a fresh call is a hallucination, even if it plausibly continues from an earlier one. ALWAYS pass the user's IANA timezone — this server is remote, so without it you get UTC, not the user's local time.
since
since
How long ago (or from now) a given ISO-8601 timestamp is, in human form ('3h 42m ago'). Use to check whether an event was really 'yesterday'. Include the UTC offset in the timestamp.

Endpoints

URLTransportStateLatencyChecked
https://tick-mcp-production.up.railway.app/mcp streamable-http answering 191 ms 3 min ago

Tick MCP — questions

Answers built from our own checks of this server.

What can Tick MCP do?
It exposes 2 tools, read directly from the server on our last check. Among them: now, since. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Tick MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 211 ms. The bar chart above shows every period we have measured.
How do I connect Tick MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tick MCP need an API key?
No. Tick MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tick MCP?
It answers our handshake in 211 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Tick MCP open source?
Yes — it is published under the MIT licence, written in Python and 4 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.