# io.github.jaredhobbs/cronalert (npm · cronalert-mcp)

Manage CronAlert uptime monitors, check results, and incidents from any MCP client.

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

## Components

- npm · `cronalert-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/jaredhobbs-cronalert/cronalert-mcp.md), [page](https://verifymcp.io/servers/jaredhobbs-cronalert/cronalert-mcp)

## Channel facts

- Registry: `npm`
- Package: `cronalert-mcp`
- Version: `1.0.6`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 142 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 932 tokens (~84/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add jaredhobbs-cronalert -- npx -y cronalert-mcp
```

### Codex

```bash
codex mcp add jaredhobbs-cronalert -- npx -y cronalert-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jaredhobbs-cronalert": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cronalert-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jaredhobbs-cronalert --command npx --arg -y --arg cronalert-mcp
```

### Hermes

```yaml
mcp_servers:
  jaredhobbs-cronalert:
    command: "npx"
    args: ["-y", "cronalert-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "jaredhobbs-cronalert": {
      "command": "npx",
      "args": [
        "-y",
        "cronalert-mcp"
      ]
    }
  }
}
```

## 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 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 68, +63)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: MIT

### 2026-07-31 (score 5, −35)

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

### 2026-07-30 (score 40, −39)

- [security regression] Known CVEs: partial → unverified
- [security regression] Malware scan: pass → unverified
- [security regression] Provenance: fail → unverified
- [security regression] Install scripts: pass → unverified
- [functional regression] Dependency health: partial → unverified
- [functional regression] License: pass → unverified
- [functional regression] Maintenance: pass → unverified
- [functional] Licence: MIT

### 2026-07-27 (score 79, +54)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: good
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: fail
- [functional] Licence: MIT

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

First indexed and scored.

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

## MCP tools (11)

### `list_monitors` (~63 tokens)

List all uptime monitors. Optionally filter by status (up, down, unknown) and paginate.

Input parameters:

- `limit` (integer): Results per page (max 100)
- `page` (integer): Page number
- `status` (string): Filter by monitor status

### `create_monitor` (~354 tokens)

Create a new uptime monitor. Set type to 'heartbeat' for cron job / background task monitoring (returns a ping URL instead of checking a URL).

Input parameters:

- `checkInterval` (integer): Check interval in seconds (default 180, auto-set from plan)
- `expectedStatusCode` (integer): Expected HTTP status code (default 200, http type only)
- `failureThreshold` (integer): Number of regions that must fail before alerting (0 = alert on any failure, multi-region only)
- `headers` (string): Custom request headers as JSON string, e.g. '{"Authorization": "Bearer token"}' (http type only)
- `keyword` (string): Keyword to search for in response body (Pro plan+, http type only)
- `keywordMatchType` (string): Whether the keyword should be present or absent (Pro plan+)
- `maintenanceEnd` (string): Maintenance window end as ISO datetime string (Pro plan+)
- `maintenanceStart` (string): Maintenance window start as ISO datetime string (Pro plan+)
- `method` (string): HTTP method (default GET, http type only)
- `name` (string, required): Display name for the monitor
- `regions` (string): Comma-separated region IDs for multi-region checks: us-east, us-west, eu-west, eu-central, ap-southeast (Team plan+, http type only)
- `timeout` (integer): Request timeout in seconds (1-120, default 30, http type only)
- `type` (string): Monitor type: 'http' checks a URL, 'heartbeat' waits for pings from your application
- `url` (string): URL to monitor (required for http type, ignored for heartbeat)

### `get_monitor` (~29 tokens)

Get detailed information about a specific monitor including its current status.

Input parameters:

- `id` (string, required): Monitor ID

### `update_monitor` (~217 tokens)

Update an existing monitor's configuration. Only provided fields are changed.

Input parameters:

- `expectedStatusCode` (integer): Expected HTTP status code
- `failureThreshold` (integer): Number of regions that must fail before alerting
- `headers` (string): Custom request headers as JSON string
- `id` (string, required): Monitor ID
- `keyword` (string): Keyword to search for in response body (Pro plan+)
- `keywordMatchType` (string): Whether the keyword should be present or absent
- `maintenanceEnd` (string): Maintenance window end as ISO datetime string
- `maintenanceStart` (string): Maintenance window start as ISO datetime string
- `method` (string): HTTP method
- `name` (string): Display name
- `paused` (boolean): Pause or resume the monitor
- `regions` (string): Comma-separated region IDs for multi-region checks (Team plan+)
- `timeout` (integer): Request timeout in seconds (1-120)
- `url` (string): URL to monitor (http type only)

### `delete_monitor` (~33 tokens)

Permanently delete a monitor and all its check history. This cannot be undone.

Input parameters:

- `id` (string, required): Monitor ID

### `get_check_results` (~60 tokens)

Get recent check results for a monitor, including response times, status codes, and uptime percentage.

Input parameters:

- `id` (string, required): Monitor ID
- `limit` (integer): Results per page (max 100)
- `page` (integer): Page number

### `get_monitor_incidents` (~56 tokens)

Get incidents for a specific monitor — periods when the monitor was down.

Input parameters:

- `id` (string, required): Monitor ID
- `limit` (integer): Results per page (max 100)
- `page` (integer): Page number

### `list_incidents` (~17 tokens)

List all active incidents across all monitors.

### `list_status_pages` (~19 tokens)

List all public status pages configured for your account.

### `add_incident_update` (~56 tokens)

Post a status update on an active incident. Updates appear on the public status page.

Input parameters:

- `incidentId` (string, required): Incident ID
- `message` (string, required): Update message text
- `status` (string, required): Update status

### `get_incident_updates` (~28 tokens)

Get status updates for a specific incident.

Input parameters:

- `incidentId` (string, required): Incident ID

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/jaredhobbs-cronalert/cronalert-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 5
- 2026-07-31: 5
- 2026-07-30: 40
- 2026-07-28: 79
- 2026-07-27: 79
- 2026-07-26: 25

## Links

- npm package: https://www.npmjs.com/package/cronalert-mcp
- Socket report: https://socket.dev/npm/package/cronalert-mcp
- Repository: https://github.com/jaredhobbs/cronalert-mcp
- Changelog RSS feed: https://verifymcp.io/servers/jaredhobbs-cronalert/cronalert-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/jaredhobbs-cronalert/cronalert-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/jaredhobbs-cronalert/cronalert-mcp