Healthchecksio Mcp

io.github.nguyenhuy158Published by GitHub account nguyenhuy158v1.0.0Updated Nov 3, 2026

MCP server for Healthchecks.io API

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

MCP server for the Healthchecks.io API that lets an assistant list, create, update, pause, resume and delete checks, inspect channels and badges, and send…

What you can do
  • List and inspect checks, filtering by tag or status, and view a check's details and up/down flip history
  • Create, update, pause, resume and delete checks
  • List notification channels and badge URLs
  • Send heartbeat pings with success, fail, start or log signals
When to use it
Useful when you manage cron jobs, scheduled tasks or background services on Healthchecks.io and want an assistant to inspect check status, adjust monitoring configuration, or send pings without leaving the chat.
Requirements
Runs locally over stdio, typically via npx or pnpm dlx from the npm package or GitHub repository. Requires a Healthchecks.io API key in the HEALTHCHECKS_API_KEY environment variable. Optional HEALTHCHECKS_API_URL and HEALTHCHECKS_PING_URL variables point at self-hosted instances; network access to Healthchecks.io is needed.
Before you install
The API key grants access to your Healthchecks.io account and is passed in plain environment configuration. Several tools change state: create, update, pause, resume and delete checks, and pings affect monitoring status and can trigger or suppress alerts. Deleting a check is destructive. Check data and pings are sent to Healthchecks.io or your configured self-hosted endpoint.

Installation

In SourceWeft

  1. Open Healthchecksio 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

healthchecksio-mcp

🇬🇧 English · 🇻🇳 Tiếng Việt

MCP server for the Healthchecks.io API. Lets Claude manage checks, channels, badges, and send pings.

Install (dev)

bash
pnpm installpnpm run build

(npm also works: npm install && npm run build)

Env config

  • HEALTHCHECKS_API_KEY (required) — API key from Settings > API Access on healthchecks.io.
  • HEALTHCHECKS_API_URL (optional) — defaults to https://healthchecks.io/api/v3. Change if self-hosting.
  • HEALTHCHECKS_PING_URL (optional) — defaults to https://hc-ping.com. Change if self-hosting.

Register with Claude Code

Install straight from GitHub, no clone needed (pnpm preferred):

bash
claude mcp add healthchecksio -e HEALTHCHECKS_API_KEY=your-key -- pnpm dlx github:nguyenhuy158/healthchecksio-mcp

npm also works:

bash
claude mcp add healthchecksio -e HEALTHCHECKS_API_KEY=your-key -- npx -y github:nguyenhuy158/healthchecksio-mcp

Or run from a local build, adding to .mcp.json / claude_desktop_config.json:

json
{  "mcpServers": {    "healthchecksio": {      "command": "node",      "args": ["/path/to/healthchecksio-mcp/build/index.js"],      "env": {        "HEALTHCHECKS_API_KEY": "your-key"      }    }  }}

Tools

  • list_checks — list checks, filter by tag/status
  • get_check — get a single check's details
  • create_check — create a new check
  • update_check — update a check
  • pause_check / resume_check
  • delete_check
  • list_check_flips — up/down status history
  • list_channels — notification channels
  • list_badges — badge URLs
  • ping — send a heartbeat ping (success/fail/start/log)

Source: README.md at commit d7f41f5

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

40% 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

    Declare a license in the repository or the registry entry.