Mcpuptimeledger MCP vs SiteHealth MCP
A side-by-side look at the Mcpuptimeledger MCP and SiteHealth MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mcpuptimeledger MCP for monitoring work over a hosted endpoint; choose SiteHealth MCP 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 Mcpuptimeledger MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_mcp_server_uptime, validate_tool_schema, detect_auth_failure.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 45/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| 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 | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 7 |
| Full listing | View Mcpuptimeledger MCP | View SiteHealth MCP |
Tools & capabilities
Mcpuptimeledger MCP tools 5
check_mcp_server_uptimevalidate_tool_schemadetect_auth_failureissue_sla_receiptexport_status_report
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
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.
Mcpuptimeledger MCP
{
"mcpServers": {
"mcpuptimeledger-mcp": {
"url": "https://mcpuptimeledger.clauxel.com/mcp"
}
}
}
SiteHealth MCP
{
"mcpServers": {
"sitehealth-mcp": {
"command": "npx",
"args": [
"-y",
"sitehealth-mcp"
]
}
}
}
Frequently asked questions
Mcpuptimeledger MCP is categorized under Monitoring and uses a remote HTTP/SSE transport. SiteHealth MCP belongs to Monitoring and uses a local stdio subprocess. Pick Mcpuptimeledger MCP for monitoring work and SiteHealth MCP 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.
Mcpuptimeledger MCP has no declared pricing — check the project's own site. SiteHealth MCP 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 mcpuptimeledger-mcp and sitehealth-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mcpuptimeledger MCP has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. SiteHealth MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.