vertaaux-mcp
Related Servers
Alternatives to vertaaux-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes a design system and UX rulebook as tools, enabling AI to generate UI consistent with your design tokens, components, layout rules, accessibility guidelines, and templates. It also provides a review tool to score UI proposals against the design system.MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted design audit MCP server that reviews UI code against Nielsen's heuristics and an accessibility rubric, returning scores and fixable findings. It also enables verifying previously flagged issues against updated code.80 npmBSD 3-Clause
- AlicenseNot gradedqualityAmaintenanceThis MCP server enables AI agents to measure live web and responsive UIs — contrast ratios, touch targets, overflow, and theme drift — returning precise, selector-attached findings as text. It also lets a human and agent share the same live mobile and desktop session, with pinned notes and screenshots readable by the agent.98 npmMIT
- AlicenseAqualityCmaintenanceMCP server that helps AI agents create UIs that don't look AI-generated by auditing components, refining copy, suggesting themes, and checking accessibility/contrast.8MIT
- AlicenseAqualityBmaintenanceFree WCAG 2.2 / ADA / Section 508 accessibility MCP: scan pages, get AI fixes, verify them, run a vision audit, and scan localhost through a secure tunnel. Sign in with a free account for full audits.20544 npmMIT
- AlicenseBqualityBmaintenanceAn MCP (Model Context Protocol) server for performing accessibility audits on webpages using axe-core. Use the results in an agentic loop with your favorite AI assistants (Cline/Cursor/GH Copilot) and let them fix a11y issues for you!2932 npm53Mozilla Public 2.0
TDQS
Scored across 29 tools
Most tools have distinct purposes, but some pairs (e.g., audit_url vs audit_a11y, suggest_fix vs generate_patch) could cause confusion despite clear descriptions. The 'vs' notes help, but the sheer number of tools increases ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (e.g., audit_url, create_schedule, delete_webhook). No mixing of styles or irregular names.
29 tools is on the high side for a domain that could be covered with fewer. While the set is comprehensive, some tools are deprecated or legacy, and the count feels slightly bloated.
The tool set covers the full lifecycle of accessibility auditing: running audits (multiple types), retrieving results, explaining findings, generating fixes, creating PRs, scheduling, diffing, webhooks, quota management, and even competitor analysis. No obvious gaps.