io.github.jaredhobbs/cronalert

NPM · CRONALERT-MCP · SCANNED AUG 3

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

Available components

−10 this week 69 69 Trust /100

Trust breakdown (6 categories)

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. How we score →

Supply Chain Security86

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 142 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability75

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 932 tokens (~84/item across 11 items; 11 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

npm · cronalert-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# add to Codex CLI

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

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.json

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

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 +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.
2 Aug 26 +63
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
31 Jul 26 −35
- 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 −39
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- License: pass → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
27 Jul 26 +54
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- 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 functional
26 Jul 26 25

First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 2 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 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 11 exposed · ~932 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

add_incident_update ~56

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

Input Output Examples

Name	Type	Req	Description
incidentId	string	yes	Incident ID
message	string	yes	Update message text
status	string	yes	Update status

No output schema declared.

No examples provided.

create_monitor ~354

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 Output Examples

Name	Type	Req	Description
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	yes	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)

No output schema declared.

No examples provided.

delete_monitor ~33

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	Monitor ID

No output schema declared.

No examples provided.

get_check_results ~60

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	Monitor ID
limit	integer	—	Results per page (max 100)
page	integer	—	Page number

No output schema declared.

No examples provided.

get_incident_updates ~28

Get status updates for a specific incident.

Input Output Examples

Name	Type	Req	Description
incidentId	string	yes	Incident ID

No output schema declared.

No examples provided.

get_monitor ~29

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	Monitor ID

No output schema declared.

No examples provided.

get_monitor_incidents ~56

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	Monitor ID
limit	integer	—	Results per page (max 100)
page	integer	—	Page number

No output schema declared.

No examples provided.

list_incidents ~17

List all active incidents across all monitors.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_monitors ~63

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

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Results per page (max 100)
page	integer	—	Page number
status	string	—	Filter by monitor status

No output schema declared.

No examples provided.

list_status_pages ~19

List all public status pages configured for your account.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_monitor ~217

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

Input Output Examples

Name	Type	Req	Description
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	yes	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)

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