io.github.jaredhobbs/cronalert
NPM · CRONALERT-MCP · SCANNED SEP 20
Manage CronAlert uptime monitors, check results, and incidents from any MCP client.
Available components
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
- 31 of 95 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 190 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).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 Management90
- Stability observed for 27 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
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 11 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
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
{
"mcpServers": {
"jaredhobbs-cronalert": {
"command": "npx",
"args": [
"-y",
"cronalert-mcp"
]
}
}
} {
"servers": {
"jaredhobbs-cronalert": {
"command": "npx",
"args": [
"-y",
"cronalert-mcp"
]
}
}
} codex mcp add jaredhobbs-cronalert -- npx -y cronalert-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jaredhobbs-cronalert": {
"type": "local",
"command": [
"npx",
"-y",
"cronalert-mcp"
],
"enabled": true
}
}
} openclaw mcp add jaredhobbs-cronalert --command npx --arg -y --arg cronalert-mcp
mcp_servers:
jaredhobbs-cronalert:
command: "npx"
args: ["-y", "cronalert-mcp"] {
"McpServers": {
"jaredhobbs-cronalert": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"cronalert-mcp"
]
}
}
} assistant mcp add jaredhobbs-cronalert -t stdio -c npx -a -y cronalert-mcp
{
"mcpServers": {
"jaredhobbs-cronalert": {
"command": "npx",
"args": [
"-y",
"cronalert-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 9 Sept 26 −3
- Stability: pass → 0.80 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 20 Sept 2026 · Analysed npm/cronalert-mcp@1.0.6
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 ~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).
| 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.
| 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.
| 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.
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 ~217
Update an existing monitor's configuration. Only provided fields are changed.
| 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.
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 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 11 tools: list_monitors, create_monitor, get_monitor, update_monitor, delete_monitor, and 6 more. Their descriptions and schemas cost roughly 932 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 20 September 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.