website-audit

Website audit

Runs a real audit of a public web page and turns the result into something the owner of that site can act on. It is not an opinion about the design: every finding comes from something measured on the page.

What it needs

This skill drives the website-audit MCP server, which exposes one tool:

audit_website(url, type?)

• url — the address to audit, such as example.com or https://example.com
• type — optional, one of local, ecommerce, portfolio, saas. It changes what counts as a problem: a missing phone number is serious for a local business and irrelevant for a portfolio. Leave it out and the type is worked out from the page itself.

If the tool is not available, the server is not installed. Tell the user to run:

claude mcp add website-audit -- npx -y github:rolledoatmeals/website-audit-mcp

Any MCP-speaking client works; the equivalent config is command: npx, args: ["-y", "github:rolledoatmeals/website-audit-mcp"]. Node 18+ required.

What it does on the network: it resolves the address, fetches that public page the way a phone browser would (following redirects), and makes one plain http:// HEAD request to the same host to check whether it redirects to the secure version. Those requests go to the audited host and nowhere else. It signs in to nothing, sends no data to any third party, and stores nothing. Addresses that resolve to private or internal ranges are refused.

How to run it

1. Take the address from the user. If they gave a bare domain, pass it as-is.
2. Call audit_website. Pass type only when the user has told you what kind of site it is, or when the auto-detected type in the result is clearly wrong and they want it re-scored.
3. Read the result before summarising it. It returns a 0–100 score, a headline, a page-weight and response-time reading, and findings grouped into six categories: Speed, Phone experience, Getting found, Getting in touch, How the writing reads, How current it looks.