Is Cronalert MCP server safe?
Yes, with the usual care.
Passed every safety check we run. Maintained, authenticated, reachable, clean scan.
No critical or high findings in the latest scan.
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 that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
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.
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 used
exec.evaldist/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.RubricAppeal a findingJSON
Other servers that do what Cronalert does
openstatusManage monitors, status pages, incidents and maintenances in your openstatus workspace.not reviewedEstablishedA
OneUptimeManage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.not reviewedEstablishedA