CronSpell
v0.1.0Validate and explain cron expressions; list next/previous run times in any time zone, DST-aware.
Endpoint health
online- Last checked
- 11/3/2026, 5:19:09 PM
- Latency
- 360 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:dev.workers.mike-tusa.cronspell%2Fcronspell
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"dev.workers.mike-tusa.cronspell/cronspell": {
"url": "https://cronspell.mike-tusa.workers.dev/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
4 shown · authentication unknown
List cron runs between two times
cron_runs_between
List 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.
Schema valid · SHA-256 bf15cf1b9503…
View input schema
{ "type": "object", "properties": { "expression": { "type": "string", "minLength": 1, "maxLength": 200, "description": "Cron expression, e.g. \"0 9 * * 1-5\", \"*/15 * * * *\", \"0 30 8 * * *\" (6 fields = leading seconds) or \"@daily\"." }, "timezone": { "type": "string", "minLength": 1, "maxLength": 64, "pattern": "^[A-Za-z0-9_+\\-/]+$", "default": "UTC", "description": "IANA time zone the schedule runs in, e.g. \"America/Denver\", \"Europe/London\". Default UTC." }, "start": { "type": "string", "minLength": 1, "maxLength": 40, "description": "Window start (inclusive). ISO 8601 with Z or an offset (2026-11-01T09:00:00Z), a local time read in the time zone (2026-11-01T09:00), or unix seconds." }, "end": { "type": "string", "minLength": 1, "maxLength": 40, "description": "Window end (inclusive). ISO 8601 with Z or an offset (2026-11-01T09:00:00Z), a local time read in the time zone (2026-11-01T09:00), or unix seconds." }, "limit": { "type": "integer", "minimum": 1, "maximum": 100, "default": 20, "description": "Max runs to return (1-100)." } }, "required": [ "expression", "start", "end" ], "additionalProperties": false }Explain a cron expression
explain_cron
Explain 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.
Connections
streamable-http
https://cronspell.mike-tusa.workers.dev/mcp