SiteHealth MCP vs Monitor
A side-by-side look at the SiteHealth MCP 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 SiteHealth MCP 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 SiteHealth MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You want tools like
audit_site, check_ssl, check_dns.
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 | 53/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,309 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View SiteHealth MCP | View Monitor |
Tools & capabilities
SiteHealth MCP tools 7
audit_siteFull audit — all 6 checks, scored reportcheck_sslSSL cert validity and expirycheck_dnsDNS records and resolutioncheck_email_authDMARC/SPF/DKIM validationcheck_performanceTTFB, load time, page weightcheck_uptimeHTTP ping + response timecheck_linksBroken link detection
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.
SiteHealth MCP
{
"mcpServers": {
"sitehealth-mcp": {
"command": "npx",
"args": [
"-y",
"sitehealth-mcp"
]
}
}
}
Monitor
{
"mcpServers": {
"betterdb-inc-monitor": {
"command": "npx",
"args": [
"-y",
"@betterdb/monitor"
]
}
}
}
Frequently asked questions
SiteHealth MCP is categorized under Monitoring and uses a local stdio subprocess. Monitor belongs to Monitoring and uses a local stdio subprocess. Pick SiteHealth MCP 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.
SiteHealth MCP 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 sitehealth-mcp and betterdb-inc-monitor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SiteHealth MCP has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Monitor has 64/100 (Good) with 5 views, 0 installs and 1,309 GitHub stars.