Healthchecksio MCP vs Netdata#Netdata
A side-by-side look at the Healthchecksio MCP and Netdata#Netdata 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 Netdata#Netdata for monitoring. 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 Netdata#Netdata when
- You need dedicated capabilities in the Monitoring domain.
- 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 | 52/100 · Good | 52/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | HEALTHCHECKS_API_KEYHEALTHCHECKS_API_URLHEALTHCHECKS_PING_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 81,108 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Healthchecksio MCP | View Netdata#Netdata |
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)
Netdata#Netdata 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"
}
}
}
}
Netdata#Netdata
No confirmed install command for Netdata#Netdata yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Healthchecksio MCP is categorized under Monitoring and uses a local stdio subprocess. Netdata#Netdata belongs to Monitoring and uses an install path we have not confirmed yet. Pick Healthchecksio MCP for monitoring work and Netdata#Netdata 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. Netdata#Netdata has no confirmed install command yet — follow its own setup instructions.
Healthchecksio MCP has no declared pricing — check the project's own site. Netdata#Netdata is listed as free. 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 healthchecksio-mcp and netdata-netdata-netdata 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 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Netdata#Netdata has 52/100 (Good) with 3 views, 0 installs and 81,108 GitHub stars.