mcpbeat

Cron Parser API MCP Server

io.github.Br0ski777/cron-parser
answering

Cron Parser API is answering right now. Last checked 15 min ago. It exposes 1 tools. Last commit 18 Jul 2026.

Parse, validate and explain cron expressions. Get next run times. x402 micropayment.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
32 ms
Response time
average over 24h
1
Stars
last commit 18 Jul 2026

Connect this server

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

run in your terminal
claude mcp add cron-parser --transport http https://cron-parser.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cron-parser": {
      "url": "https://cron-parser.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.cron-parser]
url = "https://cron-parser.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "cron-parser": {
      "url": "https://cron-parser.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "cron-parser": {
      "url": "https://cron-parser.api.klymax402.com/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.

schedule
schedule_parse_cron
Use this when you need to parse, validate, or explain a cron expression. Returns human-readable description, next N execution times, and field breakdown. Supports standard 5-field cron and extended 6-field (with seconds). Do NOT use for scheduling tasks — use api_test_webhook instead. Do NOT use for JSON validation — use data_validate_json instead.

Endpoints

URLTransportStateLatencyChecked
https://cron-parser.api.klymax402.com/mcp sse answering 36 ms 15 min ago

Cron Parser API — questions

Answers built from our own checks of this server.

What can Cron Parser API do?
It exposes 1 tools, read directly from the server on our last check. Among them: schedule_parse_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 Parser API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 32 ms. The bar chart above shows every period we have measured.
How do I connect Cron Parser API?
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 Parser API need an API key?
No. Cron Parser API 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 Parser API?
It answers our handshake in 32 ms on average, which is faster than 99% 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 Parser API open source?
Yes — it is published under the MIT licence, written in TypeScript and 1 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.