MCP server for Healthchecks: inspect, create and adjust cron and uptime checks, and read why one failed
- capability exposure inferred + 6
- tool safety inferred + 2
- trust mitigators mixed − 11
These factors total -3, not 0: the score is bounded to 0–100 after they are summed, so this one is floored at 0. The factors are left as they were applied rather than rewritten to make the column add up.
inferred mixed
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
grade last moved 6d ago · see ecosystem CVEs →
- A · 8 → A · 0
No known CVEs for this server.
- low exfiltration combo get_api_key_info
single tool reads + sends: net, secrets
[](https://mcpobservatory.com/servers/github:ni-c/healthchecks-mcp/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of ni-c.