Log inSubmit server
Healthchecksio MCP logo

Healthchecksio MCP

Manage Healthchecks.io checks, notification resources, status history, badges, and heartbeat pings through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Healthchecksio MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "healthchecksio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "github:nguyenhuy158/healthchecksio-mcp"
      ],
      "env": {
        "HEALTHCHECKS_API_KEY": "YOUR_VALUE_HERE",
        "HEALTHCHECKS_API_URL": "YOUR_VALUE_HERE",
        "HEALTHCHECKS_PING_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The healthchecksio-mcp MCP server connects MCP clients to the Healthchecks.io API and heartbeat ping endpoint. It exposes tools for managing checks, reviewing status flips, listing notification channels and badge URLs, and sending success, failure, start, or log pings. Use it when an agent needs to inspect or change Healthchecks.io monitoring resources, including deployments using a self-hosted instance.

Use cases

  • List checks filtered by tag or status
  • Create and update Healthchecks.io checks
  • Review up/down status history
  • Send heartbeat pings from an agent
  • Inspect notification channels and badge URLs

Key features

  • Check listing with tag and status filters
  • Check creation, updates, pausing, resuming, and deletion
  • Up/down status history retrieval
  • Notification channel and badge URL listing
  • Success, failure, start, and log heartbeat pings

Tools8

What Healthchecksio MCP lets your agent do. Expand a tool for its parameters.

Self-reported~70 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · github:nguyenhuy158/healthchecksio-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads165Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Tools exposed8Callable tools this server registers over MCP.

How Healthchecksio MCP works

What healthchecksio-mcp MCP server does

The healthchecksio-mcp MCP server gives an MCP-compatible client access to Healthchecks.io monitoring resources. It can retrieve the checks in an account, inspect an individual check, create new checks, and modify existing ones. Check lifecycle operations also include pausing, resuming, and deleting checks.

The server covers related read operations as well. Agents can request up/down history for a check, list configured notification channels, and retrieve badge URLs. A separate ping tool sends heartbeat events using success, failure, start, or log modes.

How it works

The server uses a Healthchecks.io API key for authenticated API operations. Its default API base is https://healthchecks.io/api/v3, while heartbeat requests use https://hc-ping.com by default. Both endpoints can be replaced for a self-hosted Healthchecks.io deployment.

MCP clients invoke the exposed tools, and the server forwards the corresponding operations to Healthchecks.io. The check-listing operation supports filtering by tag and status. Status-history results come from the check-flips operation, which reports changes between up and down states.

Setup and configuration

Install dependencies and build the project with pnpm:

bash
pnpm install
pnpm run build

npm can be used instead with npm install && npm run build. Set HEALTHCHECKS_API_KEY to the API key created under Settings > API Access in Healthchecks.io. HEALTHCHECKS_API_URL optionally changes the API base URL, and HEALTHCHECKS_PING_URL optionally changes the heartbeat destination.

For Claude Code, the repository documents direct installation from GitHub with pnpm dlx or npx. A locally built server can also be registered by running node against build/index.js and passing the API key through the MCP server environment configuration. The same environment-based configuration is shown for Claude Desktop.

Tools and capabilities

Available operations include:

  • list_checks: list checks, with tag and status filters.
  • get_check: retrieve one check's details.
  • create_check: create a check.
  • update_check: change a check.
  • pause_check and resume_check: change check activity state.
  • delete_check: remove a check.
  • list_check_flips: inspect up/down status history.
  • list_channels: list notification channels.
  • list_badges: list badge URLs.
  • ping: send a success, failure, start, or log heartbeat.

Limitations and notes

The healthchecksio-mcp MCP server requires a Healthchecks.io API key. API and ping URLs default to the public Healthchecks.io services and must be changed explicitly when using self-hosted endpoints.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Healthchecksio MCP

healthchecksio-mcp is an MCP server that connects AI clients to the Healthchecks.io API and ping endpoint. It provides tools to list, get, create, update, pause, resume, and delete checks, inspect flips, channels, and badges, plus send heartbeat pings for success, fail, start, or log events.

Install it with pnpm or npm, then build it with the project’s build command. Use `pnpm install && pnpm run build`, or `npm install && npm run build`.

It requires `HEALTHCHECKS_API_KEY`, which should contain an API key from Healthchecks.io Settings > API Access. `HEALTHCHECKS_API_URL` and `HEALTHCHECKS_PING_URL` are optional overrides for the API and heartbeat endpoints.

Claude Code can register the server from GitHub or a local build, while Claude Desktop can use a local Node.js entry point and an environment-configured API key.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHealthchecksio MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/healthchecksio-mcp?style=directory)](https://allmcps.com/mcp/healthchecksio-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/healthchecksio-mcp"><img src="https://allmcps.com/api/badge/healthchecksio-mcp?style=directory" alt="Healthchecksio MCP on AllMCPs" /></a>