CronSpell

dev.workers.mike-tusa.cronspell/cronspell · v0.1.0 · productivity

CronSpell is healthy: it completed an MCP handshake in 857 ms and exposes 4 tools.

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

Endpoint: https://cronspell.mike-tusa.workers.dev/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count4
Latency857 ms
Last checked (UTC)2026-10-22T10:45:13.967Z

Health history

Checked (UTC)StatusLatencyError
2026-10-22T10:45:13.967ZHealthy857

Tools (4)

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