Cron Schedule Audit MCP server
not respondingValidates cron expressions and finds DST bugs that make jobs silently skip or double-fire.
0 stars
Reviews
Write oneNobody has reviewed Cron Schedule Audit yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Cron Schedule Audit tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote unreachable: HTTP 5000/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 95 days ago8/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableHTTP 500
How Cron Schedule Audit compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 32/100
- higher than 6% of 48,255 servers
- Uptime
- 21%
- of our recent checks; the typical remote server answers 100%
- Response time
- 715 ms
- faster than 19% of 30,031 servers
Install Cron Schedule Audit in Claude Code, Cursor or VS Code
claude mcp add --transport http cron-schedule-audit-mcp https://cron-schedule-audit-mcp.mcpize.run/mcp
What the publisher says
From the Cron Schedule Audit repository's README, as published. We do not edit it. Read it on GitHub
cron-schedule-audit-mcp
An MCP server that validates cron expressions and computes DST-correct next-fire times using the real IANA timezone database — no moment-timezone or luxon dependency, just a hand-rolled fake-UTC-offset technique against the platform's own tz data.
The bug this catches
A cron job scheduled at 30 2 (2:30am daily) in America/NewYork silently never fires on the spring-forward date, because 2:00-2:59am doesn't exist that day. A job at 30 1 (1:30am) fires twice** on the fall-back date, because that hour is repeated. Neither failure throws an error or shows up in logs — it just looks like a flaky cron that "sometimes doesn't run." Verified against real 2026/2027 transition dates during testing (spring-forward 2027-03-14, fall-back 2026-11-01).
Also flags the day-of-month/day-of-week footgun almost everyone hits once: POSIX cron treats both fields as OR, not AND, when both are restricted.
Tools
validatecronexpression
Syntax + semantic validation: OR-not-AND warning, every-minute footgun, day-of-month values some months don't have (31, 30, 29), a nudge to check DST risk for anything in the 1-3am window. Returns a plain-English explanation of what the expression means.
getnextfire_times
Next N fire times, DST-aware. If a scheduled local time falls in a spring-forward gap it's flagged as skipped; if it falls in a fall-back overlap, both real firings are returned as ambiguous.
detectdstrisk
Scans a full year ahead and reports every date where the schedule collides with a DST transition — run this once on any job scheduled in the 1-4am local window before you ship it.
Use it
Hosted (recommended): MCPize — free tier, $7/mo Pro.
Self-host:
npm install
node server.jsPart of a small suite
mcp-schema-audit-mcp, regex-safety-audit-mcp, claude-cost-audit-mcp.
License
MIT
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-28revokeA → Fscore 32: Remote endpoint did not respond
Cron Schedule Audit: common questions
- Is Cron Schedule Audit MCP server safe?
- No: it is graded F and blocked at the gateway (32/100). Read the Cron Schedule Audit safety report
- How do I install Cron Schedule Audit?
- It runs remotely at cron-schedule-audit-mcp.mcpize.run. 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 Schedule Audit need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Cron Schedule Audit maintained?
- The last commit was 102 days ago (2026-07-25). The latest release is v1.0.0.
- Is Cron Schedule Audit up?
- 21% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Cron Schedule Audit compare with other MCP servers?
- safety score 32/100 (higher than 6% of 48,255 servers); uptime 21% (of our recent checks; the typical remote server answers 100%); response time 715 ms (faster than 19% of 30,031 servers). Full comparison.