Cron Schedule Audit
io.github.tylerscomic-labPublished by GitHub account tylerscomic-labv1.0.0Updated Oct 24, 2026
Validates cron expressions and finds DST bugs that make jobs silently skip or double-fire.
The publisher's own server: audit.domains - Domain Valuation
Overview
Validates cron expressions and computes DST-correct next-fire times, flagging jobs that silently skip or double-fire.
- What you can do
- Validate cron expressions with syntax and semantic checks, including OR-not-AND day fields and impossible dates
- Explain in plain English what an expression means
- Compute the next N fire times against real IANA timezone data, marking spring-forward gaps as skipped and fall-back overlaps as ambiguous
- Scan a full year ahead for dates where a schedule collides with a DST transition
- When to use it
- Useful when writing or reviewing cron jobs, especially anything scheduled in the early-morning local window where daylight-saving transitions can make a job skip or fire twice without any error.
- Requirements
- A remote streamable HTTP endpoint with OAuth authentication required. Self-hosting is possible by installing the npm package and running the server with Node.js.
Installation
In SourceWeft
- Open Cron Schedule Audit in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.tylerscomic-lab%2Fcron-schedule-audit-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"cron-schedule-audit": {
"type": "http",
"url": "https://cron-schedule-audit-mcp.mcpize.run/mcp"
}
}
}README
cron-schedule-audit-mcp
[License: MIT] [Live on MCPize]
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/New_York 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
validate_cron_expression
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.
get_next_fire_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.
detect_dst_risk
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:
Part of a small suite
mcp-schema-audit-mcp, regex-safety-audit-mcp, claude-cost-audit-mcp.
License
MIT
Source: README.md at commit 6205784
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Audit integrations
audit.domains - Domain Valuation
domains.auditOfficial publisher
Deterministic domain-name valuation: fair-value intervals, comparable recorded sales, availability checks, and a verified for-sale listing market.
Revenue Agent — OpenAPI Audit & Change Detection
news.prhOfficial publisher
A remote MCP endpoint that audits OpenAPI specifications and detects API changes, charging $0.10 USDC per analysis via x402 on Base.
SEO Audit & Broken Link Checker
Published by GitHub account prometheus-maker
An Apify-hosted MCP server that audits a website's pages for SEO metadata and finds broken links and images, returning per-page scores.
FinePrint AI Legal Risk & Contract Audit MCP Server
Published by GitHub account RitualDev-Lab
Local in-memory scanner that grades legal contracts, NDAs and leases for risk and drafts redline amendments for coding agents.
Mcp Supply Audit
Published by GitHub account kimmawla
Audits MCP servers as supply-chain artifacts — registry entries, PyPI/npm packages, client configs and tool definitions — using read-only static checks.