Healthchecks Io Mcp

io.github.ronniechongPublished by GitHub account ronniechongv2.1.2Updated Oct 25, 2026

Unofficial MCP server for managing Healthchecks.io checks via the Management API

VerifiedSTDIODesktop onlyProductivity & WorkflowSecurity & Monitoring

Overview

AI-generated overview

Unofficial local MCP server that lets an assistant list, inspect and manage Healthchecks.io monitoring checks through the Management API.

What you can do
List and inspect checks, including full details for a single check and badge image URLs per tag, plus status-change history (flips). Read ping history for a check and list configured notification integrations. Create new checks, optionally matching existing fields to update instead of duplicating. Update check settings, pause and resume monitoring, or permanently delete a check.
When to use it
Useful when you run scheduled jobs, backups or cron tasks monitored by Healthchecks.io and want to ask an assistant in plain language which checks exist, whether one is failing, or to pause, resume or adjust monitoring.
Requirements
Runs locally via npx (Node.js) as a stdio process. Requires a Healthchecks.io API key in the HEALTHCHECKS_API_KEY environment variable; read-only keys allow lookups only, read-write keys are needed for pings, integrations and all changes. For self-hosted instances, set HEALTHCHECKS_BASE_URL to the full API root including the /api/v3 path and no trailing slash. Network access to Healthchecks.io.
Before you install
The API key is sent as a request header on every call; an http:// self-hosted URL sends it in plaintext. A read-write key can create, change, pause, resume and permanently delete checks, and deletion cannot be undone. Pause and delete require explicit confirmation. Keys are scoped per project, so each server entry reaches only one project. Unofficial and unaffiliated with Healthchecks.io.

Installation

In SourceWeft

  1. Open Healthchecks Io Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@digitalronin/healthchecks-io-mcp

Unofficial, unaffiliated with Healthchecks.io. This is a third-party MCP server, not an official Healthchecks.io product.

What this is

Healthchecks.io is a "dead man's switch" style monitoring service: your scheduled jobs (cron jobs, backups, batch scripts, anything that's supposed to run on a schedule) ping it when they run, and Healthchecks.io alerts you if a ping doesn't show up on time — meaning the job silently failed or never ran.

This package is an MCP server — a small local program that lets an AI assistant like Claude talk to Healthchecks.io's Management API on your behalf. Once it's set up, you can ask your AI assistant things like "list my Healthchecks.io checks," "show me the ping history for my backup job," or "pause monitoring for my staging environment" in plain English, and it will call the right Healthchecks.io API endpoint for you.

Setup

1. Get a Healthchecks.io API key

  1. Log in to healthchecks.io (or your self-hosted instance, see below).
  2. Go to your project's Settings page, then the API Access tab.
  3. You'll see two keys: a read-only key and a read-write key.
    • The read-only key can look up your checks, but can't create, change, pause, or delete anything.
    • The read-write key can do everything the read-only key can, plus create, update, pause, resume, and permanently delete checks.

2. Add this server to your MCP client's config

You don't need to install anything manually — npx will download and run it automatically the first time it's used. Add this block to your MCP client's configuration (for Claude Code, this is a .mcp.json file; other clients have their own config file or UI for this):

json
{  "mcpServers": {    "healthchecks-io": {      "command": "npx",      "args": ["@digitalronin/healthchecks-io-mcp"],      "env": {        "HEALTHCHECKS_API_KEY": "your-key-here"      }    }  }}

Replace "your-key-here" with the API key from step 1. Restart your MCP client (or reload its MCP connections) after saving this — most clients only pick up new/changed servers on restart.

3. Try it out

Once connected, just ask your AI assistant something like:

  • "List all my Healthchecks.io checks"
  • "Show me the ping history for my nightly-backup check"
  • "Is my staging-cron check currently failing?"

If it responds with real data from your account, you're set up correctly.

Optional: multiple projects

Healthchecks.io API keys are scoped per project, so a single server entry only ever talks to one project. To work with more than one, register the server multiple times under different names, each with its own key:

json
{  "mcpServers": {    "healthchecks-io-personal": {      "command": "npx",      "args": ["@digitalronin/healthchecks-io-mcp"],      "env": {        "HEALTHCHECKS_API_KEY": "personal-project-key-here"      }    },    "healthchecks-io-work": {      "command": "npx",      "args": ["@digitalronin/healthchecks-io-mcp"],      "env": {        "HEALTHCHECKS_API_KEY": "work-project-key-here"      }    }  }}

Each entry runs its own process holding a single key, and MCP clients namespace tools by server name, so you can tell which project a tool call is hitting.

Optional: self-hosted Healthchecks.io

Healthchecks.io is open source, and some people run their own instance instead of using the hosted SaaS service at healthchecks.io. If that's you, add a second environment variable pointing at your instance's API root:

json
"env": {  "HEALTHCHECKS_API_KEY": "your-key-here",  "HEALTHCHECKS_BASE_URL": "https://monitoring.example.com/api/v3"}

The URL must be the full API root, including the /api/v3 path segment, with no trailing slash — e.g. https://monitoring.example.com/api/v3, not https://monitoring.example.com or https://monitoring.example.com/api/v3/. Getting this wrong will make every tool call fail with a "not found" error, since the server appends paths like /checks/ directly onto whatever you set here. If you leave HEALTHCHECKS_BASE_URL unset, it defaults to the real https://healthchecks.io/api/v3.

If your self-hosted instance isn't behind HTTPS, the server will print a warning (but still run) — your API key is sent as a request header on every call, so an http:// URL means that key travels in plaintext over the network to your instance.

What it can do

This server exposes 11 "tools" that your AI assistant can call. They fall into two groups:

Read tools — safe, look-up-only, never change anything:

ToolWhat it does
list_checksList every check in your account.
get_checkGet full details for one specific check.
list_check_pingsShow the recent ping history for a check (when it pinged in, success/fail/etc). Requires a read-write key — see note below.
list_check_flipsShow when a check's status changed (e.g. went from healthy to failing, or back).
list_integrationsList your configured notification integrations (Slack, email, etc). Requires a read-write key — see note below.
list_badgesGet the badge image URLs Healthchecks.io generates for each of your tags (useful for status pages/dashboards).

Mutating tools — these change things in your account, and all of them require a read-write API key:

ToolWhat it does
create_checkCreate 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.
update_checkChange an existing check's settings. Only the fields you specify are changed — anything you don't mention stays as it was.
pause_checkTemporarily stop monitoring a check, without deleting it. Requires explicit confirmation — see below.
resume_checkResume monitoring on a paused check.
delete_checkPermanently delete a check — this cannot be undone. Requires explicit confirmation — see below.

Technical reference

For each tool, this table gives its underlying Healthchecks.io API endpoint:

ToolRequires read-write key?Healthchecks.io API endpoint
list_checksNoGET /api/v3/checks/
get_checkNoGET /api/v3/checks/{uuid}
list_check_pingsYesGET /api/v3/checks/{uuid}/pings/
list_check_flipsNoGET /api/v3/checks/{uuid}/flips/
list_integrationsYesGET /api/v3/channels/
list_badgesNoGET /api/v3/badges/
create_checkYesPOST /api/v3/checks/
update_checkYesPOST /api/v3/checks/{uuid}
pause_checkYesPOST /api/v3/checks/{uuid}/pause
resume_checkYesPOST /api/v3/checks/{uuid}/resume
delete_checkYesDELETE /api/v3/checks/{uuid}

Source: README.md at commit 9a2d24f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v2.1.2LatestOct 9, 2026
  2. v2.1.1Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts