SiteHealth MCP
Run one agent-driven audit covering SSL, DNS, email auth records, performance, uptime, and links before or after you go live.
Overview
SiteHealth MCP is a MCP server for the Ship phase that audits SSL, DNS, DMARC/SPF/DKIM, performance, uptime, and links in one agent session.
What is this MCP server?
- Single MCP workflow for SSL, DNS, and mail authentication (DMARC, SPF, DKIM)
- Performance and uptime signals alongside link checks
- npm stdio package sitehealth-mcp v0.1.1 with no mandatory API key in manifest
- Suited to pre-launch checklists and post-deploy regression passes
- Complements link-only tools with full-site health context
- Server version 0.1.1; npm identifier sitehealth-mcp
- Audit scope spans 6 areas: SSL, DNS, DMARC/SPF/DKIM, performance, uptime, links
- stdio transport with no required secrets in server manifest
What problem does it solve?
Pre-launch checks are scattered across TLS, DNS, email auth, speed, and link tools, so small teams skip steps and ship domains that fail mail or search basics.
Who is it for?
Solo founders running a launch checklist on a new or migrated site who want one MCP audit instead of five manual dashboards.
Skip if: Deep penetration testing, compliance attestations, or affiliate-specific link revenue modeling.
What do I get? / Deliverables
After adding the npm MCP server, your agent returns a consolidated health picture you can fix before customers hit errors or inboxes reject your mail.
- Consolidated SSL and DNS findings
- DMARC, SPF, and DKIM status summary
- Performance, uptime, and link health overview
Recommended MCP Servers
Journey fit
How it compares
Broad site health audit MCP, not an MCP transport proxy or specialized affiliate link scanner.
Common Questions / FAQ
Who is sitehealth-mcp for?
It is for indie builders and tiny teams who need SSL, DNS, email authentication, performance, uptime, and link status from their coding agent.
When should I use sitehealth-mcp?
Use it before go-live, after DNS or hosting changes, or when email deliverability and HTTPS suddenly look wrong.
How do I add sitehealth-mcp to my agent?
Install the npm package sitehealth-mcp, add the stdio MCP server block in Claude Code, Cursor, or another client, and invoke audit tools against your target domain.