A11y Check MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Accessibility scans with WCAG and Korean KWCAG remediation mappings: Do WCAG/KWCAG mappings remain current while advisory-only findings stay excluded from compliance rates?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Accessibility scans and remediation guidance for public or local web pages, including WCAG/KWCAG workflows.

What we know

MCP integration for A11y Check's accessibility engine. It can scan localhost pages in place, return violation details and remediation guidance, and complements automated findings with explicit manual checks rather than claiming full conformance.

Maintenance / activity evidence

@a11ychk/mcp 0.2.0 published 2026-10-03T03:04:09.754Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read/analyze page content and local web targets; no production mutation evidenced.
Authentication not yet verified.
Sensitive access: Potentially internal page content when scanning localhost/authenticated development targets

Testing-oriented and non-destructive, but internal page content may be exposed to the scanner.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do WCAG/KWCAG mappings remain current while advisory-only findings stay excluded from compliance rates?

The bounded review of the publisher's documented Accessibility scans with WCAG and Korean KWCAG remediation mappings and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Testing-oriented and non-destructive, but internal page content may be exposed to the scanner.
Read/analyze page content and local web targets; no production mutation evidenced.
Audited page content is processed by the accessibility engine; local/private page handling depends on MCP/client environment.
Sensitive access: Potentially internal page content when scanning localhost/authenticated development targets
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
exact MCP authentication/env variables
retention for hosted scans
Automated checks cannot establish full accessibility conformance.
Authenticated/bot-blocked pages may require browser-extension workflows rather than server crawling.
Manual criteria remain a human-review responsibility.

Original activity observations

@a11ychk/mcp 0.2.0 published 2026-10-03T03:04:09.754Z

Technical identity

npm/@a11ychk/mcp

Exact implementation source: https://www.npmjs.com/package/@a11ychk/mcp ↗
Reviewed resource type: Testing / Debugging
Repository identity: IsaacEryn/a11ychk
Package identity: npm:@a11ychk/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@a11ychk/mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
www.a11ychk.com/en/about
Source material retained for this review.
Includes references whose attribution is not established.
GitHub repository ↗
isaaceryn/a11ychk
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Testing / Debugging setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
MCP100 setup guide
Publisher: register using claude mcp add a11ychk -- npx -y @a11ychk/mcp; Playwright Chromium is a separate prerequisite (npx playwright install chromium).
publisher install or stdio launch · Publisher instructions
npx -y @a11ychk/mcp
reviewed install or registration · Claude Code only · MCP100 composed guide
claude mcp add a11ychk -- npx -y @a11ychk/mcp
Configure / authenticate
MCP100 setup guide
Run Playwright Chromium prerequisite `npx playwright install chromium`; register stdio in Claude Code.
Check connection
Suggested check
Check tool discovery and run a non-mutating browser/accessibility check against a test page.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `a11ychk`, remove the client entry with `claude mcp remove a11ychk`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove a11ychk

Official Documentation & Sources

https://www.npmjs.com/package/@a11ychk/mcp ↗

What it does

MCP integration for A11y Check's accessibility engine. It can scan localhost pages in place, return violation details and remediation guidance, and complements automated findings with explicit manual checks rather than claiming full conformance.

Capability: Security & Testing
Resource type: Testing / Debugging
Industry: Software & Technology, Legal & Compliance
Best fit: Accessibility scans and remediation guidance for public or local web pages, including WCAG/KWCAG workflows.

Representative uses

Scan local/public pages
Review WCAG 2.2 AA/KWCAG violations
Get selectors/offending code/fix guidance
Export evidence for accessibility review

Limitations

Automated checks cannot establish full accessibility conformance.
Authenticated/bot-blocked pages may require browser-extension workflows rather than server crawling.
Manual criteria remain a human-review responsibility.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Read/analyze page content and local web targets; no production mutation evidenced.
Data handling: Audited page content is processed by the accessibility engine; local/private page handling depends on MCP/client environment.
Cost: freemium_or_service_plan
Risk and cautions: Testing-oriented and non-destructive, but internal page content may be exposed to the scanner.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Potentially internal page content when scanning localhost/authenticated development targets
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Scan local/public pages; Review WCAG 2.2 AA/KWCAG violations; Get selectors/offending code/fix guidance; Export evidence for accessibility review.

What setup information is documented?

Recorded installation/entrypoint step: npx -y @a11ychk/mcp. Recorded transport: stdio. Prerequisites: Node/npm; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read/analyze page content and local web targets; no production mutation evidenced.

What data-handling boundary should I consider?

Audited page content is processed by the accessibility engine; local/private page handling depends on MCP/client environment. Recorded sensitive-access context: Potentially internal page content when scanning localhost/authenticated development targets.

What limitations and risks should I check before use?

Testing-oriented and non-destructive, but internal page content may be exposed to the scanner. Automated checks cannot establish full accessibility conformance. Authenticated/bot-blocked pages may require browser-extension workflows rather than server crawling. Manual criteria remain a human-review responsibility. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is freemium or service plan. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.