Healthchecks.io MCP by usefulapi
Server Details
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.
- Status
- Healthy
- Uptime
- 71.1% over 59 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Scored across 12 tools
Each tool maps to a distinct resource and action: check CRUD, pause/resume, pings, flips, badges, and integrations. The only potentially related pair, list_pings and get_ping_body, is clearly separated by metadata vs raw body.
All tools follow a clean verb_noun snake_case pattern, with list_* for collections and get_/create_/update_/delete_/pause_/resume_ for single-resource actions. There are no mixed casing styles or inconsistent verb choices.
12 tools is well within the ideal range for this domain, and each tool covers a distinct, necessary operation for managing and inspecting Healthchecks monitoring. The set feels complete without being bloated.
The check lifecycle is fully covered with create, get, update, delete, pause, and resume, plus history and supporting data like pings, flips, badges, and integrations. The main minor gap is that there is no tool to send a ping or manually trigger a check success/failure, so end-to-end ping verification must happen out-of-band.
Available Tools
12 toolshealthchecksio_create_checkCreate checkDestructiveInspect
CREATES a new check — this MODIFIES live monitoring config. Provide a timeout (simple period-based check) OR a schedule + tz (cron-based check); the two are mutually exclusive. Use unique to avoid creating duplicates. Assign notifications via channels. Healthchecks: POST /checks/. Returns the created check (201) or the existing match (200).
| Name | Required | Description | Default |
|---|---|---|---|
| tz | No | Server's timezone for the cron `schedule`, e.g. "Europe/Riga". | |
| desc | No | Free-form description of the check. | |
| name | No | Human-readable name for the check. | |
| slug | No | URL slug (used for slug-based ping URLs). | |
| tags | No | Space-separated list of tags, e.g. "prod db backups". | |
| grace | No | Grace time in seconds after the deadline before the check goes down. | |
| unique | No | Dedupe fields — if a check already matches on these (e.g. ["name"]), it is returned instead of created. | |
| methods | No | Allowed ping HTTP methods: "" (any) or "POST" (POST-only). | |
| timeout | No | Expected period between pings, in seconds (60..31536000). Mutually exclusive with `schedule`. | |
| channels | No | Integrations to assign: "*" for all, or a comma-separated list of integration ids. | |
| schedule | No | Cron expression for the expected ping schedule (e.g. "15 5 * * *"). Mutually exclusive with `timeout`; requires `tz`. | |
| manual_resume | No | If true, a paused check does not auto-resume on the next ping (resume manually). |
healthchecksio_delete_checkDelete checkDestructiveInspect
PERMANENTLY DELETES a check by UUID — this MODIFIES live monitoring config and cannot be undone. Healthchecks: DELETE /checks/{uuid}. Returns the deleted check's last known state.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID to delete. |
healthchecksio_get_checkGet checkRead-onlyInspect
Get a single check by its UUID (or its unique read-only key). Returns the check's full state — status, timeout/schedule, grace, tags, last ping. Healthchecks: GET /checks/{uuid}.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID, or its unique read-only key. |
healthchecksio_get_ping_bodyGet ping bodyRead-onlyInspect
Get the logged request body of a single ping, returned as PLAIN TEXT (verbatim, not JSON). Healthchecks: GET /checks/{uuid}/pings/{n}/body.
| Name | Required | Description | Default |
|---|---|---|---|
| n | Yes | The ping's sequence number (the `n` field from list_pings). | |
| uuid | Yes | The check's UUID. |
healthchecksio_list_badgesList badgesRead-onlyInspect
List the project's status-badge URLs per tag (plus "*" for the overall status) — {badges:{...}}. Healthchecks: GET /badges/.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
healthchecksio_list_checksList checksRead-onlyInspect
List all checks in the project, optionally filtered by slug and/or tags. Returns {checks:[...]} — each check's status, schedule, last ping, and ping URL. Healthchecks: GET /checks/.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Filter to checks carrying ALL of these tags (each is sent as a separate `tag` query param). | |
| slug | No | Filter to checks with this exact slug. |
healthchecksio_list_flipsList flipsRead-onlyInspect
List a check's status changes ("flips") over time — [{timestamp, up}]. Optionally scope by a lookback window or an explicit start/end range. Healthchecks: GET /checks/{uuid}/flips/.
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | Return only flips at/before this Unix timestamp. | |
| uuid | Yes | The check's UUID. | |
| start | No | Return only flips at/after this Unix timestamp. | |
| seconds | No | Return only flips from the last N seconds. |
healthchecksio_list_integrationsList integrationsRead-onlyInspect
List the project's notification integrations ("channels") — {channels:[{id, name, kind}]}. The ids are what you assign to a check's channels field. Healthchecks: GET /channels/.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
healthchecksio_list_pingsList pingsRead-onlyInspect
List a check's logged pings (100 on the free plan, 1000 on paid), most recent first. Each ping: type, date, n, scheme, remote_addr, method, ua, rid, duration, body_url. Healthchecks: GET /checks/{uuid}/pings/.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID. |
healthchecksio_pause_checkPause checkDestructiveInspect
PAUSES a check — disables monitoring without deleting it (it stops going down for missed pings until it next receives a ping or is resumed). This MODIFIES live monitoring config. Healthchecks: POST /checks/{uuid}/pause (empty body).
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID to pause. |
healthchecksio_resume_checkResume checkDestructiveInspect
RESUMES a paused check — re-enables monitoring. This MODIFIES live monitoring config. Returns HTTP 409 (surfaced cleanly) if the check is not currently paused. Healthchecks: POST /checks/{uuid}/resume (empty body).
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID to resume. |
healthchecksio_update_checkUpdate checkDestructiveInspect
UPDATES an existing check by UUID — this MODIFIES live monitoring config. Send only the fields you want to change (timeout and schedule remain mutually exclusive). Healthchecks: POST /checks/{uuid}. Returns the updated check.
| Name | Required | Description | Default |
|---|---|---|---|
| tz | No | Server's timezone for the cron `schedule`, e.g. "Europe/Riga". | |
| desc | No | Free-form description of the check. | |
| name | No | Human-readable name for the check. | |
| slug | No | URL slug (used for slug-based ping URLs). | |
| tags | No | Space-separated list of tags, e.g. "prod db backups". | |
| uuid | Yes | The check's UUID to update. | |
| grace | No | Grace time in seconds after the deadline before the check goes down. | |
| unique | No | Dedupe fields — if a check already matches on these (e.g. ["name"]), it is returned instead of created. | |
| methods | No | Allowed ping HTTP methods: "" (any) or "POST" (POST-only). | |
| timeout | No | Expected period between pings, in seconds (60..31536000). Mutually exclusive with `schedule`. | |
| channels | No | Integrations to assign: "*" for all, or a comma-separated list of integration ids. | |
| schedule | No | Cron expression for the expected ping schedule (e.g. "15 5 * * *"). Mutually exclusive with `timeout`; requires `tz`. | |
| manual_resume | No | If true, a paused check does not auto-resume on the next ping (resume manually). |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
12 tool updates
- Changed
healthchecksio_create_check1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_delete_check1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_get_check1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_get_ping_body1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_list_badges1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_list_checks1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_list_flips1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_list_integrations1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_list_pings1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_pause_check1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_resume_check1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
healthchecksio_update_check1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
12 tool updates
- First observed
healthchecksio_create_check - First observed
healthchecksio_delete_check - First observed
healthchecksio_get_check - First observed
healthchecksio_get_ping_body - First observed
healthchecksio_list_badges - First observed
healthchecksio_list_checks - First observed
healthchecksio_list_flips - First observed
healthchecksio_list_integrations - First observed
healthchecksio_list_pings - First observed
healthchecksio_pause_check - First observed
healthchecksio_resume_check - First observed
healthchecksio_update_check
Related MCP Connectors
Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules.
Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks.
Self-hostable uptime monitoring: create checks, read incidents, manage status pages.
Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Healthchecks.io, allowing users to list, create, update, pause, resume, and delete checks, as well as view ping history and integrations.189 npm1MIT
- AlicenseAqualityAmaintenanceMCP server for Healthchecks: inspect, create and adjust cron and uptime checks, and read why one failed1441 npmMIT
- AlicenseAqualityBmaintenanceConnects MCP-capable AI clients to a monitoring API to inspect cron and recurring-task checks, with opt-in mutations for pings, integrations, and check changes.31MIT
- AlicenseAqualityBmaintenanceEnables managing Uptime Kuma monitoring through natural language, including creating, editing, pausing, and deleting monitors, plus retrieving heartbeats, status, metrics, notifications, and status pages.12MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.