Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.usefulapi/healthchecksio

REMOTE · HEALTHCHECKSIO.USEFULAPI.IO · SCANNED AUG 3

Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.

+3 this week 72 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security78
Transport & Reachability100
Schema Quality & AI Usability74
  • 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · healthchecksio.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-healthchecksio https://healthchecksio.usefulapi.io/mcp
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-healthchecksio]
url = "https://healthchecksio.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-healthchecksio": {
      "type": "remote",
      "url": "https://healthchecksio.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-healthchecksio --url https://healthchecksio.usefulapi.io/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-healthchecksio:
    url: "https://healthchecksio.usefulapi.io/mcp"
// mcp.json
{
  "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.

Changelog

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 Aug 26 +54
    • Authorization: unverified → pass security
    • Transport: fail → pass security
    • MCP protocol: unverified → fail functional
    • Endpoint reachability: not serving MCP → reachable functional
    • Stability: unverified → 0.20 functional
    • Tool coverage: unverified → 100 functional
  • 1 Aug 26 −53
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.13 → unverified security
    • Authorization: pass → unverified security
    • Transport: pass → fail security
    • Tool coverage: 100 → unverified functional
    • Capabilities: fail → 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
  • 30 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 0
    • Stability: unverified → 0.03 functional
  • 27 Jul 26 +57
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 12

    First indexed and scored.

Diagnostics

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 3 Aug 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 19 Jul 2026 17 Oct 2026 ECDSA 256 ECDSA-SHA256 7b2a32d1467a9f130e6407c4e384047a
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
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
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
MCP tools — 12 exposed · ~1,475 tokens

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.

Tool Tokens
healthchecksio_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).

NameTypeReqDescription
channelsstringIntegrations to assign: "*" for all, or a comma-separated list of integration ids.
descstringFree-form description of the check.
graceintegerGrace time in seconds after the deadline before the check goes down.
manual_resumebooleanIf true, a paused check does not auto-resume on the next ping (resume manually).
methodsstringAllowed ping HTTP methods: "" (any) or "POST" (POST-only).
namestringHuman-readable name for the check.
schedulestringCron expression for the expected ping schedule (e.g. "15 5 * * *"). Mutually exclusive with `timeout`; requires `tz`.
slugstringURL slug (used for slug-based ping URLs).
tagsstringSpace-separated list of tags, e.g. "prod db backups".
timeoutintegerExpected period between pings, in seconds (60..31536000). Mutually exclusive with `schedule`.
tzstringServer's timezone for the cron `schedule`, e.g. "Europe/Riga".
uniquearrayDedupe 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 ~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.

NameTypeReqDescription
uuidstringyesThe check's UUID to delete.

No output schema declared.

No examples provided.

healthchecksio_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}.

NameTypeReqDescription
uuidstringyesThe check's UUID, or its unique read-only key.

No output schema declared.

No examples provided.

healthchecksio_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.

NameTypeReqDescription
nintegeryesThe ping's sequence number (the `n` field from list_pings).
uuidstringyesThe check's UUID.

No output schema declared.

No examples provided.

healthchecksio_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 ~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/.

NameTypeReqDescription
slugstringFilter to checks with this exact slug.
tagarrayFilter 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 ~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/.

NameTypeReqDescription
endintegerReturn only flips at/before this Unix timestamp.
secondsintegerReturn only flips from the last N seconds.
startintegerReturn only flips at/after this Unix timestamp.
uuidstringyesThe check's UUID.

No output schema declared.

No examples provided.

healthchecksio_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 ~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/.

NameTypeReqDescription
uuidstringyesThe check's UUID.

No output schema declared.

No examples provided.

healthchecksio_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).

NameTypeReqDescription
uuidstringyesThe check's UUID to pause.

No output schema declared.

No examples provided.

healthchecksio_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).

NameTypeReqDescription
uuidstringyesThe check's UUID to resume.

No output schema declared.

No examples provided.

healthchecksio_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.

NameTypeReqDescription
channelsstringIntegrations to assign: "*" for all, or a comma-separated list of integration ids.
descstringFree-form description of the check.
graceintegerGrace time in seconds after the deadline before the check goes down.
manual_resumebooleanIf true, a paused check does not auto-resume on the next ping (resume manually).
methodsstringAllowed ping HTTP methods: "" (any) or "POST" (POST-only).
namestringHuman-readable name for the check.
schedulestringCron expression for the expected ping schedule (e.g. "15 5 * * *"). Mutually exclusive with `timeout`; requires `tz`.
slugstringURL slug (used for slug-based ping URLs).
tagsstringSpace-separated list of tags, e.g. "prod db backups".
timeoutintegerExpected period between pings, in seconds (60..31536000). Mutually exclusive with `schedule`.
tzstringServer's timezone for the cron `schedule`, e.g. "Europe/Riga".
uniquearrayDedupe fields — if a check already matches on these (e.g. ["name"]), it is returned instead of created.
uuidstringyesThe check's UUID to update.

No output schema declared.

No examples provided.