SiteLint Auditor MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUDITOR_PORT | No | Port for SSE transport. | 3100 |
| AUDITOR_TIMEOUT | No | Navigation/render timeout (ms). | 30000 |
| AUDITOR_HEADLESS | No | Set false to see browser. | true |
| AUDITOR_TRANSPORT | No | stdio or sse. | stdio |
| AUDITOR_CONCURRENCY | No | Max concurrent audit pages (hard cap). | 3 |
| AUDITOR_BROWSER_PATH | No | Custom Chromium/Chrome path. Defaults to Puppeteer default. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_urlA | Run a SiteLint audit on a live URL. Checks WCAG accessibility, SEO, performance, and security. Optionally filter by standard, audit type, WCAG level, version, or specific success criteria. |
| audit_htmlA | Audit raw HTML snippet against WCAG/SEO standards. Creates a sandbox page to analyze the markup. |
| check_wcag_criterionA | Check a single WCAG success criterion against a page. Filters audit to one criterion, level, and WCAG standard — faster than full audit. Returns pass/fail per element. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| auditor-standards | Supported WCAG standards and criteria |
TDQS
Scored across 3 tools
audit_url and audit_html are clearly distinct by input type, but check_wcag_criterion overlaps with audit_url when filtering to a single criterion. The descriptions help differentiate them by emphasizing speed and a single-criterion focus, but minor ambiguity remains.
Tool names follow a verb_noun pattern (audit_url, audit_html, check_wcag_criterion). The switch from 'audit' to 'check' is a slight inconsistency but still logical, as checking a single criterion differs from running a full audit.
With only 3 tools, the set is tightly scoped for a specialized auditor server. Each tool serves a distinct, necessary function—URL auditing, HTML snippet auditing, and focused WCAG criterion checks—without unnecessary bloat.
The core auditing workflows are covered: auditing a live URL, auditing raw HTML, and checking a specific WCAG criterion. Minor gaps exist, such as no tool for retrieving historical audits or comparing results, but these do not block primary usage.