{
  "markdown": "# @digitalronin/healthchecks-io-mcp\n\n> **Unofficial, unaffiliated with Healthchecks.io.** This is a third-party\n> MCP server, not an official Healthchecks.io product.\n\n## What this is\n\n[Healthchecks.io](https://healthchecks.io) is a \"dead man's switch\" style\nmonitoring service: your scheduled jobs (cron jobs, backups, batch scripts,\nanything that's supposed to run on a schedule) ping it when they run, and\nHealthchecks.io alerts you if a ping doesn't show up on time — meaning the\njob silently failed or never ran.\n\nThis package is an **MCP server** — a small local program that lets an AI\nassistant like Claude talk to Healthchecks.io's\n[Management API](https://healthchecks.io/docs/api/) on your behalf. Once\nit's set up, you can ask your AI assistant things like \"list my\nHealthchecks.io checks,\" \"show me the ping history for my backup job,\" or\n\"pause monitoring for my staging environment\" in plain English, and it\nwill call the right Healthchecks.io API endpoint for you.\n\n## Setup\n\n### 1. Get a Healthchecks.io API key\n\n1. Log in to [healthchecks.io](https://healthchecks.io) (or your\n   self-hosted instance, see below).\n2. Go to your project's **Settings** page, then the **API Access** tab.\n3. You'll see two keys: a **read-only** key and a **read-write** key.\n   - The **read-only** key can look up your checks, but can't create,\n     change, pause, or delete anything.\n   - The **read-write** key can do everything the read-only key can, plus\n     create, update, pause, resume, and **permanently delete** checks.\n\n### 2. Add this server to your MCP client's config\n\nYou don't need to install anything manually — `npx` will download and run\nit automatically the first time it's used. Add this block to your MCP\nclient's configuration (for Claude Code, this is a `.mcp.json` file; other\nclients have their own config file or UI for this):\n\n```json\n{\n  \"mcpServers\": {\n    \"healthchecks-io\": {\n      \"command\": \"npx\",\n      \"args\": [\"@digitalronin/healthchecks-io-mcp\"],\n      \"env\": {\n        \"HEALTHCHECKS_API_KEY\": \"your-key-here\"\n      }\n    }\n  }\n}\n```\n\nReplace `\"your-key-here\"` with the API key from step 1. Restart your MCP\nclient (or reload its MCP connections) after saving this — most clients\nonly pick up new/changed servers on restart.\n\n### 3. Try it out\n\nOnce connected, just ask your AI assistant something like:\n\n- \"List all my Healthchecks.io checks\"\n- \"Show me the ping history for my nightly-backup check\"\n- \"Is my staging-cron check currently failing?\"\n\nIf it responds with real data from your account, you're set up correctly.\n\n### Optional: multiple projects\n\nHealthchecks.io API keys are scoped per project, so a single server entry\nonly ever talks to one project. To work with more than one, register the\nserver multiple times under different names, each with its own key:\n\n```json\n{\n  \"mcpServers\": {\n    \"healthchecks-io-personal\": {\n      \"command\": \"npx\",\n      \"args\": [\"@digitalronin/healthchecks-io-mcp\"],\n      \"env\": {\n        \"HEALTHCHECKS_API_KEY\": \"personal-project-key-here\"\n      }\n    },\n    \"healthchecks-io-work\": {\n      \"command\": \"npx\",\n      \"args\": [\"@digitalronin/healthchecks-io-mcp\"],\n      \"env\": {\n        \"HEALTHCHECKS_API_KEY\": \"work-project-key-here\"\n      }\n    }\n  }\n}\n```\n\nEach entry runs its own process holding a single key, and MCP clients\nnamespace tools by server name, so you can tell which project a tool call\nis hitting.\n\n### Optional: self-hosted Healthchecks.io\n\nHealthchecks.io is open source, and some people run their own instance\ninstead of using the hosted SaaS service at healthchecks.io. If that's\nyou, add a second environment variable pointing at your instance's API\nroot:\n\n```json\n\"env\": {\n  \"HEALTHCHECKS_API_KEY\": \"your-key-here\",\n  \"HEALTHCHECKS_BASE_URL\": \"https://monitoring.example.com/api/v3\"\n}\n```\n\nThe URL must be the full API root, **including the `/api/v3` path\nsegment**, with **no trailing slash** — e.g.\n`https://monitoring.example.com/api/v3`, not\n`https://monitoring.example.com` or\n`https://monitoring.example.com/api/v3/`. Getting this wrong will make\nevery tool call fail with a \"not found\" error, since the server appends\npaths like `/checks/` directly onto whatever you set here. If you leave\n`HEALTHCHECKS_BASE_URL` unset, it defaults to the real\n`https://healthchecks.io/api/v3`.\n\nIf your self-hosted instance isn't behind HTTPS, the server will print a\nwarning (but still run) — your API key is sent as a request header on\nevery call, so an `http://` URL means that key travels in plaintext over\nthe network to your instance.\n\n## What it can do\n\nThis server exposes 11 \"tools\" that your AI assistant can call. They fall\ninto two groups:\n\n**Read tools** — safe, look-up-only, never change anything:\n\n| Tool                | What it does                                                                                                                  |\n| ------------------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `list_checks`       | List every check in your account.                                                                                             |\n| `get_check`         | Get full details for one specific check.                                                                                      |\n| `list_check_pings`  | Show the recent ping history for a check (when it pinged in, success/fail/etc). _Requires a read-write key — see note below._ |\n| `list_check_flips`  | Show when a check's status changed (e.g. went from healthy to failing, or back).                                              |\n| `list_integrations` | List your configured notification integrations (Slack, email, etc). _Requires a read-write key — see note below._             |\n| `list_badges`       | Get the badge image URLs Healthchecks.io generates for each of your tags (useful for status pages/dashboards).                |\n\n**Mutating tools** — these change things in your account, and all of them\nrequire a **read-write** API key:\n\n| Tool           | What it does                                                                                                                                                                                                                                                                                  |\n| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `create_check` | Create a new check (e.g. \"create a check called nightly-backup that expects a ping every 24 hours\"). Can optionally be told to match on existing fields (like the check's name) and update that check instead of creating a duplicate — useful if a job might register itself more than once. |\n| `update_check` | Change an existing check's settings. Only the fields you specify are changed — anything you don't mention stays as it was.                                                                                                                                                                    |\n| `pause_check`  | Temporarily stop monitoring a check, without deleting it. **Requires explicit confirmation** — see below.                                                                                                                                                                                     |\n| `resume_check` | Resume monitoring on a paused check.                                                                                                                                                                                                                                                          |\n| `delete_check` | **Permanently delete** a check — this cannot be undone. **Requires explicit confirmation** — see below.                                                                                                                                                                                       |\n\n## Technical reference\n\nFor each tool, this table gives its underlying Healthchecks.io API\nendpoint:\n\n| Tool                | Requires read-write key? | Healthchecks.io API endpoint                                                               |\n| ------------------- | ------------------------ | ------------------------------------------------------------------------------------------ |\n| `list_checks`       | No                       | [`GET /api/v3/checks/`](https://healthchecks.io/docs/api/#list-checks)                     |\n| `get_check`         | No                       | [`GET /api/v3/checks/{uuid}`](https://healthchecks.io/docs/api/#get-check)                 |\n| `list_check_pings`  | Yes                      | [`GET /api/v3/checks/{uuid}/pings/`](https://healthchecks.io/docs/api/#list-pings)         |\n| `list_check_flips`  | No                       | [`GET /api/v3/checks/{uuid}/flips/`](https://healthchecks.io/docs/api/#list-flips)         |\n| `list_integrations` | Yes                      | [`GET /api/v3/channels/`](https://healthchecks.io/docs/api/#list-channels)                 |\n| `list_badges`       | No                       | [`GET /api/v3/badges/`](https://healthchecks.io/docs/api/#list-badges)                     |\n| `create_check`      | Yes                      | [`POST /api/v3/checks/`](https://healthchecks.io/docs/api/#create-check)                   |\n| `update_check`      | Yes                      | [`POST /api/v3/checks/{uuid}`](https://healthchecks.io/docs/api/#update-check)             |\n| `pause_check`       | Yes                      | [`POST /api/v3/checks/{uuid}/pause`](https://healthchecks.io/docs/api/#pause-monitoring)   |\n| `resume_check`      | Yes                      | [`POST /api/v3/checks/{uuid}/resume`](https://healthchecks.io/docs/api/#resume-monitoring) |\n| `delete_check`      | Yes                      | [`DELETE /api/v3/checks/{uuid}`](https://healthchecks.io/docs/api/#delete-check)           |\n",
  "bytes": 10163,
  "sha": "cd7d17fecb4898e75c7da73ca316589d6d94f2018448d418a0f1f7018c3cb199",
  "repo_slug": "ronniechong/healthchecks-io-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_ronniechong_healthchecks_io_mc_3bde453e/readme"
}