Healthchecks MCP Server

Healthchecks is an MCP integration. Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed.

Packages and local setup

The published npm package is healthchecks-mcp, version 0.3.0. Its declared MCP transport is stdio.

The package declares HEALTHCHECKS_API_KEY (required): Project API key, exactly 32 characters, from Project Settings → API Access; HEALTHCHECKS_URL: Site root of a self-hosted instance, e.g. https://hc.example.net (default: https://healthchecks.io); HEALTHCHECKS_READ_ONLY: Set to true to register only the read tools (default: false); HEALTHCHECKS_ALLOW_TOOLS: Comma-separated tool names or list_ prefixes to register; 'essential' selects a curated preset (default: all tools); HEALTHCHECKS_DENY_TOOLS: Comma-separated tool names or list_ prefixes to remove from whatever the allow list left; HEALTHCHECKS_INSECURE_TLS: Set to true to accept a self-signed certificate from a self-hosted instance (default: false).

The published oci package is ghcr.io/ni-c/healthchecks-mcp:0.3.0. Its declared MCP transport is stdio.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.3.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.