io.github.jaredhobbs/cronalert
NPM · CRONALERT-MCP
Manage CronAlert uptime monitors, check results, and incidents from any MCP client.
Available components
Last scanned (19 hours ago)
Scores higher than 87% of npm servers
Category Monitoring and Observability
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. 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 39 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1331 tokens (~110/item across 12 items; 12 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 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 27 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.83 functional
- 15 Oct 26 +1
- Stability: 0.97 → pass security
- 13 Oct 26 +1
- Security disclosure: unverified → fail ▼ 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 4 Nov 2026 · Analysed npm/cronalert-mcp@1.5.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_incident_update ~56
Post a status update on an active incident. Updates appear on the public status page.
| 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 ~536
Create a new uptime monitor. Supports HTTP status checks, keyword matching, regex matching, content change detection, and content staleness alerts (Pro+). Set type to 'heartbeat' for cron job / background task monitoring, or 'tcp' (Pro+) to check that a host:port accepts connections — TCP checks can target bare IP addresses, which HTTP checks cannot.
| Name | Type | Req | Description |
|---|---|---|---|
| checkInterval | integer | – | Heartbeat type: expected seconds between pings, from the plan minimum (60 on Pro+) up to 604800 (7 days). Other types: ignored, set automatically from the 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) |
| gracePeriod | integer | – | Heartbeat type only: extra seconds a ping may be late before the monitor is down (default: the interval, capped at 3600) |
| headers | string | – | Custom request headers as JSON string, e.g. '{"Authorization": "Bearer token"}' (http type only) |
| host | string | – | Hostname or IP address to connect to (tcp type only) |
| keyword | string | – | Value depends on keywordMatchType: keyword text for contains/not_contains, regex pattern for regex_match/regex_not_match, number of days for content_stale, unused for content_changed (Pro+) |
| keywordMatchType | string | – | Content check mode (Pro+) |
| 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 |
| port | integer | – | TCP port to connect to (tcp type only; port 25 is not supported) |
| 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, 'tcp' opens a connection to host:port (Pro+) |
| url | string | – | URL to monitor (required for http type, ignored for other types) |
No output schema declared.
No examples provided.
delete_monitor ~90
Permanently delete a monitor and all its check history. This cannot be undone. If the API key requires confirmation, the first call returns a preview and a confirmToken; call again with that token in `confirm` to proceed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | – | Server-issued confirmation token from a prior delete attempt. Only needed when the key mandates confirmation for destructive actions. |
| 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.
| 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.
| 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.
| 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.
| 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.
import_monitors ~91
Import monitors from another monitoring service. Supports UptimeRobot, Pingdom, Better Stack, StatusCake, Checkly, Oh Dear, Cronitor, Healthchecks.io, Dead Man's Snitch, Datadog, CronAlert JSON, and CSV formats.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Raw JSON or CSV string exported from the source service |
| format | string | yes | Source format of the monitoring data |
No output schema declared.
No examples provided.
list_incidents ~17
List all active incidents across all monitors.
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.
| 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 schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_monitor ~286
Update an existing monitor's configuration including content checking mode. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| checkInterval | integer | – | Heartbeat monitors only: expected seconds between pings (plan minimum to 604800). Ignored for other types |
| expectedStatusCode | integer | – | Expected HTTP status code |
| failureThreshold | integer | – | Number of regions that must fail before alerting |
| gracePeriod | integer | – | Heartbeat monitors only: extra seconds a ping may be late before the monitor is down |
| headers | string | – | Custom request headers as JSON string |
| id | string | yes | Monitor ID |
| keyword | string | – | Value depends on keywordMatchType: keyword text, regex pattern, number of days, or unused (Pro+) |
| keywordMatchType | string | – | Content check mode (Pro+) |
| 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.
How do I install the io.github.jaredhobbs/cronalert MCP server?
io.github.jaredhobbs/cronalert runs locally as an npm package, launched with npx -y cronalert-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cronalert-mcp
claude mcp add jaredhobbs-cronalert -- npx -y cronalert-mcp
What is the io.github.jaredhobbs/cronalert MCP server?
io.github.jaredhobbs/cronalert is an MCP server listed in the public MCP registry as io.github.jaredhobbs/cronalert. Manage CronAlert uptime monitors, check results, and incidents from any MCP client. This page covers its npm package (cronalert-mcp).
Is the io.github.jaredhobbs/cronalert MCP server safe to use?
io.github.jaredhobbs/cronalert scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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.github.jaredhobbs/cronalert MCP server expose?
io.github.jaredhobbs/cronalert exposes 12 tools: list_monitors, create_monitor, get_monitor, update_monitor, delete_monitor, and 7 more. Their descriptions and schemas cost roughly 1,331 tokens of context every time the server is loaded.
Is the io.github.jaredhobbs/cronalert MCP server still maintained?
io.github.jaredhobbs/cronalert is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.jaredhobbs/cronalert MCP server under?
io.github.jaredhobbs/cronalert declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.