Cron Collision Detector

io.github.lazymac2xPublished by GitHub account lazymac2xv1.0.0Updated Oct 24, 2026

Cloudflare Workers MCP server: cron-collision-detector

The publisher's own server: Croncool Cron Jobs

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server that analyzes cron schedules, finding collision and spike windows across multiple expressions and listing upcoming firing times.

What you can do
Detect collision and spike windows across several cron schedules over a chosen time horizon, to spot jobs that would run at the same moment or bunch up. Get the next N firing timestamps for a single cron expression.
When to use it
Useful when planning or reviewing cron jobs and you want to check whether several schedules overlap or spike before deploying them, or to preview when one expression will next run.
Requirements
A remote endpoint at api.lazy-mac.com; no authentication, environment variables or headers are declared. Network access is needed.
Before you install
Schedules you submit are sent to a third-party hosted service, so avoid including sensitive details in the expressions or surrounding context.

Installation

In SourceWeft

  1. Open Cron Collision Detector in the dashboard and add it to a workspace.
  2. 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.lazymac2x%2Fcron-collision-detector/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cron-collision-detector": {
      "type": "http",
      "url": "https://api.lazy-mac.com/cron-collision-detector/mcp"
    }
  }
}

README

cron-collision-detector-api

Cloudflare Workers MCP server: cron-collision-detector. REST + MCP (JSON-RPC 2.0). Live: api.lazy-mac.com/cron-collision-detector

Source: README.md at commit b0bfaa9

Tools

2

analyze_cron_collisions

Detect collision and spike windows across multiple cron schedules over a time horizon.

Parametersjobsrequiredbucket_secondshorizon_minutescollision_threshold

next_firings

Return next N firing timestamps for a single cron expression.

Parameterscountexpressionrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Cron integrations