Cronitor MCP by usefulapi
io.usefulapi/cronitor · v1.11.1
Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.
MCPremoteno credentials
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 6 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 6 tools · 2 read, 4 write (incl. delete/pay)
Test call cronitor_list_monitors: needs a key: HTTP 401 (1,060 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://cronitor.usefulapi.io/mcpTools
6 tools listed at last check
cronitor_list_monitorsList monitors and their current passing/failing status. Cronitor API: GET /monitors (paginated via page + pageSize).cronitor_get_monitorGet full detail for one monitor (latest_event, latest_invocations, passing status) — the 'is X healthy right now?' tool. Cronitor API: GET /monitors/{key}.cronitor_create_monitorCreates a monitor in Cronitor (additive). Cronitor API: POST /monitors. Sends only the fields you provide.cronitor_update_monitorCreates or updates a monitor by key (e.g. change schedule, pause via paused:true). Cronitor API: PUT /monitors with a single monitor object. Sends only the fields you provide.cronitor_delete_monitorPERMANENTLY deletes a monitor from Cronitor. Destructive and irreversible. Cronitor API: DELETE /monitors/{key}.cronitor_ping_monitorReports a telemetry event (run/complete/fail/ok/pause) for a monitor — records job/heartbeat activity and can clear or trigger alerts. Cronitor telemetry: GET {telemetryUrl}/p/{apiKey}/{monitorKey}?state=...
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.usefulapi/cronitor)