Skip to main content

CronSpell

dev.workers.mike-tusa.cronspell/cronspellVersion 0.1.0

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

Status

Responds145 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:28 UTC
Latency
145 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://cronspell.mike-tusa.workers.dev/mcpResponds145 ms
No sign-in

Claude Code

claude mcp add --transport http cronspell https://cronspell.mike-tusa.workers.dev/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: cronspell
Remote MCP server URL: https://cronspell.mike-tusa.workers.dev/mcp

Cursor

{
  "mcpServers": {
    "cronspell": {
      "url": "https://cronspell.mike-tusa.workers.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"cronspell","type":"http","url":"https://cronspell.mike-tusa.workers.dev/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

4 tools

Tools of CronSpell
Read-only
Idempotent
Open world
cron_runs_betweenList every run of a cron expression between start and end (both inclusive) in an IANA time zone, DST-aware, oldest first. Default limit 20, max 100; truncated is true when there are more. Read-only. Same engine as GET /api/between.NoYesYesNo
explain_cronExplain a cron expression in plain English, e.g. "0 9 * * 1-5" → "At 09:00, on Monday through Friday." Also returns notes on cron rules that often surprise people (day-of-month OR day-of-week, seconds field, shorthand expansion). Invalid expressions return isError with the reason. Read-only. Same engine as GET /api/explain.NoYesYesNo
next_cron_runsList the next (or, with direction "previous", the most recent past) run times of a cron expression in an IANA time zone, DST-aware. Each run has the local time with its UTC offset, the UTC time, unix seconds and weekday. Default 5 runs, max 20; searches up to 50 years. Read-only. Same engine as GET /api/next and GET /api/previous.NoYesYesNo
validate_cronCheck whether a cron expression is valid. Returns valid true with the expanded values of every field (minute, hour, day of month, month, day of week, and seconds for 6-field expressions), or valid false with an error code, the field at fault and a message. Detects schedules that can never run (e.g. February 30). Read-only. Same engine as GET /api/validate.NoYesYesNo

Details

Registry status
Active
Published
Oct 22, 2026
Updated
Oct 22, 2026
Repository
Not given
Categories
Uncategorized
GDPR
Not declared

Are you the operator? Claim this listing