A side-by-side look at the Health Check AI MCP and Upcheck MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Health Check AI MCP for monitoring work as a local process; choose Upcheck 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 Health Check AI MCP when
You need dedicated capabilities in the Monitoring domain.
No tool names declared yet. Check the project README from the listing page.
Upcheck 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.
Health Check AI MCP is categorized under Monitoring and uses a local stdio subprocess. Upcheck belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Health Check AI MCP for monitoring work and Upcheck 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.
Health Check AI MCP has no declared pricing — check the project's own site. Upcheck 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 health-check-ai-mcp and upcheck as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Health Check AI MCP has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Upcheck has 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.