Back to Browse

Accessibility Scanner MCP Server

Developer ToolsModerate6.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Scan any URL for WCAG accessibility issues (axe-core) and get per-element fixes for an AI agent.

About

Scan any URL for WCAG accessibility issues (axe-core) and get per-element fixes for an AI agent.

Security Report

6.2
Moderate6.2Moderate Risk

Well-designed MCP server with strong security practices for its stated purpose. The server runs accessibility scans locally using Playwright and axe-core, with proper input validation, no credential handling, and appropriately scoped permissions. Minor code quality observations around error handling and logging do not materially affect security posture. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

3 files analyzed · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

env_vars

Check that this permission is expected for this type of plugin.

process_spawn

Check that this permission is expected for this type of plugin.

system_info

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Path to a Chrome/Chromium binary, if not auto-detected.Optional

Environment variable: CHROME_PATH

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-bishop81-accessibility-scanner-mcp": {
      "env": {
        "CHROME_PATH": "your-chrome-path-here"
      },
      "args": [
        "-y",
        "accessibility-scanner-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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 (claude_desktop_config.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

Input
url (string, required)The http(s) URL to scan.

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 scan_accessibility) → 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

Reviews

No reviews yet

Be the first to review this server!