io.usefulapi/cronitor

REMOTE · CRONITOR.USEFULAPI.IO · SCANNED AUG 3

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

Available components

−51 this week 18 18 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security46

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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

Transport & Reachability0

Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail

Schema Quality & AI Usability0

Schema not yet verified: we couldn't read the endpoint's schema.Unverified

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage0

Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified

Capabilities0

Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · cronitor.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-cronitor]
url = "https://cronitor.usefulapi.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-cronitor": {
      "type": "remote",
      "url": "https://cronitor.usefulapi.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-usefulapi-cronitor --url https://cronitor.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-cronitor:
    url: "https://cronitor.usefulapi.io/mcp"

// mcp.json

{
  "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.

Changelog

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 Aug 26 −54
- 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
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 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
30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +57
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 12

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	16 Jul 2026	14 Oct 2026	ECDSA 256	ECDSA-SHA256	abd39c20a210e7230ece904d1f1db905
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

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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	429

Header	Value
x-frame-options	SAMEORIGIN
referrer-policy	same-origin

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://cronitor.usefulapi.io/mcp	HTTP error	429
http (plaintext)	http://cronitor.usefulapi.io/mcp	Inconclusive	429

MCP tools — 6 exposed · ~740 tokens

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.

Tool Tokens

cronitor_create_monitor Create monitor ~186

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	69
28 Jul	70
29 Jul	70
30 Jul	69
31 Jul	71
1 Aug	72
2 Aug	72
3 Aug	18