io.github.ronniechong/healthchecks-io-mcp MCP Server
io.github.ronniechong/healthchecks-io-mcp
What this kind of tool is for
- Chain multi-step workflows across the other tools in this directory.
- Run a scheduled or triggered job instead of retyping the same request.
- Have your agent watch a feed, queue, or repo and act on new items.
How to compare servers like this
- Trigger model:
- Understand what starts the automation — a command, a schedule, or an event — before relying on it.
- Blast radius:
- Prefer tools that hand you a review point before an irreversible action runs.
- Chaining cost:
- Each chained step adds a failure point; keep critical paths on the fewest tools.
- Maintenance signal:
- Automations break quietly; a maintained tool is the difference between repair and rediscovery.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.ronniechong/healthchecks-io-mcp MCP server?
Unofficial MCP server for managing Healthchecks.io checks via the Management API
How to install io.github.ronniechong/healthchecks-io-mcp
Copy-paste configuration for popular MCP clients.
HEALTHCHECKS_API_KEYrequiredsecretHealthchecks.io API key (read-only or read-write, from Settings → API Access)
{
"mcpServers": {
"healthchecks-io-mcp": {
"command": "npx",
"args": [
"-y",
"@digitalronin/healthchecks-io-mcp"
],
"env": {
"HEALTHCHECKS_API_KEY": "<YOUR_HEALTHCHECKS_API_KEY>"
}
}
}
}Related MCP servers
MCP server for letmepost.dev. Publish across 8 social platforms from any agent.

MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
RunAPI MCP server for Flux Kontext: create tasks, poll status, check pricing.
RunAPI MCP server for Flux: create tasks, poll status, check pricing.
Multi-tenant MCP gateway for AI commerce. One connection, every store.
View repository →Multi-tenant MCP gateway for AI commerce. One connection, every store.
View repository →

