CronSpell

Name: CronSpell
Author: dev.workers.mike-tusa.cronspell

MCP serverMCP

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

by dev.workers.mike-tusa.cronspellhomepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cronspell","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability11/11 checks ok

30 days ago

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	30 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools
12 h ago	mcp initialize	ok	200	72 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools
19 h ago	mcp initialize	ok	200	51 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools
25 h ago	mcp initialize	ok	200	56 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools
32 h ago	mcp initialize	ok	200	33 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	43 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	66 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	11 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools
3 d ago	mcp initialize	ok	200	93 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools
3 d ago	mcp initialize	ok	200	81 ms	server cronspell 0.1.0 · protocol 2025-06-18 · 4 tools

Tools observed via MCP handshake

validate_cron — Check 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 second
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 peop
next_cron_runs — List 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
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 i

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrydev.workers.mike-tusa.cronspell/cronspell

first seen 3 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

3 d ago · declared · summary → "Validate and explain cron expressions; list next/previous run times in any time zone, DST-aware."
3 d ago · declared · description → "Validate and explain cron expressions; list next/previous run times in any time zone, DST-aware."
3 d ago · declared · publisherName → "dev.workers.mike-tusa.cronspell"
3 d ago · declared · homepageUrl → "https://cronspell.mike-tusa.workers.dev/"
3 d ago · declared · version → "0.1.0"
3 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from