Accessibility Scanner MCP server
Scan any URL for WCAG accessibility issues (axe-core) and get per-element fixes for an AI agent.
0 stars76 downloads/wk
Reviews
Write oneNobody has reviewed Accessibility Scanner yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Accessibility Scanner tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
scan_accessibilityScan a web page for WCAG 2.2 (A & AA) accessibility issues using axe-core in a real browser.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 11 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Accessibility Scanner compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 90% of 4,460 AI and agents servers
- Tools
- 1
- the typical AI and agents server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 76
- more than 57% of 1,538 AI and agents servers with a package
What its tools let an agent do: 1 read
Install Accessibility Scanner in Claude Code, Cursor or VS Code
Runs npx -y accessibility-scanner-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add accessibility-scanner-mcp -- npx -y accessibility-scanner-mcp
What the publisher says
From the Accessibility Scanner repository's README, as published. We do not edit it. Read it on GitHub
accessibility-scanner-mcp
An MCP server that lets an AI agent scan a web page for WCAG accessibility issues and get back findings it can act on. The agent calls one tool with a URL; it gets every violation grouped by severity, each with the exact element selector, the offending HTML, the specific failure, the WCAG success criterion, and a fix-guide link — plus the items that still need human review.
It runs the real axe-core engine in your local Chrome (via playwright-core), so nothing about the pages you scan leaves your machine. It scrolls the page first so lazy-loaded content is actually checked rather than silently skipped, and it resolves color contrast over CSS gradients, which most tools leave as "needs review."
Upgrading from 0.1.x? 0.2.0 sees more of each page and returns more findings for the same URL.
See CHANGELOG.md.
Part of accessibilityscanner.app.
Requirements
- Node.js 18+
- Google Chrome installed (or set the CHROME_PATH environment variable to a Chromium binary)
Install
Add it to your MCP client's config. No global install needed — npx fetches it on first run.
Claude Desktop (claudedesktopconfig.json), Cursor, Claude Code, or any MCP client:
{
"mcpServers": {
"accessibility-scanner": {
"command": "npx",
"args": ["-y", "accessibility-scanner-mcp"]
}
}
}If Chrome is not auto-detected, add an env block:
{
"mcpServers": {
"accessibility-scanner": {
"command": "npx",
"args": ["-y", "accessibility-scanner-mcp"],
"env": { "CHROME_PATH": "/usr/bin/google-chrome" }
}
}
}The tool
scan_accessibility
Returns a report grouped by severity. For each rule: the WCAG criterion, a fix-guide link, and per element the selector, HTML, and exact failure. Example flow with an agent:
You: Audit https://example.com for accessibility and fix what you can.
Agent: (calls scanaccessibility)* → reads the findings → edits the code → re-scans.
Honest about limits
Automated testing covers the machine-checkable subset of WCAG (most of the issues on a typical page, but not all of it). Items that need human judgement are returned under "Needs manual review." It never claims a page is "compliant."
License
MIT
Nothing above is checked by us. What we check is on the safety report.
Accessibility Scanner: common questions
- Is Accessibility Scanner MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Accessibility Scanner safety report
- How do I install Accessibility Scanner?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Accessibility Scanner need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Accessibility Scanner maintained?
- The last commit was 49 days ago (2026-09-16). The latest release is v0.1.2.
- What can I use instead of Accessibility Scanner?
- Servers from other publishers that do the same job: Agent Security Scanner MCP server, Ts Core MCP server and DCC-MCP Core MCP server.
- How does Accessibility Scanner compare with other AI and agents MCP servers?
- safety score 92/100 (higher than 90% of 4,460 AI and agents servers); tools 1 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Accessibility Scanner
Same job from other publishers: the closest match first, then the best rated.
- Agent Security ScannerSecurity layer for AI agents: blocks prompt injection, detects fake packages, scans vulnerabilities.not reviewedEstablishedC
- Ts CoreAgent-native TypeScript framework for building MCP servers.not reviewedEstablishedA
- DCC-MCP CoreAgent control plane for DCC and engine hosts: one MCP endpoint, one tool contract.not reviewedEstablishedA
- SuperlogOpen-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.not reviewedEstablishedA
- NVIDIA ElementsNVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.not reviewedEstablishedA