Search / com.crontoenglish/cron-translator
protogridR0· no sign-inExplain cron expressions in English, list next run times, and catch scheduling gotchas.
v0.1.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"cron-translator": {
"type": "http",
"url": "https://crontoenglish.com/api/mcp"
}
}
}claude mcp add --transport http cron-translator https://crontoenglish.com/api/mcp[mcp_servers.cron-translator]
url = "https://crontoenglish.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cron-translator": {
"type": "remote",
"url": "https://crontoenglish.com/api/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"cron-translator": {
"type": "http",
"url": "https://crontoenglish.com/api/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=cron-translator&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vY3JvbnRvZW5nbGlzaC5jb20vYXBpL21jcCJ9"
}{
"servers": {
"cron-translator": {
"type": "http",
"url": "https://crontoenglish.com/api/mcp"
}
}
}{
"mcpServers": {
"cron-translator": {
"httpUrl": "https://crontoenglish.com/api/mcp"
}
}
}extensions:
"cron-translator":
enabled: true
name: "cron-translator"
type: streamable_http
uri: "https://crontoenglish.com/api/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every useauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations3 of 3 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: next_cron_runs (destructiveHint, idempotentHint); explain_cron (destructiveHint, idempotentHint); build_cron (destructiveHint, idempotentHint)tools.token_costabout 1,210 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +website +reachable +uptime-100% ~updated-48d-ago -duplicate-repo(16 names)
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://crontoenglish.com/api/mcp streamable-http | none | yes | 100% | 822 ms | 2026-07-28 | 2026-10-20 |
build_cronread-only | Convert 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. |
explain_cronread-only | Translate 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. |
next_cron_runsread-only | List 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. |
Schemas: list_tools.
15 other active names share this repository (showing 10): com.gumballtools/amortize, com.gumballtools/body-metrics, com.gumballtools/check-digit, com.gumballtools/color-companion, com.gumballtools/due-date, com.gumballtools/equation-steps, com.gumballtools/iso-week, com.gumballtools/json-to-types, com.gumballtools/payload-validator, com.gumballtools/penny-rounding
{
"name": "com.crontoenglish/cron-translator",
"title": "Cron Translator",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://crontoenglish.com/api/mcp",
"type": "streamable-http"
}
],
"version": "0.1.0",
"repository": {
"url": "https://github.com/bwalvoord/gumball",
"source": "github"
},
"websiteUrl": "https://crontoenglish.com",
"description": "Explain cron expressions in English, list next run times, and catch scheduling gotchas."
}