# healthchecks-mcp

Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.3.0
- **Author:** io.github.ni-c
- **License:** MIT
- **npm:** healthchecks-mcp
- **Source:** https://github.com/ni-c/healthchecks-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-29T08:24:48.593Z
- **Version scanned:** 0.3.0
- **CVEs:** none found by OSV at scan time

## Tools

15 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_checks` — Lists the checks in the project the API key belongs to, newest state
- `get_check` — Fetches one check with all its fields, including the description and
- `list_pings` — Lists recent pings of a check, newest first. The instance caps this at
- `get_ping_body` — Returns the body that was POSTed with one ping — usually the output of
- `list_flips` — Lists the up/down transitions of a check — the history behind its
- `list_integrations` — Lists the notification integrations of the project, with the UUIDs that
- `list_badges` — Lists the status badge URLs of the project, one entry per tag plus "*"
- `get_status` — Checks that the configured Healthchecks instance is reachable and its
- `get_api_key_info` — Reports which instance is configured, whether the API key works, and
- `healthchecks-mcp` — Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed
- `create_check` — Creates a check. Pass either timeout (a simple period) or schedule (a
- `update_check` — Updates a check. Fields that are not given stay unchanged. Two
- `pause_check` — Pauses a check: it stops expecting pings and stops alerting.
- `resume_check` — Resumes a paused check and puts it back into the "new" state, waiting
- `delete_check` — Deletes a check permanently. Its UUID is not recoverable, so every

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"healthchecks\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"healthchecks-mcp\"\n      ],\n      \"env\": {\n        \"HEALTHCHECKS_API_KEY\": \"<YOUR_HEALTHCHECKS_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `HEALTHCHECKS_API_KEY` — Healthchecks API Key (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 51, ceiling 51 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/healthchecks-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/healthchecks-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/healthchecks-mcp
- HTML page: https://forgeregistry.com/registry/healthchecks-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.