io.usefulapi/cronitor
REMOTE · CRONITOR.USEFULAPI.IO · SCANNED SEP 20
Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 740 tokens (~123/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/cronitor MCP server?
io.usefulapi/cronitor is a hosted endpoint at https://cronitor.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cronitor.usefulapi.io
claude mcp add --transport http io-usefulapi-cronitor 'https://cronitor.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-cronitor": {
"url": "https://cronitor.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-cronitor": {
"type": "http",
"url": "https://cronitor.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-cronitor] url = "https://cronitor.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-cronitor": {
"type": "remote",
"url": "https://cronitor.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-cronitor --url 'https://cronitor.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-cronitor:
url: "https://cronitor.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-cronitor": {
"Transport": "http",
"Url": "https://cronitor.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-cronitor -t streamable-http -u 'https://cronitor.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-cronitor": {
"type": "http",
"url": "https://cronitor.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Sept 26 +1
- Stability: 0.97 → pass security
- 2 Sept 26 −1
- Stability: pass → 0.97 functional
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Aug 26 0
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- 3 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://cronitor.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1b5d54909bf2fca913b5fef5eae90d8e |
| SANs: usefulapi.io, cronitor.usefulapi.io, *.cronitor.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cronitor.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://cronitor.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://cronitor.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://cronitor.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://cronitor.usefulapi.io/mcp |
| Authorisation server | https://cronitor.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cronitor.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://cronitor.usefulapi.io/mcp | Inconclusive | 401 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cronitor_create_monitor Create monitor ~186
Creates a monitor in Cronitor (additive). Cronitor API: POST /monitors. Sends only the fields you provide.
| Name | Type | Req | Description |
|---|---|---|---|
| assertions | array | – | Assertions, e.g. "response.code = 200". |
| key | string | yes | Unique monitor id/key. |
| name | string | – | Human-readable monitor name. |
| note | string | – | Free-form note stored on the monitor. |
| notify | array | – | Notification list names to alert. |
| request | object | – | For type=check: {url, method?, headers?, body?, ...}. |
| schedule | string | – | Cron expression (job) or interval string, e.g. '0 9 * * *' or 'every 5 minutes'. |
| tags | array | – | Tags to group/filter monitors. |
| type | string | yes | Monitor type: job | check | heartbeat | site. |
No output schema declared.
No examples provided.
cronitor_delete_monitor Delete monitor ~49
PERMANENTLY deletes a monitor from Cronitor. Destructive and irreversible. Cronitor API: DELETE /monitors/{key}.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Monitor key/id to delete. |
No output schema declared.
No examples provided.
cronitor_get_monitor Get monitor ~62
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 | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Monitor key/id (unique identifier). |
No output schema declared.
No examples provided.
cronitor_list_monitors List monitors ~66
List monitors and their current passing/failing status. Cronitor API: GET /monitors (paginated via page + pageSize).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pageSize | integer | – | Monitors per page. |
No output schema declared.
No examples provided.
cronitor_ping_monitor Ping monitor (telemetry) ~157
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 | Type | Req | Description |
|---|---|---|---|
| host | string | – | Optional host identifier. |
| key | string | yes | Monitor key/id to ping. |
| message | string | – | Optional message attached to the event. |
| metric | string | – | Optional metric, e.g. "count:1" or "duration:30". |
| series | string | – | Optional series id to correlate run/complete pings. |
| state | string | yes | Telemetry state: run | complete | fail | ok | pause. |
No output schema declared.
No examples provided.
cronitor_update_monitor Update monitor ~220
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 | Type | Req | Description |
|---|---|---|---|
| assertions | array | – | Assertions, e.g. "response.code = 200". |
| key | string | yes | Monitor key/id to create or update. |
| name | string | – | Human-readable monitor name. |
| note | string | – | Free-form note stored on the monitor. |
| notify | array | – | Notification list names to alert. |
| paused | boolean | – | Set true to pause the monitor, false to resume. |
| request | object | – | For type=check: {url, method?, headers?, body?, ...}. |
| schedule | string | – | Cron expression (job) or interval string, e.g. '0 9 * * *' or 'every 5 minutes'. |
| tags | array | – | Tags to group/filter monitors. |
| type | string | – | Monitor type: job | check | heartbeat | site. |
No output schema declared.
No examples provided.
What is the io.usefulapi/cronitor MCP server?
io.usefulapi/cronitor is an MCP server listed in the public MCP registry as io.usefulapi/cronitor. Manage Cronitor monitors and send telemetry pings, list, inspect, create, update, delete. This page covers its hosted endpoint (https://cronitor.usefulapi.io/mcp).
Is the io.usefulapi/cronitor MCP server safe to use?
io.usefulapi/cronitor scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/cronitor MCP server expose?
io.usefulapi/cronitor exposes 6 tools: cronitor_list_monitors, cronitor_get_monitor, cronitor_create_monitor, cronitor_update_monitor, cronitor_delete_monitor, cronitor_ping_monitor. Their descriptions and schemas cost roughly 740 tokens of context every time the server is loaded.
Does the io.usefulapi/cronitor MCP server require authentication?
Yes. io.usefulapi/cronitor asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/cronitor MCP server still maintained?
io.usefulapi/cronitor is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.