com.mambabuilt/mcp-wcag-accessibility-audit
NPM · @MAMBALABSDEV/MCP-WCAG-ACCESSIBILITY-AUDIT
Audit websites for WCAG issues with axe-core, plus EAA exposure signals and compliance page checks.
Available components
Last scanned (10 hours ago)
Scores higher than 40% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 476 tokens (~476/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/@mambalabsdev/mcp-wcag-accessibility-audit@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_wcag_accessibility Audit WCAG accessibility ~476
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compliance_checks | array | – | Optional presence checks, charged once per domain as compliance-checked when any is set. impressum runs only on German language or .de sites and reports field types, never values. |
| domain | string | – | One website domain, for example mambabuilt.com. The homepage is audited. Required unless domains is set. |
| domains | array | – | A list of website domains, one row per domain. Used instead of domain when set. |
| max_charge_usd | string | – | Optional cost cap in USD, for example 1.50. The run stops before starting a domain that could take its charges past it. |
| pages | string | – | Pages per domain. 1 audits the homepage; 2 to 5 add pages from the sitemap or the homepage navigation, each charged as page-audited. Default 1. |
| skipCache | string | – | false reuses an identical audit from the last 24 hours; true audits fresh. Default false. |
| standard | string | – | Rule set to run. ada runs WCAG 2.1 AA, the level the ADA Title II rule names. en301549 runs the rules axe maps to EN 301 549, the standard the EAA points to. Default wcag21aa. |
| viewport | string | – | desktop renders at 1280 by 800; mobile at 390 by 844 with touch. Default desktop. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-wcag-accessibility-audit server?
com.mambabuilt/mcp-wcag-accessibility-audit runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-wcag-accessibility-audit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-wcag-accessibility-audit
claude mcp add com-mambabuilt-mcp-wcag-accessibility-audit -- npx -y @mambalabsdev/mcp-wcag-accessibility-audit
What is the com.mambabuilt/mcp-wcag-accessibility-audit server?
com.mambabuilt/mcp-wcag-accessibility-audit is listed in the public MCP registry as com.mambabuilt/mcp-wcag-accessibility-audit. Audit websites for WCAG issues with axe-core, plus EAA exposure signals and compliance page checks. This page covers its npm package (@mambalabsdev/mcp-wcag-accessibility-audit).
Is the com.mambabuilt/mcp-wcag-accessibility-audit server safe to use?
com.mambabuilt/mcp-wcag-accessibility-audit scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-wcag-accessibility-audit server expose?
com.mambabuilt/mcp-wcag-accessibility-audit exposes 1 tool: audit_wcag_accessibility. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-wcag-accessibility-audit server still maintained?
com.mambabuilt/mcp-wcag-accessibility-audit is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-wcag-accessibility-audit server under?
com.mambabuilt/mcp-wcag-accessibility-audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.