Website Audit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBSITE_AUDIT_ALLOW_PRIVATE | No | Setting WEBSITE_AUDIT_ALLOW_PRIVATE=1 disables the private-host check. It exists for the test suite and should not be set otherwise. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_websiteB | Fetch one http/https URL and score it 0-100 for performance, SEO, design, functionality and technology, with findings. |
| compare_websitesA | Audit 2 to 10 URLs and return them ranked by overall score, best first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools differ by cardinality: audit_website targets a single URL, compare_websites targets 2-10 URLs and returns a ranking. The boundary is mostly clear, though compare_websites is essentially a batch wrapper and an agent could plausibly reach for it when auditing one site plus a competitor.
Both names follow the same verb_noun snake_case pattern (audit_website, compare_websites). The verb directly signals the action and the noun the resource, so the convention is fully predictable.
Two tools is thin for a server claiming five audit dimensions (performance, SEO, design, functionality, technology). The surface is cohesive and each tool earns its place, but there is no tooling for targeted checks, configuration, or report retrieval, putting it at the borderline.
Single-site auditing and multi-site ranking are covered, so the core workflow has no dead ends. However, there is no way to request a specific dimension, retrieve or export a report, or re-examine prior results, which are notable gaps for an audit product.