cron-collision-detector
Cloudflare Workers MCP server: cron-collision-detector
我該用這個嗎
品質與安全性
A
發現項目(1)
- LOW在 analyze_cron_collisions 中
根據工具定義與協定合規性的自動化分析。
上下文成本
~204Token(工具定義)
~938 B典型回應大小
極小的注意力影響(128k 上下文的 0.16%)
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"cron-collision-detector": {
"url": "https://api.lazy-mac.com/cron-collision-detector/mcp"
}
}
}遠端端點
https://api.lazy-mac.com/cron-collision-detector/mcpstreamable-http它能做什麼
工具清單
工具(2)
🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢analyze_cron_collisions(jobs, horizon_minutes, bucket_seconds, collision_threshold)
Detect collision and spike windows across multiple cron schedules over a time horizon.
輸入結構描述
{
"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.
輸入結構描述
{
"type": "object",
"properties": {
"expression": {
"type": "string"
},
"count": {
"type": "number",
"description": "How many firings to return (default 5, max 50)"
}
},
"required": [
"expression"
]
}社群
證據
近期觀測
已驗證未記錄版本2 個工具
已驗證未記錄版本2 個工具
已驗證未記錄版本2 個工具