Cronalert Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Cronalert Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
MCP server for CronAlert uptime monitoring. Manage your monitors, check results, and incidents from Claude, Cursor, Windsurf, or any MCP-compatible AI client.
Sign up at cronalert.com and create an API key in Settings > API Keys.
Claude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.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-mcpCursor — 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/mcpAuthenticate with Authorization: Bearer ca_your_key header. Supports Streamable HTTP transport.
Ask your AI assistant to manage your monitors (see examples below).
| Tool | Description | Type |
|---|---|---|
list_monitors | List all monitors with status and response times | Read |
create_monitor | Create a new HTTP monitor | Write |
get_monitor | Get details for a specific monitor | Read |
update_monitor | Update settings, pause/resume | Write |
delete_monitor | Permanently delete a monitor | Write |
get_check_results | Check history with uptime % and response times | Read |
get_monitor_incidents | Incidents for a specific monitor | Read |
list_incidents | All active incidents across monitors | Read |
list_status_pages | Your public status pages | Read |
User prompt: "Create a monitor for https://api.example.com/health that checks every minute, then show me its details."
What happens:
create_monitor with name: "API Health", url: "https://api.example.com/health", checkInterval: 60get_monitor with the new ID to show the detailsExpected output:
{
"id": "abc123",
"name": "API Health",
"url": "https://api.example.com/health",
"method": "GET",
"checkInterval": 60,
"lastStatus": "unknown",
"createdAt": "2026-03-08T12:00:00Z"
}User prompt: "Are any of my monitors down? If so, show me the error details."
What happens:
list_incidents to check for active incidentsget_monitor for each affected monitorget_check_results to get the recent error detailsExpected output (no incidents):
{
"data": [],
"message": "No active incidents"
}Expected output (with incident):
{
"data": [
{
"id": "inc_xyz",
"monitorId": "abc123",
"cause": "Expected status 200, got 503",
"startedAt": "2026-03-08T11:45:00Z"
}
]
}User prompt: "List all my monitors, then pause the staging one."
What happens:
list_monitors to get all monitorsupdate_monitor with id: "staging_id" and paused: trueExpected output:
{
"id": "staging_id",
"name": "Staging Server",
"isPaused": true,
"lastStatus": "up"
}This MCP server connects to the CronAlert API (cronalert.com/api/v1/) using your API key. It transmits:
Data is processed by CronAlert's servers on Cloudflare's infrastructure. No data is stored locally by the MCP server itself. See our full Privacy Policy for details on data collection, retention, and your rights.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.