Accessibility Testing MCP
Related Servers
Alternatives to Accessibility Testing MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables automated web accessibility scanning and browser automation, allowing WCAG compliance checks, page interaction, persistent browser sessions, and detailed accessibility reports with visual annotations.2,492 npmMIT
- AlicenseBqualityCmaintenanceEnables WCAG accessibility inspection of websites, with tools to check, analyze, and report on compliance issues.45 npmISC
- AlicenseBqualityAmaintenanceEnables automated web accessibility scans for WCAG compliance using Playwright and Axe-core, providing visual and JSON reports with remediation guidance.252,492 npm57MIT
- AlicenseNot gradedqualityCmaintenanceEnables accessibility testing using Playwright and Axe, allowing users to scan URLs, HTML content, and batches for violations, and summarize results.14 npm1MIT

axe MCP Serverofficial
FlicenseNot gradedqualityCmaintenanceEnables AI agents to scan web pages for accessibility issues and get AI-powered remediation guidance using Axe DevTools for Web.8-- FlicenseBqualityDmaintenanceEnables AI agents to perform comprehensive accessibility audits on websites using Playwright and axe-core against WCAG standards. Provides detailed compliance reports with violation summaries and remediation guidance across multiple browsers.3-
TDQS
Scored across 5 tools
The tools are clearly separated by input type (URL vs HTML) and output format (detailed report vs raw JSON). The _json suffix disambiguates the output format, but analyze_url and analyze_url_json are conceptually similar, which could cause minor selection confusion.
All tool names follow a consistent verb_noun pattern with snake_case. The analyze_* prefix is used for testing actions, and get_rules follows the same convention, making the naming predictable and uniform.
With 5 tools, the set is well-scoped for the server's purpose of accessibility testing. Each tool serves a distinct input/output combination without unnecessary bloat, and the count is within the ideal range.
The server covers the core workflows of accessibility testing: analyzing URLs and HTML, with both human-readable and JSON output, plus rule discovery. Minor gaps exist, such as lack of customizable WCAG versions or screen sizes, but the essential surface is complete.