Cron Collision Detector MCP Server

by lazymac2x Your server? Claim it

answering

Cron Collision Detector is answering right now. Last checked 2 min ago. It exposes 2 tools. Last commit 17 May 2026.

Cloudflare Workers MCP server: cron-collision-detector

Uptime history 91 days of history · worst day 92%

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

192 ms

Response time

average over 24h

Stars

last commit 17 May 2026

Nothing serious here today

Today is the operative word: we check Cron Collision Detector every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add cron-collision-detector --transport http https://api.lazy-mac.com/cron-collision-detector/mcp

Settings → Connectors → Add custom connector, then paste this address

https://api.lazy-mac.com/cron-collision-detector/mcp

~/.codex/config.toml

[mcp_servers.cron-collision-detector]
url = "https://api.lazy-mac.com/cron-collision-detector/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

analyze

analyze_cron_collisions

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

next_firings

Return next N firing timestamps for a single cron expression.

Endpoints

URL	Transport	State	Latency	Checked
https://api.lazy-mac.com/cron-collision-detector/mcp	streamable-http	answering	144 ms	2 min ago

Alternatives to Cron Collision Detector

same job, measured the same way

Cron Monitor

by lazymac2x

Cloudflare Workers MCP server: cron-monitor

6 tools answering

Agent Loop Detector

by lazymac2x

Cloudflare Workers MCP server: agent-loop-detector

3 tools answering

Cron Parser

by lazymac2x

Cloudflare Workers MCP server: cron-parser

6 tools answering

API Schema Drift Detector

by lazymac2x

Cloudflare Workers MCP server: api-schema-drift-detector

3 tools answering

Color Palette

by lazymac2x

Cloudflare Workers MCP server: color-palette

7 tools answering

Blog

by lazymac2x

Cloudflare Workers MCP server: blog

3 tools answering

API Diff Monitor

by lazymac2x

Cloudflare Workers MCP server: api-diff-monitor

6 tools answering

API Mock Server

by lazymac2x

Cloudflare Workers MCP server: api-mock-server

6 tools answering

Cron Collision Detector — questions

Answers built from our own checks of this server.

What can Cron Collision Detector do?

It exposes 2 tools, read directly from the server on our last check. Among them: analyze_cron_collisions, next_firings. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Cron Collision Detector working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 192 ms. The bar chart above shows every period we have measured.

How do I connect Cron Collision Detector?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Cron Collision Detector need an API key?

No. Cron Collision Detector completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Cron Collision Detector?

It answers our handshake in 192 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Cron Collision Detector open source?

We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.