AccessLumens
NPM · @ACCESSLUMENS/MCP
Free WCAG accessibility checks for any page, including localhost, with fix guidance for each issue.
Available components
Last scanned (16 hours ago)
Scores higher than 36% 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
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 581 tokens (~290/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.86 ▲ functional
- 22 Oct 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Dependency health: 0.85 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.1 → 0.1.3 functional
- Package version: 0.1.1 → 0.1.2 functional
- 21 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 48
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 24 Oct 2026 · Analysed npm/@accesslumens/mcp@0.1.3
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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
check_accessibility Check accessibility ~271
Runs the AccessLumens accessibility scanner (axe-core plus AccessLumens keyboard, focus and reflow checks) in a local headless browser and returns a 0-100 score and every issue: severity, WCAG success criteria, how to fix it, and each failing element's CSS selector, markup and the reason it failed. Works on localhost and other local addresses, public URLs, and local .html files or folders. Takes about 10-60 seconds per page. Re-run after fixing to verify. A clean result covers only what automation can detect: before reporting the work as done, also review the source for repeated buttons or links with the same name and alt text that repeats nearby text.
| Name | Type | Req | Description |
|---|---|---|---|
| crawl | boolean | – | Follow same-site links and test up to 10 pages instead of only this one. |
| keyboard | boolean | – | Also test keyboard access: unreachable controls, keyboard traps, invisible focus, skip links, and reflow at 320px. Slower; turn off for a quick check. |
| max_issues | integer | – | Most issue types to return, most severe first. |
| url | string | yes | Page to scan: a URL (http://localhost:3000/checkout, https://example.com), or a path to a local .html file or folder. |
No output schema declared.
No examples provided.
explain_issue Explain an accessibility rule ~88
Explains one accessibility rule from a check_accessibility result: what it means, who it affects, how to fix it, the WCAG success criteria it maps to (with W3C links), and a reference page.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | The rule id shown in a check_accessibility result, e.g. "color-contrast", "button-name", "keyboard-trap". |
No output schema declared.
No examples provided.
How do I install the AccessLumens MCP server?
AccessLumens runs locally as an npm package, launched with npx -y @accesslumens/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 · @accesslumens/mcp
claude mcp add com-accesslumens-mcp -- npx -y @accesslumens/mcp
What is the AccessLumens MCP server?
AccessLumens is an MCP server listed in the public MCP registry as com.accesslumens/mcp. Free WCAG accessibility checks for any page, including localhost, with fix guidance for each issue. This page covers its npm package (@accesslumens/mcp).
Is the AccessLumens MCP server safe to use?
AccessLumens scores 59 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 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 AccessLumens MCP server expose?
AccessLumens exposes 2 tools: check_accessibility, explain_issue. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded.
Is the AccessLumens MCP server still maintained?
AccessLumens is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.