Healthchecks
io.github.ni-c/healthchecks-mcp
About Healthchecks
Healthchecks is an MCP server published by the GitHub account ni-c. Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed
It runs on your own machine: your AI client starts it from the npm package healthchecks-mcp at version 0.3.0.
It asks for one secret: HEALTHCHECKS_API_KEY. Give it a key with the least access that still works.
Version 0.3.0 was published on 7 September 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
HEALTHCHECKS_API_KEY | Yes | Yes | Project API key, exactly 32 characters, from Project Settings → API Access |
HEALTHCHECKS_URL | No | No | Site root of a self-hosted instance, e.g. https://hc.example.net (default: https://healthchecks.io) |
HEALTHCHECKS_READ_ONLY | No | No | Set to true to register only the read tools (default: false) |
HEALTHCHECKS_ALLOW_TOOLS | No | No | Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools) |
HEALTHCHECKS_DENY_TOOLS | No | No | Comma-separated tool names or list_* prefixes to remove from whatever the allow list left |
HEALTHCHECKS_INSECURE_TLS | No | No | Set to true to accept a self-signed certificate from a self-hosted instance (default: false) |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/ni-c/healthchecks-mcp |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for 1 secret: HEALTHCHECKS_API_KEY |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account ni-c |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | healthchecks-mcp@0.3.0 runs nothing at install |
| Code red flags | Pass | Read 30 files in healthchecks-mcp@0.3.0: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 30 files, including comments and the README |
Popularity & health: 59 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
0 forks, 49 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.ni-c/healthchecks-mcp |
|---|---|
| Publisher | GitHub account ni-c |
| How the name is verified | Name verified via GitHub account ni-c. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm healthchecks-mcp 0.3.0 (stdio)oci ghcr.io/ni-c/healthchecks-mcp:0.3.0 no version given (stdio) |
| Version | 0.3.0 |
| Published | |
| Last updated | |
| Source repository | https://github.com/ni-c/healthchecks-mcp |
| Website | https://healthchecks-mcp.ni-c.de |
| Category | Analytics & monitoring (assigned by keyword rule, not by hand) |
Related servers in Analytics & monitoring
- nimo3/3Website monitoring: uptime alerts, page speed and Core Web Vitals…
- Mettler Toledo Balance7/7MCP server for Mettler Toledo laboratory balances (MT-SICS): weigh,…
- displaybuddy-mcp7/7MCP server for controlling Mac monitors via DisplayBuddy — adjust…
- SolidPing3/3Self-hostable uptime monitoring: create checks, read incidents,…
Exit1 Uptime Monitoring8/8Set up uptime monitoring from your editor: create checks, alerts,…
UptimeRobot3/3Monitor websites, APIs, and servers: create monitors, triage…