# WCAG 2.2 Compliance (mcpb · wcag-compliance-mcp.mcpb)

WCAG 2.2 audits with corrected markup, verified fix examples, and U.S. ADA deadlines.

- Trust score: 41/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `wcag-compliance-mcp.mcpb`: 41/100 (this document), [markdown](https://verifymcp.io/servers/veduis-wcag-compliance-mcp/wcag-compliance-mcp.md), [page](https://verifymcp.io/servers/veduis-wcag-compliance-mcp/wcag-compliance-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Veduis/wcag-compliance-mcp/releases/download/v1.0.0/wcag-compliance-mcp.mcpb`
- Transport: `stdio`
- SHA-256: `a8f5e1694a966ea4bfdf311b1186c7a8d1e243f0e4747de223e95a36e05bc681`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 619 tokens (~123/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 64% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the WCAG 2.2 Compliance MCP server?

WCAG 2.2 Compliance ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, a8f5e1694a966ea4bfdf311b1186c7a8d1e243f0e4747de223e95a36e05bc681; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Veduis/wcag-compliance-mcp/releases/download/v1.0.0/wcag-compliance-mcp.mcpb`
- SHA-256: `a8f5e1694a966ea4bfdf311b1186c7a8d1e243f0e4747de223e95a36e05bc681`

### Verify on macOS / Linux

```bash
echo "a8f5e1694a966ea4bfdf311b1186c7a8d1e243f0e4747de223e95a36e05bc681  wcag-compliance-mcp.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\wcag-compliance-mcp.mcpb).Hash -eq "a8f5e1694a966ea4bfdf311b1186c7a8d1e243f0e4747de223e95a36e05bc681"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 41, +2)

- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Maintenance: unverified → pass

### 2026-11-02 (score 39, 0)

- [security regression] Provenance: unverified → fail

### 2026-11-01 (score 39, −2)

- [security regression] Provenance: fail → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Maintenance: pass → unverified

### 2026-10-29 (score 41)

First indexed and scored.

## MCP tools (4)

### `audit_html_snippet` (~148 tokens)

Audit HTML for WCAG 2.2 defects

Run 18 static WCAG 2.2 checks against an HTML snippet or full page and return findings with the failing success criterion, the offending markup, and a corrected example. Covers alt text, accessible names for links and buttons, form labels, language, title, heading order, duplicate ids, tabindex, aria-hidden, list structure, iframe titles, table headers, video captions, viewport zoom, and autocomplete purpose. Static analysis only: it cannot judge contrast, keyboard traps, focus visibility, or reading order in a rendered page.

Input parameters:

- `html` (string, required): HTML fragment or full document to audit
- `severity_floor` (string): Return only errors (default) or every finding

### `lookup_wcag_criterion` (~124 tokens)

Look up a WCAG 2.2 success criterion

Search the 87 WCAG 2.2 success criteria by number (1.4.3), name (Contrast), keyword, or axe-core rule name. Returns level, principle, guideline, whether it applies to U.S. ADA Title II entities, the practical test, the axe-core rules that target it, and links to the W3C specification and Understanding document.

Input parameters:

- `level` (string)
- `limit` (integer)
- `query` (string, required): Criterion number, name, or keyword such as "focus visible" or "contrast"

### `get_verified_fix_example` (~155 tokens)

Get a browser-verified WCAG fix example

Return a failing HTML snippet and its corrected version for a WCAG 2.2 defect, with an explanation of the impact on assistive technology and a manual test step. Every pair was executed in headless Chromium against axe-core 4.14.0, and the detection method is reported so you know whether automation catches this defect or a human must. Look up by criterion number (2.4.7), pair id (wcag-1-4-3-01), or keyword (focus indicator).

Input parameters:

- `limit` (integer)
- `query` (string): Keyword when the criterion number is unknown
- `sc_id` (string): Success criterion number, for example 1.4.3

### `check_ada_compliance_deadlines` (~159 tokens)

Check ADA / Section 504 web accessibility deadlines

Return the dated web accessibility obligations that apply to an entity type, from the 1990 ADA statute through the 2027 and 2028 deadlines in the DOJ Title II final rule and the HHS Section 504 rule. Reports what is binding now, what is upcoming within the horizon with days remaining, and the primary source URL for every date. Entity types: title_ii_large, title_ii_small, title_iii_business, federal_contractor, hhs_recipient, eu_business, ontario.

Input parameters:

- `as_of` (string): Reference date in YYYY-MM-DD, defaults to today
- `entity_type` (string, required): Entity type to scope the timeline to
- `horizon_years` (integer)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/veduis-wcag-compliance-mcp/wcag-compliance-mcp#diagnostics

## Score history

- 2026-11-05: 41
- 2026-11-04: 41
- 2026-11-03: 41
- 2026-11-02: 39
- 2026-11-01: 39
- 2026-10-31: 41
- 2026-10-30: 41
- 2026-10-29: 41

## Common questions

### What is the WCAG 2.2 Compliance MCP server?

WCAG 2.2 Compliance is an MCP server listed in the public MCP registry as io.github.Veduis/wcag-compliance-mcp. WCAG 2.2 audits with corrected markup, verified fix examples, and U.S. ADA deadlines. This page covers its MCPB bundle (https://github.com/Veduis/wcag-compliance-mcp/releases/download/v1.0.0/wcag-compliance-mcp.mcpb).

### Is the WCAG 2.2 Compliance MCP server safe to use?

WCAG 2.2 Compliance scores 41 out of 100 on VerifyMCP. 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 WCAG 2.2 Compliance MCP server expose?

WCAG 2.2 Compliance exposes 4 tools: audit_html_snippet, lookup_wcag_criterion, get_verified_fix_example, check_ada_compliance_deadlines. Their descriptions and schemas cost roughly 586 tokens of context every time the server is loaded.

### What licence is the WCAG 2.2 Compliance MCP server under?

WCAG 2.2 Compliance declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/Veduis/wcag-compliance-mcp
- Website: https://veduis.com/products/vcompliance-scanner/
- Changelog RSS feed: https://verifymcp.io/servers/veduis-wcag-compliance-mcp/wcag-compliance-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/veduis-wcag-compliance-mcp/wcag-compliance-mcp.json
- HTML version of this page: https://verifymcp.io/servers/veduis-wcag-compliance-mcp/wcag-compliance-mcp