healthchecksio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEALTHCHECKS_API_KEY | Yes | API key from Settings > API Access on healthchecks.io. | |
| HEALTHCHECKS_API_URL | No | Defaults to https://healthchecks.io/api/v3. Change if self-hosting. | https://healthchecks.io/api/v3 |
| HEALTHCHECKS_PING_URL | No | Defaults to https://hc-ping.com. Change if self-hosting. | https://hc-ping.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_checksA | List all checks in the project. Optionally filter by tag or status. |
| get_checkA | Get details of a single check by its UUID. |
| create_checkC | Create a new check. |
| update_checkC | Update an existing check's configuration. |
| pause_checkB | Pause monitoring for a check. |
| resume_checkA | Resume monitoring for a paused check (cron/schedule based checks only). |
| delete_checkB | Permanently delete a check. |
| list_check_flipsA | List status change history (up/down flips) for a check. |
| list_channelsA | List all notification channels (email, Slack, webhook, etc.) in the project. |
| list_badgesA | List status badge URLs for the project, per tag. |
| pingA | Send a ping (heartbeat) signal for a check. Use this to report success, failure, or manually test a check. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.