mcpbeat

Cron Explainer MCP Server

io.github.IdoAzaCalls/cron-explainer
answering

Cron Explainer is answering right now. Last checked 1 min ago. It exposes 1 tools. Last commit 23 Apr 2026.

Cron expression parser: explains any cron + returns next N fire times. Timezone-aware.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
1
Tools
read from the server
82 ms
Response time
average over 24h
0
Stars
last commit 23 Apr 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add cron-explainer --transport http https://cron-explainer.cron-explainer-prod.workers.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cron-explainer": {
      "url": "https://cron-explainer.cron-explainer-prod.workers.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.cron-explainer]
url = "https://cron-explainer.cron-explainer-prod.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "cron-explainer": {
      "url": "https://cron-explainer.cron-explainer-prod.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "cron-explainer": {
      "url": "https://cron-explainer.cron-explainer-prod.workers.dev/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

explain
explain_cron
Parse a POSIX/Vixie cron expression and return the next N fire times plus an English description. Timezone-aware (IANA). Best-effort accuracy. Billed at 1 EUR cent per successful call; non-2xx responses are refunded.

Endpoints

URLTransportStateLatencyChecked
https://cron-explainer.cron-explainer-prod.workers.dev/mcp streamable-http answering 100 ms 1 min ago

Cron Explainer — questions

Answers built from our own checks of this server.

What can Cron Explainer do?
It exposes 1 tools, read directly from the server on our last check. Among them: explain_cron. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Cron Explainer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 82 ms. The bar chart above shows every period we have measured.
How do I connect Cron Explainer?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Cron Explainer need an API key?
No. Cron Explainer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Cron Explainer?
It answers our handshake in 82 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Cron Explainer open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.