healthchecksio-mcp
# healthchecksio-mcp
<!-- mcp-name: io.github.nguyenhuy158/healthchecksio-mcp -->
π¬π§ English Β· [π»π³ TiαΊΏng Viα»t](./README-vi.md)
MCP server for the Healthchecks.io API. Lets Claude manage checks, channels, badges, and send pings.
## Install (dev)
```bash
pnpm install
pnpm run build
```
(npm also works: `npm install && npm run build`)
## Env config
- `HEALTHCHECKS_API_KEY` (required) β API key from Settings > API Access on healthchecks.io.
- `HEALTHCHECKS_API_URL` (optional) β defaults to `https://healthchecks.io/api/v3`. Change if self-hosting.
- `HEALTHCHECKS_PING_URL` (optional) β defaults to `https://hc-ping.com`. Change if self-hosting.
## Register with Claude Code
Install straight from GitHub, no clone needed (pnpm preferred):
```bash
claude mcp add healthchecksio -e HEALTHCHECKS_API_KEY=your-key -- pnpm dlx github:nguyenhuy158/healthchecksio-mcp
```
npm also works:
```bash
claude mcp add healthchecksio -e HEALTHCHECKS_API_KEY=your-key -- npx -y github:nguyenhuy158/healthchecksio-mcp
```
Or run from a local build, adding to `.mcp.json` / `claude_desktop_config.json`:
```json
{
"mcpServers": {
"healthchecksio": {
"command": "node",
"args": ["/path/to/healthchecksio-mcp/build/index.js"],
"env": {
"HEALTHCHECKS_API_KEY": "your-key"
}
}
}
}
```
## Tools
- `list_checks` β list checks, filter by tag/status
- `get_check` β get a single check's details
- `create_check` β create a new check
- `update_check` β update a check
- `pause_check` / `resume_check`
- `delete_check`
- `list_check_flips` β up/down status history
- `list_channels` β notification channels
- `list_badges` β badge URLs
- `ping` β send a heartbeat ping (success/fail/start/log)
TDQS
Scored across 11 tools
Each tool targets a specific resource and action: checks (CRUD, pause/resume, flips), channels, badges, and ping. No two tools have overlapping purposes, and actions like pause vs. resume are clearly distinct.
All tools follow a consistent verb_noun pattern in snake_case (list_checks, get_check, create_check, update_check, delete_check, pause_check, resume_check). The single exception 'ping' is a standard verb for heartbeats and fits the pattern.
11 tools is well-scoped for a health checks server. The set covers the primary resource (checks) with full lifecycle actions, plus supporting resources (channels, badges) and the ping action. No unnecessary bloat or thinness.
The check lifecycle is complete: create, read, update, delete, list, pause, resume. Additional operations like listing flips, channels, badges, and sending pings cover the core functionality of healthchecks.io with no obvious gaps.