Tick MCP Server

by clawhard Your server? Claim it

answering

Tick is answering right now. Last checked 14 min ago. It exposes 2 tools.

Next cron run times in any IANA timezone, with DST gap and fold warnings.

Uptime history 26 hours of history

26 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

150 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Tick every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tick --transport http https://tick.clawhard.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://tick.clawhard.com/mcp

~/.codex/config.toml

[mcp_servers.tick]
url = "https://tick.clawhard.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "tick": {
      "url": "https://tick.clawhard.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "tick": {
      "type": "http",
      "url": "https://tick.clawhard.com/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.

tick

tick_matches

Use when you need a yes/no on whether a cron expression would fire at a specific instant in a timezone — for example before shipping a schedule that crosses a DST transition, or to verify a single expected fire. Example: {"expression":"0 9 * * 1-5","timezone":"America/New_York","at":"2026-11-06T14:00:00Z"}. Returns fires true/false, the local wall time of that instant, and DST notes if the local time is in a gap or fold.

tick_next_runs

Use when you or the user just wrote a cron expression (GitHub Actions, Vercel cron, Cloudflare Cron Triggers, systemd, an agent schedule) and need the next fire times before claiming it is correct. Pass the expression and an IANA timezone (default UTC). Returns the next N runs as local wall times and UTC ISO, a plain-English field breakdown, and DST gap/fold warnings (spring-forward skips, fall-back double fires). Example: {"expression":"0 9 * * 1-5","timezone":"America/New_York","count":5}. Do not guess next runs yourself — DST rules differ by region and year. Not for converting a meeting time across cities (use Meridian) or for email DNS (use Stamp).

Endpoints

URL	Transport	State	Latency	Checked
https://tick.clawhard.com/mcp	streamable-http	answering	121 ms	14 min ago

Alternatives to Tick

same job, measured the same way

CronSpell

by workers-mike-tusa-cronspell

Validate and explain cron expressions; list next/previous run times in any time zone, DST-aware.

4 tools answering

Timezone MCP

by mukundakatta

IANA timezone conversions with real DST rules.

53 installs/wk local only

Cron Schedule MCP

by mrfentmen

Cron expression helper: explain a schedule in plain words and list its next run times, with

183 installs/wk local only

Clockport

by cloudcorprecords

Current time and timezone conversion for any IANA zone.

98 installs/wk local only

Cron Explainer

by idoazacalls

Cron expression parser: explains any cron + returns next N fire times. Timezone-aware.

1 tools answering

Time MCP Server

by lchinglen

MCP server for timezone conversions and time queries with support for IANA timezones

127 installs/wk local only

Temporal MCP Server

by jordanburke

Time, timezone and duration tools — IANA zones, conversion, DST-correct date arithmetic.

110 installs/wk 5 tools answering

IANA Zones

by sadri-dridi

Common IANA timezone names for clock calls.

30 tools answering

Tick — questions

Answers built from our own checks of this server.

What can Tick do?

It exposes 2 tools, read directly from the server on our last check. Among them: tick_matches, tick_next_runs. 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 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 150 ms. The bar chart above shows every period we have measured.

How do I connect Tick?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Tick need an API key?

No. Tick 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?

It answers our handshake in 150 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.