Healthchecksio MCP vs UptimeRobot
A side-by-side look at the Healthchecksio MCP and UptimeRobot MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Healthchecksio MCP for monitoring work as a local process; choose UptimeRobot for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Healthchecksio MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HEALTHCHECKS_API_KEY, HEALTHCHECKS_API_URL, HEALTHCHECKS_PING_URL. - You want tools like
list_checks, get_check, create_check.
Choose UptimeRobot when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 51/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | HEALTHCHECKS_API_KEYHEALTHCHECKS_API_URLHEALTHCHECKS_PING_URL |
Tools & capabilities
Healthchecksio MCP tools 8
list_checkslist checks, filter by tag/statusget_checkget a single check's detailscreate_checkcreate a new checkupdate_checkupdate a checklist_check_flipsup/down status historylist_channelsnotification channelslist_badgesbadge URLspingsend a heartbeat ping (success/fail/start/log)
UptimeRobot 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.
Healthchecksio MCP
{
"mcpServers": {
"healthchecksio-mcp": {
"command": "npx",
"args": [
"-y",
"github:nguyenhuy158/healthchecksio-mcp"
],
"env": {
"HEALTHCHECKS_API_KEY": "YOUR_HEALTHCHECKS_API_KEY_HERE",
"HEALTHCHECKS_API_URL": "YOUR_HEALTHCHECKS_API_URL_HERE",
"HEALTHCHECKS_PING_URL": "YOUR_HEALTHCHECKS_PING_URL_HERE"
}
}
}
}
UptimeRobot
{
"mcpServers": {
"uptimerobot": {
"url": "https://mcp.uptimerobot.com/mcp"
}
}
}
Frequently asked questions
Healthchecksio MCP is categorized under Monitoring and uses a local stdio subprocess. UptimeRobot belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Healthchecksio MCP for monitoring work and UptimeRobot 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.
Healthchecksio MCP has no declared pricing — check the project's own site. UptimeRobot has no declared pricing — check the project's own site. 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 healthchecksio-mcp and uptimerobot as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Healthchecksio MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. UptimeRobot has 37/100 (Fair) with 0 views, 0 installs and 24 GitHub stars.
