Skip to content

Cronitor MCP by usefulapi

io.usefulapi/cronitorusefulapi.iostreamable-httpv1.40.4Scanned

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

6 tools: 4 can delete or cancel things and 2 only read.

Tools: 4 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Cronitor MCP by usefulapi can do

The Cronitor MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (4 tools: cronitor_create_monitor, cronitor_update_monitor, cronitor_delete_monitor and cronitor_ping_monitor). 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Deletes or cancels 4Claude Code: deny
  • cronitor_create_monitorCreates a monitor in Cronitor (additive).No findings

    Why it is in this group

    • The name "cronitor_create_monitor" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Creates a monitor in Cronitor (additive). Cronitor API: POST /monitors. Sends only the fields you provide.

    Annotations the server declares

    • title: Create monitor
    • destructiveHint: true
  • cronitor_delete_monitorPERMANENTLY deletes a monitor from Cronitor.No findings

    Why it is in this group

    • The name "cronitor_delete_monitor" says "delete": a word for removing or ending something.
    • The description says "PERMANENTLY deletes".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    PERMANENTLY deletes a monitor from Cronitor. Destructive and irreversible. Cronitor API: DELETE /monitors/{key}.

    Annotations the server declares

    • title: Delete monitor
    • destructiveHint: true
  • cronitor_ping_monitorReports a telemetry event (run/complete/fail/ok/pause) for a monitor — records job/heartbeat activity and can clear or trigger alerts.1 finding

    Why it is in this group

    • The name "cronitor_ping_monitor" says "ping": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Warn

      The server marks "cronitor_ping_monitor" destructive (destructiveHint: true), and its name says "ping", a word for reading.

      Matched text

      annotations: {"destructiveHint":true}; The name "cronitor_ping_monitor" says "ping": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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=...

    Annotations the server declares

    • title: Ping monitor (telemetry)
    • destructiveHint: true
  • cronitor_update_monitorCreates or updates a monitor by key (e.g.No findings

    Why it is in this group

    • The name "cronitor_update_monitor" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update monitor
    • destructiveHint: true
Only reads 2Show 2 read-only tools
  • cronitor_get_monitorGet full detail for one monitor (latest_event, latest_invocations, passing status) — the 'is X healthy right now?' tool.No findings

    Why it is in this group

    • The name "cronitor_get_monitor" says "get": a word for reading.
    Description, as the server wrote it
    Get full detail for one monitor (latest_event, latest_invocations, passing status) — the 'is X healthy right now?' tool. Cronitor API: GET /monitors/{key}.

    Annotations the server declares

    • title: Get monitor
    • readOnlyHint: true
  • cronitor_list_monitorsList monitors and their current passing/failing status.No findings

    Why it is in this group

    • The name "cronitor_list_monitors" says "list": a word for reading.
    Description, as the server wrote it
    List monitors and their current passing/failing status. Cronitor API: GET /monitors (paginated via page + pageSize).

    Annotations the server declares

    • title: List monitors
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:34 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://cronitor.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://cronitor.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "cronitor_ping_monitor" destructive (destructiveHint: true), and its name says "ping", a word for reading.

    Matched text

    annotations: {"destructiveHint":true}; The name "cronitor_ping_monitor" says "ping": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://cronitor.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://cronitor.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http cronitor https://cronitor.usefulapi.io/mcp
claude mcp add --transport http cronitor https://cronitor.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cronitor__cronitor_list_monitors",
      "mcp__cronitor__cronitor_get_monitor"
    ],
    "ask": [],
    "deny": [
      "mcp__cronitor__cronitor_create_monitor",
      "mcp__cronitor__cronitor_update_monitor",
      "mcp__cronitor__cronitor_delete_monitor",
      "mcp__cronitor__cronitor_ping_monitor"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cronitor. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/cronitor/verify?hash=878333f89a5efe0023fd7713ced5b114c26e9df7c7aff10aa832772f03527324" | jq -e '.changed == false'

Pinned hash 878333f89a5e, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/cronitor/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/cronitor
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/cronitor.svg)](https://radar.anlyon.com/servers/io.usefulapi/cronitor)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Cronitor MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Cronitor MCP by usefulapi safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Cronitor MCP by usefulapi delete data?

Yes. 4 tools can delete, cancel or revoke something: cronitor_create_monitor, cronitor_update_monitor, cronitor_delete_monitor and cronitor_ping_monitor.

Can the Cronitor MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Cronitor MCP by usefulapi have?

6 tools: 4 destructive, 2 read. cronitor_create_monitor, cronitor_update_monitor, cronitor_delete_monitor, cronitor_ping_monitor, cronitor_list_monitors and cronitor_get_monitor.

Does the Cronitor MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Cronitor MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Cronitor MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.