Wcag Accessibility Audit MCP server
Audit websites for WCAG issues with axe-core, plus EAA exposure signals and compliance page checks.
0 stars93 downloads/wk
Reviews
Write oneNobody has reviewed Wcag Accessibility Audit yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Wcag Accessibility Audit tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
audit_wcag_accessibility
Public scan report
scanner v0.1.10 · 2026-10-27 · 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 qualitystatic API keys via environment variables6/15
- Maintenancelast push 7 days ago15/15
- Maintainer identitynamespace and repository owner differ4/10
How Wcag Accessibility Audit compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 93
- more than 61% of 12,191 servers with a package
What its tools let an agent do: 1 read
Install Wcag Accessibility Audit in Claude Code, Cursor or VS Code
Runs npx -y @mambalabsdev/mcp-wcag-accessibility-audit on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-wcag-accessibility-audit -- npx -y @mambalabsdev/mcp-wcag-accessibility-audit
What the publisher says
From the Wcag Accessibility Audit repository's README, as published. We do not edit it. Read it on GitHub
WCAG Accessibility Audit MCP Server
An MCP server for the Mamba Labs WCAG Accessibility Audit actor on Apify. Send a domain or a list. Each domain is rendered in a real browser and audited with axe-core, and you get back one row per domain: the WCAG issues automated checks find by severity, the worst failing rules, a score, European Accessibility Act exposure signals, and optional compliance page checks.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Tool
- Inputs
- Pricing
- Your keys
- Full actor documentation
- License
What it does
Audit websites for accessibility with axe-core in a real browser. Give one domain or a list; each domain returns one row with the WCAG issues automated checks find (distinct failing rules by impact, affected element count, top failing rules with help links, sample selectors), a 0 to 100 score, European Accessibility Act exposure signals, and optional presence checks for an accessibility statement, an accessibility overlay widget, a privacy policy, a German Impressum, and the US privacy choice link and GPC file. Blocked, timed out, or unreachable sites return a free row that says why. Automated checks find a subset of WCAG failures and the result is never a conformance claim. A run that does not succeed is returned as an error with its run ID. Read-only on the audited sites; requires an APIFY_TOKEN and consumes Apify credits per audited domain.
All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config (claudedesktopconfig.json), Cursor, or any MCP client:
{
"mcpServers": {
"mamba-wcag-accessibility-audit": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-wcag-accessibility-audit"
],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}Restart the client. The auditwcagaccessibility tool appears.
Prerequisites
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Wcag Accessibility Audit: common questions
- Is Wcag Accessibility Audit MCP server safe?
- Mostly: it is graded B (77/100). Read the Wcag Accessibility Audit safety report
- How do I install Wcag Accessibility Audit?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Wcag Accessibility Audit need an API key?
- Yes. The registry entry asks for
APIFY_TOKEN. - Is Wcag Accessibility Audit maintained?
- The last commit was 15 days ago (2026-10-20). The latest release is v1.0.0.
- What can I use instead of Wcag Accessibility Audit?
- Servers from other publishers that do the same job: Domain Liveness MCP server and Business Contact Finder MCP server.
- How does Wcag Accessibility Audit compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Wcag Accessibility Audit
Same job from other publishers: the closest match first, then the best rated.
- Domain LivenessIs this business's website still there? Checks apex and www, and DNS separately from HTTP.not reviewedEstablishedA
- Business Contact FinderCheck how to contact a business website, and whether that contact path actually works.not reviewedEstablishedA