Skip to main content
Glama
Sign In
healthchecksio-mcp

healthchecksio-mcp

by nguyenhuy158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

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)

pnpm install
pnpm run build

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

Related MCP server: uptrack-mcp

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):

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

npm also works:

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:

{
  "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)

Available Tools

11 tools
create_checkCreate checkC

Create a new check.

Inputs: tz, desc, name, tags, +5 more.

delete_checkDelete checkB

Permanently delete a check.

Inputs: uuid (required).

get_checkGet checkA

Get details of a single check by its UUID.

Inputs: uuid (required).

list_badgesList badgesA

List status badge URLs for the project, per tag.

Inputs: no named parameters.

list_channelsList notification channelsA

List all notification channels (email, Slack, webhook, etc.) in the project.

Inputs: no named parameters.

list_check_flipsList check status flipsA

List status change history (up/down flips) for a check.

Inputs: uuid (required), seconds.

list_checksList checksA

List all checks in the project. Optionally filter by tag or status.

Inputs: tags, status.

pause_checkPause checkB

Pause monitoring for a check.

Inputs: uuid (required).

pingSend pingA

Send a ping (heartbeat) signal for a check. Use this to report success, failure, or manually test a check.

Inputs: uuid (required), state, message, exitStatus.

resume_checkResume checkA

Resume monitoring for a paused check (cron/schedule based checks only).

Inputs: uuid (required).

update_checkUpdate checkC

Update an existing check's configuration.

Inputs: uuid (required), tz, desc, name, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a specific resource and action: checks (CRUD, pause/resume, flips), channels, badges, and ping. No two tools have overlapping purposes, and actions like pause vs. resume are clearly distinct.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (list_checks, get_check, create_check, update_check, delete_check, pause_check, resume_check). The single exception 'ping' is a standard verb for heartbeats and fits the pattern.

    Tool Count5/5

    11 tools is well-scoped for a health checks server. The set covers the primary resource (checks) with full lifecycle actions, plus supporting resources (channels, badges) and the ping action. No unnecessary bloat or thinness.

    Completeness5/5

    The check lifecycle is complete: create, read, update, delete, list, pause, resume. Additional operations like listing flips, channels, badges, and sending pings cover the core functionality of healthchecks.io with no obvious gaps.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers