Skip to content
Agentmart
Submit a tool

Cron Schedule Audit

Validates cron expressions and finds DST bugs that make jobs silently skip or double-fire.

Connector by tylerscomic-lab · GitHub account verified by the MCP Registry

IndexedMITRemote (HTTP)
Write a review

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/tylerscomic-lab-cron-schedule-audit-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://cron-schedule-audit-mcp.mcpize.run/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Validates cron expressions and finds DST bugs that make jobs silently skip or double-fire.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
3 read · 0 write · 0 deleteRead-only
Secrets
None asked for
Install scripts
Nothing to install (hosted)
Runs as
Hosted (remote endpoint)

Tools by what they do 3

Read from the source code; the running server may list different tools.

Read 3 · Look things up without changing anything.

  • detect_dst_risk
  • get_next_fire_times
  • validate_cron_expression

Network hosts it talks to 1

  • cron-schedule-audit-mcp.mcpize.run · found in remote endpoint, install command

Tools (3)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • detect_dst_risk

    Scan a cron expression forward across a full year in a given IANA timezone and report every date where its scheduled local time falls into a DST gap (silently skipped) or overlap (fires twice) window. Use this on any job scheduled in the 1-4am local window before you ship it — this is the single most common "why did my cron job not run that one day" support ticket.

  • get_next_fire_times

    Compute the next N times a cron expression will actually fire, correctly accounting for the given IANA timezone's DST transitions (using the platform tz database, not a fixed UTC offset — this is the part that's easy to get subtly wrong by hand). If a scheduled local time falls in a spring-forward gap it is skipped and flagged; if it falls in a fall-back overlap both real firings are returned and flagged as ambiguous.

  • validate_cron_expression

    Validate a cron expression's syntax AND flag the semantic footguns that valid-but-wrong expressions hit in practice: day-of-month/day-of-week OR-not-AND semantics, every-minute schedules, day-of-month values that some months never have (31, 30, 29), and a nudge to check DST risk for anything scheduled in the 1-3am window. Also returns a plain-English explanation of what the expression actually means.

Signals

Stars
0
Forks
0
Open issues
0
Last commit
Jul 25, 2026 (3 months ago)
Last release
Jul 25, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.tylerscomic-lab/cron-schedule-audit-mcp
Version
1.0.0
Auth
Auth not stated
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from tylerscomic-lab

Cite this page

Cron Schedule Audit MCP server. Agent Mart. https://agentmart.dev/connectors/tylerscomic-lab-cron-schedule-audit-mcp (last updated 2026-10-24)