# io.usefulapi/healthchecksio (remote · healthchecksio.usefulapi.io)

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

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `healthchecksio.usefulapi.io`: 72/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-healthchecksio/healthchecksio.md), [page](https://verifymcp.io/servers/io-usefulapi-healthchecksio/healthchecksio)

## Channel facts

- Endpoint: `https://healthchecksio.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-healthchecksio https://healthchecksio.usefulapi.io/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-healthchecksio --url https://healthchecksio.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-healthchecksio:
    url: "https://healthchecksio.usefulapi.io/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 72, +54)

- [security improvement] Authorization: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Tool coverage: unverified → 100

### 2026-08-01 (score 18, −53)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified

### 2026-07-31 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 71, +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.

### 2026-07-29 (score 70, +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.

### 2026-07-28 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 69, +57)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 12)

First indexed and scored.

## MCP tools (12)

### `healthchecksio_list_checks` (~95 tokens)

List checks

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

Input parameters:

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

### `healthchecksio_get_check` (~73 tokens)

Get check

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

Input parameters:

- `uuid` (string, required): The check's UUID, or its unique read-only key.

### `healthchecksio_list_pings` (~84 tokens)

List pings

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

Input parameters:

- `uuid` (string, required): The check's UUID.

### `healthchecksio_get_ping_body` (~83 tokens)

Get ping body

Get the logged request body of a single ping, returned as PLAIN TEXT (verbatim, not JSON). Healthchecks: GET /checks/{uuid}/pings/{n}/body.

Input parameters:

- `n` (integer, required): The ping's sequence number (the `n` field from list_pings).
- `uuid` (string, required): The check's UUID.

### `healthchecksio_list_flips` (~116 tokens)

List flips

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

Input parameters:

- `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, required): The check's UUID.

### `healthchecksio_list_integrations` (~54 tokens)

List integrations

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

### `healthchecksio_list_badges` (~45 tokens)

List badges

List the project's status-badge URLs per tag (plus "*" for the overall status) — {badges:{...}}. Healthchecks: GET /badges/.

### `healthchecksio_create_check` (~365 tokens)

Create check

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

Input parameters:

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

### `healthchecksio_update_check` (~343 tokens)

Update check

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.

Input parameters:

- `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, required): The check's UUID to update.

### `healthchecksio_pause_check` (~75 tokens)

Pause check

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

Input parameters:

- `uuid` (string, required): The check's UUID to pause.

### `healthchecksio_resume_check` (~76 tokens)

Resume check

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

Input parameters:

- `uuid` (string, required): The check's UUID to resume.

### `healthchecksio_delete_check` (~66 tokens)

Delete check

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.

Input parameters:

- `uuid` (string, required): The check's UUID to delete.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-healthchecksio/healthchecksio#diagnostics

## Score history

- 2026-08-03: 72
- 2026-08-02: 72
- 2026-08-01: 18
- 2026-07-31: 71
- 2026-07-30: 71
- 2026-07-29: 70
- 2026-07-28: 69
- 2026-07-27: 69
- 2026-07-26: 12

## Links

- Remote endpoint: https://healthchecksio.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-healthchecksio/healthchecksio/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-healthchecksio/healthchecksio/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-healthchecksio/healthchecksio