Mcp Wcag Accessibility Audit

com.mambabuiltPublished by mambabuilt.comv1.0.1Updated Nov 7, 2026

Audit websites for WCAG issues with axe-core, plus EAA exposure signals and compliance page checks.

The publisher's own server: audit.domains - Domain Valuation

Overview

AI-generated overview

Runs WCAG accessibility audits on one domain or a list via an Apify actor, returning axe-core issues, scores and EAA exposure signals.

What you can do
  • Audit one domain or a list of domains for WCAG issues with axe-core in a real browser
  • Get per-domain rows with failing rules by impact, affected element counts, top rules with help links, sample selectors and a 0 to 100 score
  • Choose the standard (WCAG 2.1/2.2 AA, Section 508, ADA, EN 301 549), page count, desktop or mobile viewport
  • Run optional compliance page checks for accessibility statement, overlay widget, privacy policy, Impressum and US privacy links
  • Receive a free explanatory row for blocked, timed-out or unreachable sites
When to use it
Useful when you need a quick automated accessibility screen of one site or a batch of domains, for example checking EU shop domains for European Accessibility Act exposure or whether an accessibility statement and Impressum are present.
Requirements
Runs locally over stdio via npx, so Node.js 18 or newer is needed. Requires an Apify account and an Apify API token supplied as the APIFY_TOKEN environment variable; the tool is listed without a token but calls need one. Network access to Apify and the audited sites is required.
Before you install
Each audited domain, extra page, compliance check and run start consumes Apify credits billed to your Apify account; an optional max_charge_usd cap can limit cost. The APIFY_TOKEN is a secret and should be kept out of shared configs. Audited domains are sent to Apify's actor, and automated checks cover only a subset of WCAG failures, so results are not a conformance claim.

Installation

In SourceWeft

  1. Open Mcp Wcag Accessibility Audit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

WCAG Accessibility Audit MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Wcag Accessibility Audit MCP server]

An MCP server for the Mamba Labs Website Accessibility Checker, WCAG 2.2 AA 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

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 (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "mamba-wcag-accessibility-audit": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-wcag-accessibility-audit"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The audit_wcag_accessibility tool appears.

Prerequisites

Example prompts

  • "Audit mambabuilt.com and example.de against WCAG 2.2 AA and list the critical issues."
  • "Check these 20 EU shop domains for EAA exposure and whether each links an accessibility statement."
  • "Does this German site have an Impressum, and which required fields does it show?"

Tool

audit_wcag_accessibility. One tool. Example arguments:

json
{  "domains": ["mambabuilt.com", "example.de"],  "standard": "wcag22aa",  "compliance_checks": ["accessibility_statement", "impressum", "overlay"]}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults.

InputTypeRequiredDescription
domainstringone of the twoOne website domain. The homepage is audited.
domainsarrayone of the twoA list of website domains, one row per domain.
standardstringnowcag21aa (default), wcag22aa, wcag2aa, wcag2a, section508, ada, or en301549.
pagesstringno1 to 5 pages per domain. Default 1.
viewportstringnodesktop (default) or mobile.
compliance_checksarraynoAny of accessibility_statement, overlay, privacy_policy, impressum, us_privacy_links.
skipCachestringnofalse (default) reuses an identical audit from the last 24 hours; true audits fresh.
max_charge_usdstringnoOptional cost cap for the run, in USD.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
domain-audited, per domain with a rendered audit$0.01$0.0095$0.009$0.0085
page-audited, per page after the homepage$0.002$0.0019$0.0018$0.0017
compliance-checked, per domain with any compliance check$0.003$0.00285$0.0027$0.00255
apify-actor-start, per run start$0.0025$0.0025$0.0025$0.0025

Blocked, timed out, and unreachable domains are never charged.

Your keys

The actor needs no provider key. It reads only the sites you give it and holds no key of its own.

Full actor documentation

apify.com/mambalabs/wcag-accessibility-audit

License

MIT. See LICENSE.

Source: README.md at commit 0b27b48

Tools

1

audit_wcag_accessibility

Audit WCAG accessibility

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.

ParameterspagesdomaindomainsstandardviewportskipCachemax_charge_usdcompliance_checks

Version history

2
  1. v1.0.1LatestNov 5, 2026
  2. v1.0.0Oct 19, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Audit integrations