Home / MCP registry index / io.github.lazymac2x/cron-collision-detector
io.github.lazymac2x/cron-collision-detector
io.github.lazymac2x/cron-collision-detector in the official MCP registry.
Endpoint https://api.lazy-mac.com/cron-collision-detector/mcp. Source: github.com/lazymac2x/cron-collision-detector-api.
The registry describes it as: Cloudflare Workers MCP server: cron-collision-detector
Not read yet. The index re-reads every listed server about once a week, and this one is in the queue. You can check it yourself right now.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-lazymac2x-cron-collision-detector)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| Cloudflare Radar io.github.pipeworx-io/cloudflare-radar | 48 tools, nothing matched 2026-10-22 |
| Mat Web & Data Toolkit (x402, Cloudflare) dev.workers.matt-d59.automatom/web-data-toolkit | 46 tools, nothing matched 2026-10-22 |
| ai.kaiv/is-it-down ai.kaiv/is-it-down | 3 tools, nothing matched 2026-10-22 |
| ShadowCrawl io.github.DevsHero/shadow-crawl | needs credentials to list tools 2026-10-22 |
| cc.aiones/dev-toolbox cc.aiones/dev-toolbox | not read yet |
| com.cloudflare.mcp/mcp com.cloudflare.mcp/mcp | not read yet |