Cron Translator
com.crontoenglish/cron-translatorVersion 0.1.0Explain cron expressions in English, list next run times, and catch scheduling gotchas.
Status
Responds213 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:52 UTC
- Latency
- 213 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://crontoenglish.com/api/mcpResponds213 msNo sign-in
Claude Code
claude mcp add --transport http cron-translator https://crontoenglish.com/api/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: cron-translator
Remote MCP server URL: https://crontoenglish.com/api/mcpCursor
{
"mcpServers": {
"cron-translator": {
"url": "https://crontoenglish.com/api/mcp"
}
}
}VS Code
code --add-mcp '{"name":"cron-translator","type":"http","url":"https://crontoenglish.com/api/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
build_cronConvert an English schedule description into a standard five-field cron expression, then explain and validate the result.
Use this when a user describes a schedule in words and needs the expression. This is a RULE-BASED converter, not a language model: it handles a fixed grammar and returns an error listing the supported phrasings when a phrase falls outside it. That refusal is deliberate — a plausible-looking wrong schedule is worse than no answer. If a phrase is rejected, rephrase it into one of the supported shapes and call again.
Returns the expression, which rule matched, any words the rules did not use (check these — leftover words may mean the phrase was misread), the English description of the result, warnings, and the next run times. | Not declared | Yes | Not declared | No |
explain_cronTranslate a cron expression into plain English, list its upcoming run times in a specific timezone, and report the gotchas that make schedules misfire.
Use this whenever a cron expression needs to be read, verified, or explained — and prefer it over reasoning about the expression directly. Cron has several counter-intuitive rules that are easy to get wrong: day-of-month and day-of-week are combined with OR (not AND) when both are set, steps like */7 do not divide their field evenly, dates like February 30 never fire at all, and daylight-saving transitions skip or repeat runs. This tool checks all of them.
Returns the normalised expression, a one-sentence description, a per-field breakdown, a list of warnings with severity and a fix for each, the next run times as both UTC ISO 8601 instants and local wall-clock strings, and an approximate runs-per-day figure. | Not declared | Yes | Not declared | No |
next_cron_runsList the next run times for a cron expression in a specific timezone, with no prose.
Use this when the only question is "when does this next fire" — for example to check whether a job will run before a deadline, or to show a user their upcoming schedule. Do not compute these dates yourself: weekday arithmetic, month lengths, and daylight-saving shifts make manual calculation unreliable.
Returns each run as a UTC ISO 8601 instant plus a local wall-clock rendering in the requested timezone. Refuses Quartz-only syntax (L, W, #, ?) rather than guessing. | Not declared | Yes | Not declared | No |
Details
- Registry status
- Active
- Published
- Sep 2, 2026
- Updated
- Sep 2, 2026
- Categories
- Uncategorized
- GDPR
- Not declared