
Cron Explainer
- Updated April 23, 2026
- IdoAzaCalls/cron-explainer
A tiny pay-per-call API that parses cron expressions, returns the next N fire.
About
A tiny pay-per-call API that parses cron expressions, returns the next N fire. A tiny pay-per-call API that parses cron expressions, returns the next N fire times, and produces a short English description. Timezone-aware (IANA). **Live:** https://cron-explainer.cron-explainer-prod.workers.dev/ **Pricing:** 0.01 EUR per successful call, prepaid via Stripe Checkout in packs of 500 / 5,000 / 50,000 calls. Non-2xx responses are refunded. No subscription. Keys never expire. 1. Get a key at https://cron-explainer.cron-explainer-prod.workers.dev/ (Stripe Checkout, €5 minimum).
- A tiny pay-per-call API that parses cron expressions, returns the next N fire
- times, and produces a short English description. Timezone-aware (IANA).
- **Live:** https://cron-explainer.cron-explainer-prod.workers.dev/
- 1. Get a key at https://cron-explainer.cron-explainer-prod.workers.dev/ (Stripe Checkout, €5 minimum).
- 2. Copy the key - it's shown exactly once.
Cron Explainer by the numbers
- Exposes 1 verified tools (MCP introspection)
- Data as of Jul 9, 2026 (Skillselion catalog sync)
claude mcp add --transport http cron-explainer https://cron-explainer.cron-explainer-prod.workers.dev/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
| Tools | 1 |
| Last updated | April 23, 2026 |
| Repository | IdoAzaCalls/cron-explainer ↗ |
How do agents access cron-explainer capabilities without custom integration code?
A tiny pay-per-call API that parses cron expressions, returns the next N fire
Who is it for?
Developers wiring cron-explainer into Cursor, Claude Desktop, or other MCP clients.
Skip if: Teams that need features outside the documented cron-explainer tool surface.
What you get
Configured MCP host can call cron-explainer tools with schemas from the server README.
- Human-readable explanation of a cron expression
- List of next N scheduled execution instants in the chosen timezone
By the numbers
- [object Object]
Cron Explainer capabilities & compatibility
- Capabilities
- a tiny pay per call api that parses cron express · times, and produces a short english description. · **live:** https://cron explainer.cron explainer · 1. get a key at https://cron explainer.cron expl
- Use cases
- api development · orchestration
- Runs
- Local or remote
- Pricing
- Bring your own API key
Tools 1
Public tool metadata - what this server can do for an agent.
explain_cron3 paramsParse 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.
cronstringrequiredPOSIX/Vixie cron expression (5 fields, e.g. '*/15 * * * *').tzstringIANA timezone (e.g. 'Europe/Lisbon'). Defaults to UTC.nintegerNumber of upcoming fire times to return.
README.md
cron-explainer
A tiny pay-per-call API that parses cron expressions, returns the next N fire times, and produces a short English description. Timezone-aware (IANA).
Live: https://cron-explainer.cron-explainer-prod.workers.dev/ Pricing: 0.01 EUR per successful call, prepaid via Stripe Checkout in packs of 500 / 5,000 / 50,000 calls. Non-2xx responses are refunded. No subscription. Keys never expire.
Quick start
- Get a key at https://cron-explainer.cron-explainer-prod.workers.dev/ (Stripe Checkout, €5 minimum).
- Copy the key — it's shown exactly once.
- Call the API:
curl -X POST https://cron-explainer.cron-explainer-prod.workers.dev/v1/explain \
-H "content-type: application/json" \
-H "x-api-key: $YOUR_KEY" \
-d '{"cron":"0 9 * * 1-5","tz":"Europe/Lisbon","n":3}'
Response:
{
"input": {"cron":"0 9 * * 1-5","tz":"Europe/Lisbon","n":3},
"valid": true,
"description": "At 09:00, Monday through Friday",
"next": ["2026-04-24T08:00:00.000Z","2026-04-27T08:00:00.000Z","2026-04-28T08:00:00.000Z"],
"flags": {"dst_transition_ahead": false, "ambiguous": false, "notes": []},
"errors": []
}
Check remaining balance:
curl -H "x-api-key: $YOUR_KEY" \
https://cron-explainer.cron-explainer-prod.workers.dev/v1/balance
MCP
The server is listed on the official MCP registry as
io.github.IdoAzaCalls/cron-explainer with a Streamable HTTP endpoint at
POST /mcp. It exposes one tool, explain_cron. Pass your x-api-key as
an HTTP header on the MCP transport; billing is identical to the REST path.
Registry entry: https://registry.modelcontextprotocol.io/v0/servers?search=cron-explainer
Endpoints
| Method | Path | Purpose |
|---|---|---|
POST |
/v1/explain |
Parse + describe + next fire times (billed) |
GET |
/v1/balance |
Remaining balance for an x-api-key |
POST |
/v1/checkout |
Create a Stripe Checkout Session |
GET |
/v1/schema |
JSON Schema for request/response |
POST |
/mcp |
MCP Streamable HTTP (JSON-RPC 2.0) |
GET |
/.well-known/mcp.json |
Static tool manifest |
GET |
/health |
Liveness probe |
GET |
/legal/{tos,privacy,disclaimer,notices} |
Legal docs |
Limits
- Cron: 5-field POSIX/Vixie syntax (minute, hour, day-of-month, month, day-of-week).
- Timezones: IANA names (e.g.
Europe/Lisbon,America/Los_Angeles). Defaults toUTC. nclamps to[1, 100].- Best-effort accuracy. See
/legal/disclaimerfor warranty terms. - Zero PII: inputs are cron strings and IANA timezones only. Request and response bodies are never logged.
Stack
TypeScript on Cloudflare Workers. Cron parsing via
croner (MIT). English descriptions via
cronstrue (MIT). Full NOTICE
text at /legal/notices.
Contact
azariaido@gmail.com — billing issues, bug reports, custom pricing.
Recommended MCP Servers
How it compares
Hosted cron parse-and-preview MCP endpoint, not a self-hosted scheduler or monitoring dashboard.
FAQ
What does cron-explainer do?
A tiny pay-per-call API that parses cron expressions, returns the next N fire.
When should I use cron-explainer?
A tiny pay-per-call API that parses cron expressions, returns the next N fire
Is cron-explainer safe to install?
Review the Security Audits panel on this page before installing in production.