Healthchecks.io MCP by usefulapi
io.usefulapi/healthchecksiousefulapi.iostreamable-httpv1.40.4Scanned
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.
12 tools: 5 can delete or cancel things and 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Healthchecks.io MCP by usefulapi can do
The Healthchecks.io MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (5 tools: healthchecksio_create_check, healthchecksio_update_check, healthchecksio_pause_check, healthchecksio_resume_check and 1 more). 7 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 5Claude Code: deny
healthchecksio_create_checkCREATES a new check — this MODIFIES live monitoring config.No findings
Why it is in this group
- The name "healthchecksio_create_check" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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).
Annotations the server declares
- title: Create check
- destructiveHint: true
healthchecksio_delete_checkPERMANENTLY DELETES a check by UUID — this MODIFIES live monitoring config and cannot be undone.No findings
Why it is in this group
- The name "healthchecksio_delete_check" says "delete": a word for removing or ending something.
- The description says "PERMANENTLY DELETES".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Delete check
- destructiveHint: true
healthchecksio_pause_checkPAUSES a check — disables monitoring without deleting it (it stops going down for missed pings until it next receives a ping or is resumed).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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).
Annotations the server declares
- title: Pause check
- destructiveHint: true
healthchecksio_resume_checkRESUMES a paused check — re-enables monitoring.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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).
Annotations the server declares
- title: Resume check
- destructiveHint: true
healthchecksio_update_checkUPDATES an existing check by UUID — this MODIFIES live monitoring config.No findings
Why it is in this group
- The name "healthchecksio_update_check" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Update check
- destructiveHint: true
Only reads 7Show 7 read-only tools
healthchecksio_get_checkGet a single check by its UUID (or its unique read-only key).No findings
Why it is in this group
- The name "healthchecksio_get_check" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get check
- readOnlyHint: true
healthchecksio_get_ping_bodyGet the logged request body of a single ping, returned as PLAIN TEXT (verbatim, not JSON).No findings
Why it is in this group
- The name "healthchecksio_get_ping_body" says "get": a word for reading.
Description, as the server wrote it Get the logged request body of a single ping, returned as PLAIN TEXT (verbatim, not JSON). Healthchecks: GET /checks/{uuid}/pings/{n}/body.
Annotations the server declares
- title: Get ping body
- readOnlyHint: true
healthchecksio_list_badgesList the project's status-badge URLs per tag (plus "*" for the overall status) — {badges:{...}}.No findings
Why it is in this group
- The name "healthchecksio_list_badges" says "list": a word for reading.
Description, as the server wrote it List the project's status-badge URLs per tag (plus "*" for the overall status) — {badges:{...}}. Healthchecks: GET /badges/.
Annotations the server declares
- title: List badges
- readOnlyHint: true
healthchecksio_list_checksList all checks in the project, optionally filtered by slug and/or tags.No findings
Why it is in this group
- The name "healthchecksio_list_checks" says "list": a word for reading.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List checks
- readOnlyHint: true
healthchecksio_list_flipsList a check's status changes ("flips") over time — [{timestamp, up}].No findings
Why it is in this group
- The name "healthchecksio_list_flips" says "list": a word for reading.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List flips
- readOnlyHint: true
healthchecksio_list_integrationsList the project's notification integrations ("channels") — {channels:[{id, name, kind}]}.No findings
Why it is in this group
- The name "healthchecksio_list_integrations" says "list": a word for reading.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List integrations
- readOnlyHint: true
healthchecksio_list_pingsList a check's logged pings (100 on the free plan, 1000 on paid), most recent first.No findings
Why it is in this group
- The name "healthchecksio_list_pings" says "list": a word for reading.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List pings
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://healthchecksio.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://healthchecksio.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://healthchecksio.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://healthchecksio.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http healthchecksio https://healthchecksio.usefulapi.io/mcpclaude mcp add --transport http healthchecksio https://healthchecksio.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__healthchecksio__healthchecksio_list_checks",
"mcp__healthchecksio__healthchecksio_get_check",
"mcp__healthchecksio__healthchecksio_list_pings",
"mcp__healthchecksio__healthchecksio_get_ping_body",
"mcp__healthchecksio__healthchecksio_list_flips",
"mcp__healthchecksio__healthchecksio_list_integrations",
"mcp__healthchecksio__healthchecksio_list_badges"
],
"ask": [],
"deny": [
"mcp__healthchecksio__healthchecksio_create_check",
"mcp__healthchecksio__healthchecksio_update_check",
"mcp__healthchecksio__healthchecksio_pause_check",
"mcp__healthchecksio__healthchecksio_resume_check",
"mcp__healthchecksio__healthchecksio_delete_check"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as healthchecksio. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/healthchecksio/verify?hash=c533a8cd6df88a88afacdd4fab624005223e5684eb7a688a1e3bd896a28b8004" | jq -e '.changed == false'Pinned hash c533a8cd6df8, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/healthchecksio/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/healthchecksio)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Healthchecks.io MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Healthchecks.io MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 12 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Healthchecks.io MCP by usefulapi delete data?
- Yes. 5 tools can delete, cancel or revoke something: healthchecksio_create_check, healthchecksio_update_check, healthchecksio_pause_check, healthchecksio_resume_check and healthchecksio_delete_check.
Can the Healthchecks.io MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Healthchecks.io MCP by usefulapi have?
- 12 tools: 5 destructive, 7 read. healthchecksio_create_check, healthchecksio_update_check, healthchecksio_pause_check, healthchecksio_resume_check, healthchecksio_delete_check, healthchecksio_list_checks, healthchecksio_get_check, healthchecksio_list_pings and 4 more.
Does the Healthchecks.io MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Healthchecks.io MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Healthchecks.io MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.