Cronalert MCP server

by jaredhobbs·io.github.jaredhobbs/cronalert·v1.5.1

No reviews yet

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

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

Growing

0 stars186 downloads/wk

Reviews

Write one

Nobody has reviewed Cronalert yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cronalert tools (12, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

add_incident_updatewrite action
Post a status update on an active incident. Updates appear on the public status page.
create_monitorwrite action
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 \u2014 TCP checks can target bare IP addresses, which HTTP checks cannot.
delete_monitorwrite action
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.
get_check_results
Get recent check results for a monitor, including response times, status codes, and uptime percentage.
get_incident_updates
Get status updates for a specific incident.
get_monitor
Get detailed information about a specific monitor including its current status.
get_monitor_incidents
Get incidents for a specific monitor \u2014 periods when the monitor was down.
import_monitors
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.
list_incidents
List all active incidents across all monitors.
list_monitors
List all uptime monitors. Optionally filter by status (up, down, unknown) and paginate.
list_status_pages
List all public status pages configured for your account.
update_monitorwrite action
Update an existing monitor's configuration including content checking mode. Only provided fields are changed.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

1 medium

Code scan5 source files scanned20/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 0 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

mediumeval / new Function usedexec.eval

dist/bundle.cjs: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Cronalert compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 12; the typical server has 7
Tools that change things: 33%; typical: 0%. Fewer write tools means less an agent can break
Downloads a week: 186; more than 74% of 12,191 servers with a package

What its tools let an agent do: 7 read · 3 create · 1 change · 1 delete

Release history: 2 versions in the registry since 2026-03-10, latest 2026-09-25, typically one every 199 days.

Install Cronalert in Claude Code, Cursor or VS Code

Runs npx -y cronalert-mcp on your machine. Read the scan report first; the gateway never runs local packages.

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

Add to Cursor

What the publisher says

From the Cronalert repository's README, as published. We do not edit it. Read it on GitHub

cronalert-mcp

MCP server for CronAlert uptime monitoring. Manage your monitors, check results, and incidents from Claude, Cursor, Windsurf, or any MCP-compatible AI client.

Quick Start

1. Get your API key

When creating the key, choose a scope:

Read-only — the agent can list and read monitors, check results, and incidents but cannot create, update, or delete anything. Recommended for most agent setups.
Read & write — full access, including destructive tools. Optionally enable "require confirmation" so deletes need a server-issued confirmation token (see Security & permissions).

2. Add to your MCP client

Claude Desktop — edit ~/Library/Application Support/Claude/claudedesktopconfig.json:

{
  "mcpServers": {
    "cronalert": {
      "command": "npx",
      "args": ["-y", "cronalert-mcp"],
      "env": {
        "CRONALERT_API_KEY": "ca_your_api_key_here"
      }
    }
  }
}

Claude Code — run:

claude mcp add cronalert -e CRONALERT_API_KEY=ca_your_key -- npx -y cronalert-mcp

Cursor — add to .cursor/mcp.json:

{
  "mcpServers": {
    "cronalert": {
      "command": "npx",
      "args": ["-y", "cronalert-mcp"],
      "env": {
        "CRONALERT_API_KEY": "ca_your_api_key_here"
      }
    }
  }
}

Remote server (no install needed) — connect any MCP client to:

https://cronalert.com/mcp

Authenticate with Authorization: Bearer cayourkey header. Supports Streamable HTTP transport.

3. Start using it

Ask your AI assistant to manage your monitors (see examples below).

Available Tools

Security & permissions

Approvals in MCP clients are client-side: write tools carry destructiveHint: true, so Claude Code / Desktop / Cursor prompt before running them. CronAlert adds two server-side boundaries so the client prompt isn't the only gate:

Read-only API keys. A read-only key is rejected on every write endpoint (create/update/delete/import) with a 403 — enforced by the server, regardless of the client. Hand agents a read-only key and destructive tools simply cannot succeed. This is the strongest boundary and the recommended default.
Confirmation tokens for deletes. If a read-write key has "require confirmation" enabled, deletemonitor first returns a preview plus a short-lived, resource-bound confirmToken instead of deleting. The agent must call deletemonitor again with that token in the confirm argument. This prevents a single stray or prompt-injected call from destroying data and gives the server an auditable, explicit second step.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Cronalert: common questions

Is Cronalert MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Cronalert safety report
How do I install Cronalert?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Cronalert need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Cronalert maintained?: The last commit was 40 days ago (2026-09-25). The latest release is v1.5.1.
What can I use instead of Cronalert?: Servers from other publishers that do the same job: openstatus MCP server and OneUptime MCP server.
How does Cronalert compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 12 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Cronalert

Same job from other publishers: the closest match first, then the best rated.

openstatus
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
not reviewed
Established
A
OneUptime
Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
not reviewed
Established
A