Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.
Scored across 6 tools
Each tool targets a distinct action: create, delete, get, list, ping, update. There is no ambiguity or overlap between them.
All tools follow the 'cronitor_<verb>_monitor' pattern with snake_case and consistent verb placement. Minor pluralization in 'list_monitors' is standard for listing endpoints.
6 tools cover the core lifecycle of monitors without unnecessary extras. The count is well-scoped for a monitoring server.
The set provides full CRUD operations plus telemetry via ping. There are no obvious gaps for managing monitors.
Creates a monitor in Cronitor (additive). Cronitor API: POST /monitors. Sends only the fields you provide.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Unique monitor id/key. | |
| name | No | Human-readable monitor name. | |
| note | No | Free-form note stored on the monitor. | |
| tags | No | Tags to group/filter monitors. | |
| type | Yes | Monitor type: job | check | heartbeat | site. | |
| notify | No | Notification list names to alert. | |
| request | No | For type=check: {url, method?, headers?, body?, ...}. | |
| schedule | No | Cron expression (job) or interval string, e.g. '0 9 * * *' or 'every 5 minutes'. | |
| assertions | No | Assertions, e.g. "response.code = 200". |
PERMANENTLY deletes a monitor from Cronitor. Destructive and irreversible. Cronitor API: DELETE /monitors/{key}.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Monitor key/id to delete. |
Get full detail for one monitor (latest_event, latest_invocations, passing status) — the 'is X healthy right now?' tool. Cronitor API: GET /monitors/{key}.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Monitor key/id (unique identifier). |
List monitors and their current passing/failing status. Cronitor API: GET /monitors (paginated via page + pageSize).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based). Default 1. | |
| pageSize | No | Monitors per page. |
Reports 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=...
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Monitor key/id to ping. | |
| host | No | Optional host identifier. | |
| state | Yes | Telemetry state: run | complete | fail | ok | pause. | |
| metric | No | Optional metric, e.g. "count:1" or "duration:30". | |
| series | No | Optional series id to correlate run/complete pings. | |
| message | No | Optional message attached to the event. |
Creates 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.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Monitor key/id to create or update. | |
| name | No | Human-readable monitor name. | |
| note | No | Free-form note stored on the monitor. | |
| tags | No | Tags to group/filter monitors. | |
| type | No | Monitor type: job | check | heartbeat | site. | |
| notify | No | Notification list names to alert. | |
| paused | No | Set true to pause the monitor, false to resume. | |
| request | No | For type=check: {url, method?, headers?, body?, ...}. | |
| schedule | No | Cron expression (job) or interval string, e.g. '0 9 * * *' or 'every 5 minutes'. | |
| assertions | No | Assertions, e.g. "response.code = 200". |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
cronitor_create_monitor1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"cronitor_delete_monitor1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"cronitor_get_monitor1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"cronitor_list_monitors1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"cronitor_ping_monitor1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"cronitor_update_monitor1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"cronitor_create_monitorcronitor_delete_monitorcronitor_get_monitorcronitor_list_monitorscronitor_ping_monitorcronitor_update_monitorMonitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
Uptime monitoring that doesn't cry wolf: manage monitors, read incidents, record deploys.
Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.
Add one secure layer between your agents and this server.
