Remote MCP server that runs an automated axe-core and Lighthouse accessibility check on a public web page and returns scores, badge tier and top violations.
What you can do
Run an automated accessibility check on one public http(s) page, returning a score, badge tier and the most important violations with CSS selectors.
Retrieve the summary of a previously saved check by its result ID, including top violations.
When to use it
Useful when you want an assistant to audit a single public page for accessibility issues and suggest fixes from the reported selectors, or to look up an earlier saved result. Automated checks cannot prove WCAG conformance, so treat output as a starting point rather than a certification.
Requirements
A remote streamable HTTP endpoint; no package, account, API key or environment variable is declared. The page to check must be publicly reachable over http(s), and a check can take roughly one to two minutes.
Before you install
Checks are limited to one public page per call and only web page results are returned. Automated results cannot prove WCAG conformance, so reported scores and badge tiers should not be presented as compliance. The page URL is sent to a third-party service.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.wiabook%2Fa11y/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Run an automated accessibility check (axe-core + Lighthouse) on ONE public http(s) web page and return a score, badge tier, and the most important violations with CSS selectors so you can suggest fixes. Takes up to ~1–2 minutes. Automated checks cannot prove WCAG conformance: 'no automated errors found' still needs manual review. Only public pages are accepted (private/localhost addresses are rejected). (공개 웹 페이지 1개 자동 접근성 검사. 자동 검사는 준수를 증명하지 못하며 수동 확인이 남음.)
Parametersurlrequiredrefreshmax_violations
a11y_get_result
Get a saved accessibility check result
Fetch the summary of a previously saved web accessibility check by its result ID (WIA-A11Y-XXXXXXXX), including top violations. Only results of web page checks are returned. (저장된 접근성 검사 결과 요약 조회.)
Parametersidrequiredmax_violations
Version history
1
v1.0.0LatestOct 13, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.