MCP.Market

Cron Explainer MCP server

online · 100% uptime
by IdoAzaCalls·io.github.IdoAzaCalls/cron-explainer·v0.1.2

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

B81/100grade B
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Cron Explainer yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cron Explainer tools (1)

write = sends, deletes, buys or posts
  • explain_cronFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 581ms20/20
  • Tool poisoning1 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 157 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Cron Explainer compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
81/100
higher than 62% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
58 ms
faster than 91% of 30,031 servers

What its tools let an agent do: 1 read

Install Cron Explainer in Claude Code, Cursor or VS Code

claude mcp add --transport http cron-explainer https://cron-explainer.cron-explainer-prod.workers.dev/mcp
Add to Cursor

What the publisher says

From the Cron Explainer repository's README, as published. We do not edit it. Read it on GitHub

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

  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.
  3. 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

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 to UTC.
  • n clamps to [1, 100].
  • Best-effort accuracy. See /legal/disclaimer for 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.

Nothing above is checked by us. What we check is on the safety report.

Cron Explainer: common questions

Is Cron Explainer MCP server safe?
Mostly: it is graded B (81/100). Read the Cron Explainer safety report
How do I install Cron Explainer?
It runs remotely at cron-explainer.cron-explainer-prod.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Cron Explainer need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Cron Explainer maintained?
The last commit was 195 days ago (2026-04-23). The latest release is v0.1.2.
Is Cron Explainer up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Cron Explainer compare with other MCP servers?
safety score 81/100 (higher than 62% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.