wcag-accessibility-mcp

MCPcommunity
v0.1.6io.github.aditya-ariosityUnknownUpdated 1mo agonpmGitHub

A WCAG accessibility testing MCP for AI agents, Codex, Claude Code, and automated UI audits.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.aditya-ariosity
LicenseUnknown
Version0.1.6
Sourcenpm+mcp-registry
npmwcag-accessibility-mcp
GitHubaditya-ariosity/wcag-accessibility-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface7 tools · none privileged
Security scan✓ Cleanv0.1.6 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

7 tools · none privileged
Statically extracted from the published packagev0.1.6 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

audit_urlLoad a public or local web page in headless Chromium, run axe-core, and return prioritized WCAG findings, DOM evidence, computed styles, and contrast corrections. Read-only.

Load a public or local web page in headless Chromium, run axe-core, and return prioritized WCAG findings, DOM evidence, computed styles, and contrast corrections. Read-only.

No input schema was published for this tool.

audit_htmlRender supplied HTML in an isolated headless browser and return WCAG findings plus evidence and suggested corrections. Use for generated UI before it is hosted. Read-only.

Render supplied HTML in an isolated headless browser and return WCAG findings plus evidence and suggested corrections. Use for generated UI before it is hosted. Read-only.

No input schema was published for this tool.

audit_fileRender a local .html or .htm file beneath the configured allowed root and return accessibility findings and corrections. Read-only.

Render a local .html or .htm file beneath the configured allowed root and return accessibility findings and corrections. Read-only.

No input schema was published for this tool.

check_contrastCalculate the WCAG contrast ratio for foreground and background colors and determine whether the pair passes for the supplied text size and weight.

Calculate the WCAG contrast ratio for foreground and background colors and determine whether the pair passes for the supplied text size and weight.

No input schema was published for this tool.

suggest_contrast_fixFind the nearest black-or-white-directed foreground or background adjustment that reaches the selected WCAG contrast threshold. Returns a mathematical candidate, not an automatic edit.

Find the nearest black-or-white-directed foreground or background adjustment that reaches the selected WCAG contrast threshold. Returns a mathematical candidate, not an automatic edit.

No input schema was published for this tool.

explain_issueReturn implementation-focused remediation steps and the axe rule reference for a rule ID found in an audit.

Return implementation-focused remediation steps and the axe rule reference for a rule ID found in an audit.

No input schema was published for this tool.

get_wcag_checklistReturn every success criterion required by a WCAG 2.0, 2.1, or 2.2 A/AA/AAA profile, with W3C references, axe rule mappings, and explicit automated-partial versus manual coverage. Use this to plan the checks that a browser audit cannot complete.

Return every success criterion required by a WCAG 2.0, 2.1, or 2.2 A/AA/AAA profile, with W3C references, axe rule mappings, and explicit automated-partial versus manual coverage. Use this to plan the checks that a browser audit cannot complete.

No input schema was published for this tool.

7 of 7 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

A WCAG accessibility testing MCP for AI agents, Codex, Claude Code, and automated UI audits.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

7 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-01 — observed resolution, not a publisher declaration.

60 packages resolved · 5 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

67 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+55 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.