@webability/mcp
Related Servers
Alternatives to @webability/mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceAn accessibility expert MCP server that provides AI coding assistants with real-time access to WAI-ARIA patterns, code review, contrast checking, and WCAG guidance for writing accessible code from the start.426 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for accessibility auditing that provides WCAG 2.2 criteria lookup, HTML remediation guidance, and automated documentation generation for UI components. It enables users to analyze code snippets for issues and generate professional accessibility audit reports.120 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets an AI agent scan a web page for WCAG accessibility issues and get back findings it can act on.33 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that scores how usable websites are for AI browser agents by analyzing accessibility trees, providing prioritized fixes, and enabling an improvement loop with baseline comparisons.MIT
- AlicenseAqualityDmaintenanceAn MCP server that audits websites for accessibility (WCAG 2.1 AA/EAA), performance, SEO, design quality, and mobile responsiveness, providing actionable scores, grades, and prioritized fixes.6MIT

@accesslint/mcpofficial
AlicenseAqualityFmaintenanceAn MCP server for WCAG accessibility auditing in AI coding agents, providing tools to audit HTML, files, URLs, and diffs, plus a prompt for React component auditing.5654 npm6MIT
TDQS
Scored across 20 tools
Most tools have clearly distinct scopes (single-page scan, journey scan, HTML snippet scan, vision audit, fix verification, diffing). The main overlap is between the focused checkers (check_color_contrast, check_aria) and the broader scan_page/scan_html, which also surface those findings — but careful descriptions clarify when to reach for the narrow tools versus the full scan.
Names are mostly verb_noun (scan_page, verify_fix, start_audit, add_site, list_sites, get_rules, generate_report_pdf). A handful invert to noun/qualifier + verb (flow_scan, diff_scan, visual_audit), which is a minor deviation but still readable and predictable.
At 20 tools this is on the heavier side, but the breadth (page/journey/HTML/vision scanning, fixing, verification, history, reporting, account and widget management) justifies the surface. Each tool maps to a distinct capability rather than padding, so it stays reasonable for the scope.
The set covers the full accessibility lifecycle: find (scan_page, flow_scan, scan_html, visual_audit), diagnose (check_color_contrast, check_aria, detect_framework, get_rules, find_source), fix (generate_ai_fix), verify (verify_fix, diff_scan), persist/report (scan_history, generate_report_pdf, start_audit/get_audit), plus site/widget/account management. No obvious dead ends.