A11yScope
NPM · A11YSCOPE-MCP
WCAG 2.2 AA accessibility checks for pages and HTML, run locally in headless Chrome.
Available components
Last scanned (23 hours ago)
Scores higher than 35% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 49 of 168 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 650 tokens (~216/item across 3 items; 3 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 Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −3
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed npm/a11yscope-mcp@0.3.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 →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-c475-qrg2-pj4r | CVE-2026-102990 | high | yes | |
| GHSA-7pqw-9j4j-h8q3 | CVE-2026-19693 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H | no |
| GHSA-jmr9-qjv8-65gv | CVE-2026-56876 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | no |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 168 packages
| Packages resolved | 168 |
|---|---|
| Stale | 49 |
| 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 →
list_rules List the accessibility checks ~40
The 31 checks A11yScope runs, each with its WCAG 2.2 success criteria, level, impact, and how to fix it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_html Scan an HTML string for WCAG 2.2 AA issues ~183
Renders the given HTML in headless Chrome and scans it. Use this for markup you generated or are about to write. Pass base_url when the HTML references relative stylesheets or images that live on a server you can reach; otherwise inline the CSS, since contrast checks depend on computed styles.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | Origin to resolve relative URLs against; the HTML is served at this address. |
| html | string | yes | A complete HTML document or a fragment. |
| include_passed | boolean | – | Also list rules with zero findings, each with status passed or inapplicable and its checked count. |
| include_review | boolean | – | Also return items that need a human decision (not failures). |
| max_findings_per_rule | integer | – | Cap on findings returned per rule. |
| viewport_height | integer | – | – |
| viewport_width | integer | – | – |
No output schema declared.
No examples provided.
scan_page Scan a page for WCAG 2.2 AA issues ~189
Loads a URL (http/https) or a local HTML file path in headless Chrome, runs the A11yScope engine, and returns violations grouped by rule with CSS selectors and HTML snippets. Needs the page to be reachable from this machine.
| Name | Type | Req | Description |
|---|---|---|---|
| include_passed | boolean | – | Also list rules with zero findings, each with status passed or inapplicable and its checked count. |
| include_review | boolean | – | Also return items that need a human decision (not failures). |
| max_findings_per_rule | integer | – | Cap on findings returned per rule. |
| url | string | yes | http(s) URL, file:// URL, or a path to an HTML file (relative to the server's working directory). |
| viewport_height | integer | – | – |
| viewport_width | integer | – | – |
| wait_ms | integer | – | Extra time to wait after load, for pages that render late. |
No output schema declared.
No examples provided.
How do I install the A11yScope MCP server?
A11yScope runs locally as an npm package, launched with npx -y a11yscope-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · a11yscope-mcp
claude mcp add perceivable-a11yscope -- npx -y a11yscope-mcp
What is the A11yScope MCP server?
A11yScope is an MCP server listed in the public MCP registry as io.github.perceivable/a11yscope. WCAG 2.2 AA accessibility checks for pages and HTML, run locally in headless Chrome. This page covers its npm package (a11yscope-mcp).
Is the A11yScope MCP server safe to use?
A11yScope scores 68 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 4 November 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 A11yScope MCP server expose?
A11yScope exposes 3 tools: scan_page, scan_html, list_rules. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.
Is the A11yScope MCP server still maintained?
A11yScope is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.