# io.usefulapi/cronitor (remote · cronitor.usefulapi.io)

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

- Trust score: 18/100 (low)
- Change this week: −51
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `cronitor.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-cronitor/cronitor.md), [page](https://verifymcp.io/servers/io-usefulapi-cronitor/cronitor)

## Channel facts

- Endpoint: `https://cronitor.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 429.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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

### Claude

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

### Codex

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

### OpenClaw

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

### Hermes

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

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 18, −54)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-08-01 (score 72, +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.

### 2026-07-31 (score 71, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 69, +57)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 12)

First indexed and scored.

## MCP tools (6)

### `cronitor_list_monitors` (~66 tokens)

List monitors

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

Input parameters:

- `page` (integer): Page number (1-based). Default 1.
- `pageSize` (integer): Monitors per page.

### `cronitor_get_monitor` (~62 tokens)

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

Input parameters:

- `key` (string, required): Monitor key/id (unique identifier).

### `cronitor_create_monitor` (~186 tokens)

Create monitor

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

Input parameters:

- `assertions` (array): Assertions, e.g. "response.code = 200".
- `key` (string, required): 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, required): Monitor type: job | check | heartbeat | site.

### `cronitor_update_monitor` (~220 tokens)

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.

Input parameters:

- `assertions` (array): Assertions, e.g. "response.code = 200".
- `key` (string, required): 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.

### `cronitor_delete_monitor` (~49 tokens)

Delete monitor

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

Input parameters:

- `key` (string, required): Monitor key/id to delete.

### `cronitor_ping_monitor` (~157 tokens)

Ping monitor (telemetry)

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 parameters:

- `host` (string): Optional host identifier.
- `key` (string, required): 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, required): Telemetry state: run | complete | fail | ok | pause.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-cronitor/cronitor#diagnostics

## Score history

- 2026-08-03: 18
- 2026-08-02: 72
- 2026-08-01: 72
- 2026-07-31: 71
- 2026-07-30: 69
- 2026-07-29: 70
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 12

## Links

- Remote endpoint: https://cronitor.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-cronitor/cronitor/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-cronitor/cronitor/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-cronitor/cronitor