Health Check AI MCP vs SiteVitals
A side-by-side look at the Health Check AI MCP and SiteVitals 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 SiteVitals 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.
- You prefer a local stdio subprocess transport.
Choose SiteVitals when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_sites, get_site_health, get_site_uptime.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 39/100 · Fair | 45/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 | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Health Check AI MCP | View SiteVitals |
Tools & capabilities
Health Check AI MCP tools
No tool names declared yet. Check the project README from the listing page.
SiteVitals tools 5
list_sitesList all monitored sites with current health scoresget_site_healthDetailed scores and trends for a specific siteget_site_uptimeUptime history and downtime incidents (up to 90 days)get_latest_checksLatest SEO, security and page speed check resultsget_ssl_domain_statusSSL certificate and domain expiry status
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
{
"mcpServers": {
"health-check-ai-mcp": {
"command": "npx",
"args": [
"-y",
"meok-setup"
]
}
}
}
SiteVitals
{
"mcpServers": {
"sitevitals": {
"url": "https://www.sitevitals.co.uk/api/mcp"
}
}
}
Frequently asked questions
Health Check AI MCP is categorized under Monitoring and uses a local stdio subprocess. SiteVitals belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Health Check AI MCP for monitoring work and SiteVitals 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. SiteVitals 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 sitevitals 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. SiteVitals has 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.