SiteLint Auditor MCP
OfficialRelated Servers
Alternatives to SiteLint Auditor MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to audit URLs or raw HTML for SEO, AEO, and GEO performance, generate llms.txt manifests, and check the tool version via MCP tools.1MIT
- AlicenseAqualityBmaintenanceEnables running comprehensive website audits from any MCP client, returning actionable plain-language reports covering SEO, accessibility, performance, security, and more.650 npmMIT
- AlicenseNot gradedqualityAmaintenanceExposes website auditing, finding retrieval, and safe fix application as MCP tools so AI agents can diagnose and remediate SEO, accessibility, and technical web issues.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to perform comprehensive SEO audits on web pages, including meta tags, headings, links, images, performance, and more, via a CLI or MCP server.181MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with web accessibility analysis tools via MCP, enabling checks for alt text, heading hierarchy, color contrast, ARIA validation, and form accessibility.40 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to perform real accessibility audits by controlling a browser, running axe-core scans, reviewing page structure, images, tab order, and WCAG 2.2 color contrast, all over MCP with local session logging.21Apache 2.0
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.