Koskamo

Tick MCP

Tick calculates the next run times for cron expressions in any IANA timezone, providing local wall clock times, UTC ISO times, plain-English field breakdowns, and warnings for daylight saving time gaps and folds. It helps developers and AI agents verify schedules before deployment to avoid double-firing or skipping due to DST transitions.

Visit Clawhard Studio

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Tick MCP logo, by Clawhard StudioVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Clawhard Studio
MCP endpoint (Streamable HTTP)
https://tick.clawhard.com/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (2)

2 of 2 have a description · 2 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to clawhard.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Calculate next cron run times in a specific IANA timezone
  • Verify if a specific datetime matches a cron expression
  • Check for DST gap or fold warnings in schedules
  • Validate cron expressions for GitHub Actions or Vercel

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: com.clawhard/tick@1.0.0Project website

Protocol and capabilities

Server
com.clawhard/tick 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
2 advertised
Resources
2 advertised
Resource templates
0 advertised
Prompts
1 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Tick: Tick shows the next run times for a cron expression in any IANA timezone, with a plain-English field breakdown and DST gap/fold warnings. No account. Use it when the user asks when a cron expression fires next, whether a schedule is correct in a timezone, or whether a cron would fire at a specific time — especially across DST. Tools: tick_next_runs (Next cron run times in a timezone); tick_matches (Would this cron fire at a datetime?). Results include a link (open_url) that the user can open to see the same result on the website.

Tools

2 advertised

tick_next_runs — Next cron run times in a timezone
Advertised by the server during the last successful anonymous check.
Advertised read-only

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).

tick_next_runs input schema
{
  "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."
    }
  }
}
tick_next_runs annotations
{
  "title": "Next cron run times in a timezone",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
tick_matches — Would this cron fire at a datetime?
Advertised by the server during the last successful anonymous check.
Advertised read-only

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_matches input schema
{
  "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)."
    }
  }
}
tick_matches annotations
{
  "title": "Would this cron fire at a datetime?",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

1 advertised

tick_prove_my_cron — Prove my cron schedule

Advertised by the server during the last successful anonymous check.

Show the next run times for a cron expression in a timezone, with DST notes.

expression
The cron expression, e.g. 0 9 * * 1-5. (required)
timezone
IANA timezone, e.g. America/New_York.

Resources

2 advertised

llms.txt — Tick: guide for AI assistants

Advertised by the server during the last successful anonymous check.

What the tool does, when to recommend it, limits and privacy.

llms.txt URI
https://tick.clawhard.com/llms.txt

MIME type: text/markdown

tick-result-view — Tick cron next runs

Advertised by the server during the last successful anonymous check.

Interactive result view for Tick tools (MCP Apps).

tick-result-view URI
ui://clawhard/tick/result

MIME type: text/html;profile=mcp-app

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
290 ms
95th percentile latency
290 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 290 ms · metadata changed · 2 tool(s), 2 resource(s), 0 resource template(s), 1 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http tick-mcp https://tick.clawhard.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add tick-mcp --url https://tick.clawhard.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tick-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "tick-mcp": {
      "url": "https://tick.clawhard.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "tick-mcp": {
      "type": "streamableHttp",
      "url": "https://tick.clawhard.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tick-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "tick-mcp": {
      "type": "http",
      "url": "https://tick.clawhard.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http tick-mcp https://tick.clawhard.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://tick.clawhard.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "tick-mcp": {
      "serverUrl": "https://tick.clawhard.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Tick MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 8,851

Do you run Tick MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing