Cron Translator is a remote MCP server that gives an AI agent 3 tools, among them build_cron, explain_cron, next_cron_runs. It answers at https://crontoenglish.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 11 of 11 times since 3 September 2026; the last check, on 19 October 2026, succeeded.
Explain cron expressions in English, list next run times, and catch scheduling gotchas.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
build_cron | 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 lan Inputs: phrase, timezone |
explain_cron | 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 prefe Inputs: expression, timezone, count |
next_cron_runs | 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 upco Inputs: expression, timezone, count |
Every block below points at https://crontoenglish.com/api/mcp. Pick your client and copy.
claude mcp add --transport http cron-translator https://crontoenglish.com/api/mcp
{
"mcpServers": {
"cron-translator": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://crontoenglish.com/api/mcp"]
}
}
}{
"mcpServers": {
"cron-translator": {
"url": "https://crontoenglish.com/api/mcp"
}
}
}{
"servers": {
"cron-translator": {
"type": "http",
"url": "https://crontoenglish.com/api/mcp"
}
}
}{
"context_servers": {
"cron-translator": {
"url": "https://crontoenglish.com/api/mcp"
}
}
}{
"mcpServers": {
"cron-translator": {
"serverUrl": "https://crontoenglish.com/api/mcp"
}
}
}{
"mcpServers": {
"cron-translator": {
"url": "https://crontoenglish.com/api/mcp"
}
}
}name: Cron Translator
version: 0.0.1
schema: v1
mcpServers:
- name: Cron Translator
type: streamable-http
url: https://crontoenglish.com/api/mcp{
"mcpServers": {
"cron-translator": {
"httpUrl": "https://crontoenglish.com/api/mcp"
}
}
}{
"mcpServers": {
"cron-translator": {
"type": "http",
"url": "https://crontoenglish.com/api/mcp"
}
}
}{
"mcpServers": {
"cron-translator": {
"url": "https://crontoenglish.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fcrontoenglish.com%2Fapi%2Fmcp&type=streamable_http&id=cron-translator&name=Cron%20Translator
It answered our last check on 19 October 2026 in 956 ms. Over 11 checks since 3 September 2026 it answered 11. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by crontoenglish.com and served from crontoenglish.com, the vendor's own domain: https://crontoenglish.com/api/mcp.
3, as returned by the server's own tools/list on 2 September 2026: build_cron, explain_cron, next_cron_runs.
It answered our last check on 19 October 2026 in 956 ms. Over 11 checks since 3 September 2026 it answered 11.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://crontoenglish.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.crontoenglish. Endpoint host: crontoenglish.com. ARD identifier: urn:air:com.crontoenglish:mcp:cron-translator.
First indexed 2 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.