io.usefulapi/healthchecksio
REMOTE · HEALTHCHECKSIO.USEFULAPI.IO · SCANNED SEP 20
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1475 tokens (~122/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/healthchecksio MCP server?
io.usefulapi/healthchecksio 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'
{
"mcpServers": {
"io-usefulapi-healthchecksio": {
"url": "https://healthchecksio.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-healthchecksio": {
"type": "http",
"url": "https://healthchecksio.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-healthchecksio] url = "https://healthchecksio.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-healthchecksio": {
"type": "remote",
"url": "https://healthchecksio.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-healthchecksio --url 'https://healthchecksio.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-healthchecksio:
url: "https://healthchecksio.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-healthchecksio": {
"Transport": "http",
"Url": "https://healthchecksio.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-healthchecksio -t streamable-http -u 'https://healthchecksio.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-healthchecksio": {
"type": "http",
"url": "https://healthchecksio.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Aug 26 0
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- 1 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 20 Sept 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 | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a7c059043012d575138324c00fce5bae |
| SANs: usefulapi.io, healthchecksio.usefulapi.io, *.healthchecksio.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 | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://healthchecksio.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://healthchecksio.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://healthchecksio.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://healthchecksio.usefulapi.io/mcp |
| Authorisation server | https://healthchecksio.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://healthchecksio.usefulapi.io/mcp | Inconclusive | 401 |
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.
What is the io.usefulapi/healthchecksio MCP server?
io.usefulapi/healthchecksio is an MCP server 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 io.usefulapi/healthchecksio MCP server safe to use?
io.usefulapi/healthchecksio scores 86 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 io.usefulapi/healthchecksio MCP server expose?
io.usefulapi/healthchecksio 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 io.usefulapi/healthchecksio MCP server require authentication?
Yes. io.usefulapi/healthchecksio asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/healthchecksio MCP server still maintained?
io.usefulapi/healthchecksio is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.