Upkeep MCP vs Siteaudit MCP
A side-by-side look at the Upkeep MCP and Siteaudit MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Upkeep MCP for monitoring work as a local process; choose Siteaudit 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 Upkeep MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
Choose Siteaudit MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
full_audit, seo_audit, security_audit.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 41/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
Upkeep MCP tools
No tool names declared yet. Check the project README from the listing page.
Siteaudit MCP tools 11
full_auditRun a comprehensive audit on a URL — SEO, performance, and security in one call. Returns a unified score (0-100) plus detailed results for each category. This is the most complete analysis available.seo_auditRun an SEO-focused audit on a URL. Checks title tags, meta descriptions, headings, images alt text, internal/external links, canonical URLs, Open Graph, structured data, mobile viewport, and content length. Returns score + actionable recommendations.security_auditRun a security audit on a URL. Checks HTTPS, HSTS, CSP, X-Frame-Options, cookie flags, SSL certificate validity and expiration, server disclosure, and other security headers. Returns score + fixes needed.performance_auditCheck page performance — response time, page size, compression, caching. Returns server response time, page size, compression status, redirect chain analysis, and caching header review.compare_sitesCompare SEO and performance scores of multiple websites side by side. Useful for competitive analysis — see how your site stacks up against competitors across SEO, performance, and security.lighthouse_auditRun Google Lighthouse via PageSpeed Insights API — get performance, accessibility, SEO, and best-practices scores plus Core Web Vitals (LCP, INP, CLS). Returns Lighthouse scores (0-100), Core Web Vitals with ratings, and the top 5 performance optimization opportunities ranked by potential time savings. This uses Google's real Lighthouse engine — the same tool Chrome DevTools uses. Takes 15-30 seconds to complete.check_linksScan a page for broken links — find 404s, redirects, timeouts, and server errors. Extracts all links (internal + external) from the page, checks each with a HEAD request, and groups results by status: working (2xx), redirects (3xx), client errors (4xx), server errors (5xx), and timeouts. Checks up to 50 links concurrently for speed. Results cached for 5 minutes.
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.
Upkeep MCP
{
"mcpServers": {
"upkeep-mcp": {
"command": "npx",
"args": [
"-y",
"upkeep-mcp"
]
}
}
}
Siteaudit MCP
{
"mcpServers": {
"vdalhambra-siteaudit-mcp": {
"command": "uvx",
"args": [
"--from",
"siteaudit-mcp",
"siteaudit"
]
}
}
}
Frequently asked questions
Upkeep MCP is categorized under Monitoring and uses a local stdio subprocess. Siteaudit MCP belongs to Monitoring and uses a local stdio subprocess. Pick Upkeep MCP for monitoring work and Siteaudit 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.
Upkeep MCP has no declared pricing — check the project's own site. Siteaudit MCP is listed as free. Auth: no auth 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 upkeep-mcp and vdalhambra-siteaudit-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Upkeep MCP has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Siteaudit MCP has 56/100 (Good) with 1 views, 0 installs and 5 GitHub stars.
