wcagc - accessibility scanning
Spec Support Unverified Confidence: Good (0.85)wcagc - accessibility scanning is an MCP server published by WCAG-Compliance; its MCP spec-revision support has not been verified yet. Last verified 2026-08-07.
Does wcagc - accessibility scanning support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision wcagc - accessibility scanning supports (as of 2026-08-07).
Is wcagc - accessibility scanning a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for wcagc - accessibility scanning (as of 2026-08-07).
How do I connect to wcagc - accessibility scanning?
wcagc - accessibility scanning is available via a hosted remote endpoint at https://mcp.wcagc.com/mcp, the package npm:@wcagc/mcp, the official MCP Registry under io.github.WCAG-Compliance/mcp, the source repository at https://github.com/wcag-compliance/wcagc-mcp. Authentication: oauth. Transports: streamable-http.
When were wcagc - accessibility scanning's facts last verified?
2026-08-07. Each fact on this page links to the sources used to verify it.
Deterministic axe-core accessibility scans (WCAG 2.1 AA, EN 301 549, PDF/UA) via your account.
How widely adopted is wcagc - accessibility scanning?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.WCAG-Compliance/mcp at version 0.7.2 - lists remote endpoint https://mcp.wcagc.com/mcp and repository https://github.com/wcag-compliance/wcagc-mcp - accessed
- Endpoint probe of https://mcp.wcagc.com/mcp - authorization required (HTTP 401, Bearer error="invalid_token", error_description="Missing Aut); capability set not observable without credentials - accessed