Next cron run times in any IANA timezone, with DST gap and fold warnings.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
ISO datetime to test, e.g. 2026-11-06T14:00:00Z.
Cron expression (5 or 6 fields, or a nickname like @hourly).
IANA timezone. Default UTC.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http tick https://tick.clawhard.com/mcp
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.
| Argument | Type | Description |
|---|---|---|
| at* | string | ISO datetime to test, e.g. 2026-11-06T14:00:00Z. |
| timezone | string | IANA timezone. Default UTC. |
| expression* | string | Cron expression (5 or 6 fields, or a nickname like @hourly). |
{
"type": "object",
"required": [
"expression",
"at"
],
"properties": {
"at": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "ISO datetime to test, e.g. 2026-11-06T14:00:00Z."
},
"timezone": {
"type": "string",
"maxLength": 80,
"description": "IANA timezone. Default UTC."
},
"expression": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Cron expression (5 or 6 fields, or a nickname like @hourly)."
}
}
}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).
| Argument | Type | Description |
|---|---|---|
| from | string | Optional ISO datetime to start from (default now), e.g. 2026-03-07T12:00:00Z. |
| count | integer | How many next runs to return (1–20). Default 5. |
| timezone | string | IANA timezone for local wall times, e.g. America/New_York. Default UTC. |
| expression* | string | Cron expression: 5 fields (minute hour day-of-month month day-of-week) or 6 with seconds first. Also accepts @hourly, @daily, @weekly, @monthly, @yearly. |
{
"type": "object",
"required": [
"expression"
],
"properties": {
"from": {
"type": "string",
"maxLength": 40,
"description": "Optional ISO datetime to start from (default now), e.g. 2026-03-07T12:00:00Z."
},
"count": {
"type": "integer",
"maximum": 20,
"minimum": 1,
"description": "How many next runs to return (1–20). Default 5."
},
"timezone": {
"type": "string",
"maxLength": 80,
"description": "IANA timezone for local wall times, e.g. America/New_York. Default UTC."
},
"expression": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Cron expression: 5 fields (minute hour day-of-month month day-of-week) or 6 with seconds first. Also accepts @hourly, @daily, @weekly, @monthly, @yearly."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 6, 2026.