Skip to content

healthchecks-mcpCron monitoring, in the conversation

MCP server for Healthchecks — inspect, create and adjust cron and uptime checks, and read why one failed

How healthchecks-mcp connects an MCP client to HealthchecksAn MCP client talks to healthchecks-mcp over stdio. The server calls the Healthchecks Management API v3 over HTTPS. The monitored jobs ping Healthchecks directly, on a path the server is not on.MCP clientClaude, Codex, …healthchecks-mcp14 tools, 7 essentialconfirm tokensHealthcheckscron and uptimestdioHTTPS/api/v3Your jobscron, timers, backupsping
The server only reads and writes checks. The pings that keep them green come from the jobs themselves, on a path this server is deliberately not on.

Fourteen tools, or seven

The tool list is not fixed. HEALTHCHECKS_ALLOW_TOOLS=essential narrows it to the seven that cover the job end to end, and a name that matches nothing stops the server instead of quietly leaving a tool out of tools/list.

Listing the tools, narrowing them to the essential preset, and the startup abort a mistyped tool name produces

Recorded from docs/demo.tape with no credentials at all — the server starts without an API key so that registries and inspectors can introspect it.

Released under the MIT License.