cron-collision-detector
Cloudflare Workers MCP server: cron-collision-detector
Should I use this
Quality & Safety
A
Findings (1)
- LOWTool 'analyze_cron_collisions' description lacks action verbin analyze_cron_collisions
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~204Tokens (tool definitions)
~938 BTypical response size
Minimal attention impact (0.16% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"cron-collision-detector": {
"url": "https://api.lazy-mac.com/cron-collision-detector/mcp"
}
}
}Remote endpoints
https://api.lazy-mac.com/cron-collision-detector/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢analyze_cron_collisions(jobs, horizon_minutes, bucket_seconds, collision_threshold)
Detect collision and spike windows across multiple cron schedules over a time horizon.
Input Schema
{
"type": "object",
"properties": {
"jobs": {
"type": "array",
"description": "Array of { id, expression }",
"items": {
"type": "object"
}
},
"horizon_minutes": {
"type": "number",
"description": "Look-ahead horizon in minutes (default 60)"
},
"bucket_seconds": {
"type": "number",
"description": "Collision bucket size in seconds (default 1)"
},
"collision_threshold": {
"type": "number",
"description": "Min concurrent jobs to count as collision (default 2)"
}
},
"required": [
"jobs"
]
}⚪next_firings(expression, count)
Return next N firing timestamps for a single cron expression.
Input Schema
{
"type": "object",
"properties": {
"expression": {
"type": "string"
},
"count": {
"type": "number",
"description": "How many firings to return (default 5, max 50)"
}
},
"required": [
"expression"
]
}Community
Evidence
Recent observations
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools