io.usefulapi/cronitor

Cronitor MCP by usefulapi

Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.

1.11.1
Version
remote
Transport
6
Tools

Security review

Partly reviewed

Reviewed 27m ago.

  • tools: 6 tools scanned
  • metadata: scanned
  • mediumReviewRemote tools take credentials as input

    Whatever an agent passes to a remote tool leaves the machine. Never send connection strings, tokens or passwords to a third-party MCP server unless it is the service those credentials belong to.

    cronitor_ping_monitor

Tools (6)

  • cronitor_list_monitors

    List monitors and their current passing/failing status. Cronitor API: GET /monitors (paginated via page + pageSize).

  • cronitor_get_monitor

    Get 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_monitor

    Creates a monitor in Cronitor (additive). Cronitor API: POST /monitors. Sends only the fields you provide.

  • cronitor_update_monitor

    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.

  • cronitor_delete_monitor

    PERMANENTLY deletes a monitor from Cronitor. Destructive and irreversible. Cronitor API: DELETE /monitors/{key}.

  • cronitor_ping_monitor

    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=...