Tick

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~658Tokens (tool definitions)
~1.6 KBTypical response size
Moderate attention impact (0.51% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://tick.clawhard.com/mcpstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢tick_next_runs(expression, timezone, count, from)

Use when you or the user just wrote a cron expression (GitHub Actions, Vercel cron, Cloudflare Cron Triggers, systemd, an agent schedule) and need its next fire times. 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}. Uses the tz database, so DST rules match the region and year. Not for converting a meeting time across cities (use Meridian) or for email DNS (use Stamp).

Input Schema

{
  "type": "object",
  "properties": {
    "expression": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "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."
    },
    "timezone": {
      "type": "string",
      "maxLength": 80,
      "description": "IANA timezone for local wall times, e.g. America/New_York. Default UTC."
    },
    "count": {
      "type": "integer",
      "minimum": 1,
      "maximum": 20,
      "description": "How many next runs to return (1–20). Default 5."
    },
    "from": {
      "type": "string",
      "maxLength": 40,
      "description": "Optional ISO datetime to start from (default now), e.g. 2026-03-07T12:00:00Z."
    }
  },
  "required": [
    "expression"
  ]
}
🟢tick_matches(expression, timezone, at)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "expression": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "description": "Cron expression (5 or 6 fields, or a nickname like @hourly)."
    },
    "timezone": {
      "type": "string",
      "maxLength": 80,
      "description": "IANA timezone. Default UTC."
    },
    "at": {
      "type": "string",
      "minLength": 1,
      "maxLength": 40,
      "description": "ISO datetime to test, e.g. 2026-11-06T14:00:00Z."
    }
  },
  "required": [
    "expression",
    "at"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools