A
licenseA
qualityB
maintenanceMCP server for axe-core accessibility audits. Enables scanning URLs or HTML for WCAG violations with impact levels and fix guidance.
4
14 npm
1
MIT
axecap
by ICJIA
Related Servers
Alternatives to axecap
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn 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!2228 npm52Mozilla Public 2.0
- AlicenseBqualityDmaintenanceA proxy MCP server that summarizes Playwright accessibility snapshots using Claude Haiku, reducing context usage for efficient browser automation.258 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that enables LLMs to perform web accessibility testing against WCAG standards using Deque Axe-core API and Puppeteer.6178 npm91MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that extracts accessibility tree, design tokens, screenshots, Claude DSL, and Figma JSON from any URL using a persistent Chromium browser with zero LLM cost.MIT
- FlicenseAqualityBmaintenanceAn MCP server that gives Claude direct control of a real browser via Playwright, enabling AI-driven web testing, autonomous test execution, and live failure analysis through natural language.84,799 npm3-
TDQS
A4.3/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: auditing a URL, auditing HTML, listing rules, getting rule details, and checking server status. There is no overlap or ambiguity between them.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using underscores (audit_url, audit_html, get_rules, get_rule_info, get_status). The naming is uniform and predictable.
Tool Count5/5
With 5 tools, the set is well-scoped for an accessibility auditing server. Each tool serves a necessary function without redundancy or bloat.
Completeness5/5
The tool set covers the core domain: performing audits on both live URLs and raw HTML, accessing comprehensive rule information, and checking server status. There are no obvious gaps in the workflow.
Maintenance
ActivityMaintained
ResponsivenessNo issues