io.github.rog0x/a11y
NPM · @ROG0X/MCP-A11Y-TOOLS
Alt text, headings, contrast, ARIA for AI agents
Available components
Last scanned (4 hours ago)
Scores higher than 84% 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
- 32 of 114 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- 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 228 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 366 tokens (~73/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-a11y-tools@1.0.2
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 114 packages
| Packages resolved | 114 |
|---|---|
| Deprecated | 1 |
| Stale | 32 |
| 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_alt_text ~70
Analyze images in HTML for missing, empty, or low-quality alt text. Reports which images need alt text, which use decorative (empty) alt, and which are properly labeled. Also checks linked images and input[type=image].
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The HTML content to analyze for image alt text |
No output schema declared.
No examples provided.
check_color_contrast ~96
Check WCAG 2.x contrast ratio between a foreground and background color pair. Reports AA and AAA compliance for both normal and large text. Accepts hex (#fff, #ffffff), rgb(r,g,b), or named colors.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | yes | Background color in hex, rgb(), or named color format |
| foreground | string | yes | Foreground (text) color in hex, rgb(), or named color format |
No output schema declared.
No examples provided.
check_form_accessibility ~68
Check form elements for accessibility: verifies labels are associated with inputs, radio/checkbox groups use fieldset/legend, placeholder is not used as sole label, autocomplete hints on personal info fields, and detects duplicate IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The HTML content to analyze for form accessibility |
No output schema declared.
No examples provided.
check_heading_hierarchy ~66
Validate heading structure in HTML: checks for proper h1-h6 nesting order, no skipped levels, single h1, empty headings, and heading content quality. Returns a visual tree of the heading structure.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The HTML content to analyze for heading structure |
No output schema declared.
No examples provided.
validate_aria ~66
Validate ARIA attributes in HTML: checks for invalid roles, missing required ARIA properties, redundant ARIA on native elements, aria-label on non-interactive elements, and aria-hidden on focusable elements.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The HTML content to validate for ARIA correctness |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/a11y MCP server?
io.github.rog0x/a11y runs locally as an npm package, launched with npx -y @rog0x/mcp-a11y-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-a11y-tools
claude mcp add rog0x-a11y -- npx -y @rog0x/mcp-a11y-tools
What is the io.github.rog0x/a11y MCP server?
io.github.rog0x/a11y is an MCP server listed in the public MCP registry as io.github.rog0x/a11y. Alt text, headings, contrast, ARIA for AI agents. This page covers its npm package (@rog0x/mcp-a11y-tools).
Is the io.github.rog0x/a11y MCP server safe to use?
io.github.rog0x/a11y scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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 io.github.rog0x/a11y MCP server expose?
io.github.rog0x/a11y exposes 5 tools: check_alt_text, check_heading_hierarchy, check_color_contrast, validate_aria, check_form_accessibility. Their descriptions and schemas cost roughly 366 tokens of context every time the server is loaded.
Is the io.github.rog0x/a11y MCP server still maintained?
io.github.rog0x/a11y is still listed as active in the MCP registry. We last reached this channel on 6 November 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 io.github.rog0x/a11y MCP server under?
io.github.rog0x/a11y declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/a11y MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/a11y, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.