Healthchecks vs Monitor
A side-by-side look at the Healthchecks and Monitor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Healthchecks for monitoring work as a local process; choose Monitor for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Healthchecks when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_checks, get_check, list_flips.
Choose Monitor when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 55/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1,310 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Healthchecks | View Monitor |
Tools & capabilities
Healthchecks tools 10
list_checksChecks in the project, with `tag`, `slug` and `status` filtersget_checkOne check with every field, by UUID or `unique_keylist_flipsUp/down transitions of a check, with a time windowlist_badgesStatus badge URLs, per tag and for the projectget_statusWhether the instance is reachable — needs no API key at allget_api_key_infoWhich instance, which kind of key, and what that key cannot docreate_checkCreates a check. Notifies every integration unless `channels` says otherwiseupdate_checkChanges the given fields. `channels` replaces the list rather than adding to it; an empty list is refusedpause_checkStops the check expecting pings — and alerting. `resume_check` puts it backresume_checkPuts a paused check back into the `new` state
Monitor tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Healthchecks
{
"mcpServers": {
"healthchecks": {
"command": "npx",
"args": [
"-y",
"healthchecks-mcp"
]
}
}
}
Monitor
{
"mcpServers": {
"betterdb-inc-monitor": {
"command": "npx",
"args": [
"-y",
"@betterdb/monitor"
]
}
}
}
Frequently asked questions
Healthchecks is categorized under Monitoring and uses a local stdio subprocess. Monitor belongs to Monitoring and uses a local stdio subprocess. Pick Healthchecks for monitoring work and Monitor for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Healthchecks has no declared pricing — check the project's own site. Monitor is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add healthchecks and betterdb-inc-monitor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Healthchecks has a quality signal of 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Monitor has 64/100 (Good) with 5 views, 0 installs and 1,310 GitHub stars.