SiteHealth MCP
NPM · SITEHEALTH-MCP
Full website health audit — SSL, DNS, DMARC/SPF/DKIM, performance, uptime, links
Available components
Last scanned (23 hours ago)
Scores higher than 66% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 574 tokens (~82/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 −1
- Stability: pass → 0.93 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/sitehealth-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_site Full Site Health Audit ~135
Run a comprehensive website health audit — SSL, DNS, DMARC/SPF/DKIM, page performance, uptime, and broken links. Returns a 0-100 health score with letter grade, critical issues, warnings, and actionable recommendations. All checks run in parallel for speed.
| Name | Type | Req | Description |
|---|---|---|---|
| checkLinks | boolean | – | Include broken link check (adds ~10-20s). Default: true |
| maxLinks | number | – | Max links to check for broken links. Default: 50 |
| url | string | yes | Website URL or domain to audit (e.g. 'https://example.com' or 'example.com') |
No output schema declared.
No examples provided.
check_dns DNS Health Check ~61
Resolve all DNS records (A, AAAA, MX, NS, CNAME, TXT, SOA) and check for IPv6 support, MX records, nameserver redundancy, and resolution time.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL or domain to check |
No output schema declared.
No examples provided.
check_email_auth Email Authentication Check ~63
Validate DMARC, SPF, and DKIM records for a domain. Checks for common misconfigurations, missing records, and provides fix recommendations. DMARC is now mandatory for Gmail/Yahoo/Microsoft.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL or domain to check |
No output schema declared.
No examples provided.
check_links Broken Link Check ~71
Extract links from a page and check each for broken responses (4xx/5xx). Returns broken links with status codes and the page they were found on.
| Name | Type | Req | Description |
|---|---|---|---|
| maxLinks | number | – | Maximum links to check. Default: 50 |
| url | string | yes | Website URL to check for broken links |
No output schema declared.
No examples provided.
check_performance Page Performance Check ~49
Measure TTFB, total load time, page weight, redirect chain, compression, and cache headers. Returns performance grade with specific optimization recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL to check |
No output schema declared.
No examples provided.
check_ssl SSL Certificate Check ~56
Check SSL/TLS certificate validity, expiry date, issuer, protocol version, and SANs. Returns a grade (A-F) based on days until expiry and cert validity.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL or domain to check |
No output schema declared.
No examples provided.
check_uptime Uptime Check ~34
HTTP ping to check if a site is reachable and measure response time.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL to ping |
No output schema declared.
No examples provided.
How do I install the SiteHealth MCP server?
SiteHealth MCP runs locally as an npm package, launched with npx -y sitehealth-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sitehealth-mcp
claude mcp add carsonroell-debug-sitehealth-mcp -- npx -y sitehealth-mcp
What is the SiteHealth MCP server?
SiteHealth MCP is listed in the public MCP registry as io.github.carsonroell-debug/sitehealth-mcp. Full website health audit, SSL, DNS, DMARC/SPF/DKIM, performance, uptime, links. This page covers its npm package (sitehealth-mcp).
Is the SiteHealth MCP server safe to use?
SiteHealth MCP scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SiteHealth MCP server expose?
SiteHealth MCP exposes 7 tools: audit_site, check_ssl, check_dns, check_email_auth, check_performance, and 2 more. Their descriptions and schemas cost roughly 469 tokens of context every time the server is loaded.
Is the SiteHealth MCP server still maintained?
SiteHealth MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the SiteHealth MCP server under?
SiteHealth MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.