mcpbeat

Cron Collision Detector MCP Server

io.github.lazymac2x/cron-collision-detector
answering

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

Cloudflare Workers MCP server: cron-collision-detector

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
145 ms
Response time
average over 24h
0
Stars
last commit 17 May 2026

Connect this server

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

run in your terminal
claude mcp add cron-collision-detector --transport http https://api.lazy-mac.com/cron-collision-detector/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cron-collision-detector": {
      "url": "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
{
  "mcpServers": {
    "cron-collision-detector": {
      "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
next_firings
Return next N firing timestamps for a single cron expression.

Endpoints

URLTransportStateLatencyChecked
https://api.lazy-mac.com/cron-collision-detector/mcp streamable-http answering 190 ms 3 min ago

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 145 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 with the file path 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 145 ms on average, which is faster than 74% 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?
Yes — 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.