Healthchecks.io MCP by usefulapi
REMOTE · HEALTHCHECKSIO.USEFULAPI.IO
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “create_or_update_a_check” functional
- New prompt “find_when_a_check_went_down_and_came_back” functional
- New prompt “inspect_the_recent_pings_of_a_check” functional
- New prompt “list_notification_integrations_and_status_badges” functional
- New prompt “pause_or_resume_checks_during_maintenance” functional
- New prompt “see_which_checks_are_down” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 −1
- Stability: pass → 0.93 functional
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://healthchecksio.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of healthchecksio.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://healthchecksio.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/healthchecksio/ |
| http (plaintext) | http://healthchecksio.usefulapi.io/mcp | Inconclusive | 302 | http://healthchecksio.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
healthchecksio_create_check Create check ~365
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 | Type | Req | Description |
|---|---|---|---|
| channels | string | – | Integrations to assign: "*" for all, or a comma-separated list of integration ids. |
| desc | string | – | Free-form description of the check. |
| grace | integer | – | Grace time in seconds after the deadline before the check goes down. |
| manual_resume | boolean | – | If true, a paused check does not auto-resume on the next ping (resume manually). |
| methods | string | – | Allowed ping HTTP methods: "" (any) or "POST" (POST-only). |
| name | string | – | Human-readable name for the check. |
| schedule | string | – | Cron expression for the expected ping schedule (e.g. "15 5 * * *"). Mutually exclusive with `timeout`; requires `tz`. |
| slug | string | – | URL slug (used for slug-based ping URLs). |
| tags | string | – | Space-separated list of tags, e.g. "prod db backups". |
| timeout | integer | – | Expected period between pings, in seconds (60..31536000). Mutually exclusive with `schedule`. |
| tz | string | – | Server's timezone for the cron `schedule`, e.g. "Europe/Riga". |
| unique | array | – | Dedupe fields — if a check already matches on these (e.g. ["name"]), it is returned instead of created. |
No output schema declared.
No examples provided.
healthchecksio_delete_check Delete check ~66
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 | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | The check's UUID to delete. |
No output schema declared.
No examples provided.
healthchecksio_get_check Get check ~73
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 | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | The check's UUID, or its unique read-only key. |
No output schema declared.
No examples provided.
healthchecksio_get_ping_body Get ping body ~83
Get the logged request body of a single ping, returned as PLAIN TEXT (verbatim, not JSON). Healthchecks: GET /checks/{uuid}/pings/{n}/body.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | yes | The ping's sequence number (the `n` field from list_pings). |
| uuid | string | yes | The check's UUID. |
No output schema declared.
No examples provided.
healthchecksio_list_badges List badges ~45
List the project's status-badge URLs per tag (plus "*" for the overall status) — {badges:{...}}. Healthchecks: GET /badges/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
healthchecksio_list_checks List checks ~95
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 | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Filter to checks with this exact slug. |
| tag | array | – | Filter to checks carrying ALL of these tags (each is sent as a separate `tag` query param). |
No output schema declared.
No examples provided.
healthchecksio_list_flips List flips ~116
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 | Type | Req | Description |
|---|---|---|---|
| end | integer | – | Return only flips at/before this Unix timestamp. |
| seconds | integer | – | Return only flips from the last N seconds. |
| start | integer | – | Return only flips at/after this Unix timestamp. |
| uuid | string | yes | The check's UUID. |
No output schema declared.
No examples provided.
healthchecksio_list_integrations List integrations ~54
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/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
healthchecksio_list_pings List pings ~84
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 | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | The check's UUID. |
No output schema declared.
No examples provided.
healthchecksio_pause_check Pause check ~75
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 | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | The check's UUID to pause. |
No output schema declared.
No examples provided.
healthchecksio_resume_check Resume check ~76
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 | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | The check's UUID to resume. |
No output schema declared.
No examples provided.
healthchecksio_update_check Update check ~343
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 | Type | Req | Description |
|---|---|---|---|
| channels | string | – | Integrations to assign: "*" for all, or a comma-separated list of integration ids. |
| desc | string | – | Free-form description of the check. |
| grace | integer | – | Grace time in seconds after the deadline before the check goes down. |
| manual_resume | boolean | – | If true, a paused check does not auto-resume on the next ping (resume manually). |
| methods | string | – | Allowed ping HTTP methods: "" (any) or "POST" (POST-only). |
| name | string | – | Human-readable name for the check. |
| schedule | string | – | Cron expression for the expected ping schedule (e.g. "15 5 * * *"). Mutually exclusive with `timeout`; requires `tz`. |
| slug | string | – | URL slug (used for slug-based ping URLs). |
| tags | string | – | Space-separated list of tags, e.g. "prod db backups". |
| timeout | integer | – | Expected period between pings, in seconds (60..31536000). Mutually exclusive with `schedule`. |
| tz | string | – | Server's timezone for the cron `schedule`, e.g. "Europe/Riga". |
| unique | array | – | Dedupe fields — if a check already matches on these (e.g. ["name"]), it is returned instead of created. |
| uuid | string | yes | The check's UUID to update. |
No output schema declared.
No examples provided.
How do I install the Healthchecks.io MCP by usefulapi server?
Healthchecks.io MCP by usefulapi is a hosted endpoint at https://healthchecksio.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · healthchecksio.usefulapi.io
claude mcp add --transport http io-usefulapi-healthchecksio 'https://healthchecksio.usefulapi.io/mcp'
What is the Healthchecks.io MCP by usefulapi server?
Healthchecks.io MCP by usefulapi is listed in the public MCP registry as io.usefulapi/healthchecksio. Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io. This page covers its hosted endpoint (https://healthchecksio.usefulapi.io/mcp).
Is the Healthchecks.io MCP by usefulapi server safe to use?
Healthchecks.io MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Healthchecks.io MCP by usefulapi server expose?
Healthchecks.io MCP by usefulapi exposes 12 tools: healthchecksio_list_checks, healthchecksio_get_check, healthchecksio_list_pings, healthchecksio_get_ping_body, healthchecksio_list_flips, and 7 more. Their descriptions and schemas cost roughly 1,475 tokens of context every time the server is loaded.
Does the Healthchecks.io MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Healthchecks.io MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Healthchecks.io MCP by usefulapi server still maintained?
Healthchecks.io MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.