Full website health audit — SSL, DNS, DMARC/SPF/DKIM, performance, uptime, links
Full website health audit in one MCP tool call. Zero API keys required.
One call. Six checks. Scored report.
One-click install: Install on MCPize |
npx sitehealth-mcp
{
"mcpServers": {
"sitehealth": {
"command": "npx",
"args": ["-y", "sitehealth-mcp"]
}
}
}
Then ask your AI agent:
"Audit the health of example.com"
| Tool | Description |
|---|---|
audit_site | Full audit — all 6 checks, scored report |
check_ssl | SSL cert validity and expiry |
check_dns | DNS records and resolution |
check_email_auth | DMARC/SPF/DKIM validation |
check_performance | TTFB, load time, page weight |
check_uptime | HTTP ping + response time |
check_links | Broken link detection |
| Tool | Free | Pro ($19/mo) |
|---|---|---|
check_ssl | Yes | Yes |
check_dns | Yes | Yes |
audit_site | - | Yes |
check_email_auth | - | Yes |
check_performance | - | Yes |
check_uptime | - | Yes |
check_links | - | Yes |
Free tier gives you SSL and DNS checks. Pro unlocks the full 6-check audit with A-F scoring, email authentication, performance, uptime, and broken link detection.
Upgrade to Pro on MCPize — $19/mo or $190/yr.
{
"url": "https://example.com",
"overallScore": 82,
"overallGrade": "B",
"criticalIssues": [
"No DMARC record — required by Gmail/Yahoo/Microsoft for deliverability"
],
"warnings": [
"SSL certificate expires in 28 days — renew soon",
"2 broken links found out of 47 checked"
],
"recommendations": [
"Add a DMARC record: v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com",
"Enable gzip/brotli compression to reduce transfer size"
]
}
All checks use Node.js builtins (tls, dns/promises, fetch) — no external API keys, no costs, no rate limits.
audit_site("example.com")
├── SSL check (tls socket) → cert validity, expiry
├── DNS check (dns/promises) → record resolution
├── Email auth (DNS TXT lookups) → DMARC, SPF, DKIM
├── Performance (timed fetch) → TTFB, page weight
├── Uptime (HEAD request) → reachability
└── Broken links (page crawl) → link validation
↓
Weighted score (0-100) + grade (A-F) + recommendations
| Check | Weight |
|---|---|
| SSL | 20% |
| Performance | 20% |
| Uptime | 20% |
| Email Auth | 15% |
| Links | 15% |
| DNS | 10% |
One-click install with managed hosting: Install on MCPize
npx sitehealth-mcp
MIT — Built by Freedom Engineers
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y sitehealth-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-carsonroell-debug-sitehealth-mcp": {
"command": "npx",
"args": [
"-y",
"sitehealth-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencesitehealth-mcpnpmSiteHealth MCP works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.