mcpbeat Sign in

WIA A11y Checker MCP Server

answering

WIA A11y Checker is answering right now. Last checked 1 min ago. It exposes 2 tools.

Automated accessibility check (axe-core, Lighthouse) of one public web page; fetch saved results.

Uptime history 13 days of history · worst day 99%
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
918 ms
Response time
average over 24h
open, no key
Access
streamable-http

WIA A11y Checker missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add a11y --transport http https://mcp-a11y.wiabook.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp-a11y.wiabook.com/mcp
~/.codex/config.toml
[mcp_servers.a11y]
url = "https://mcp-a11y.wiabook.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "a11y": {
      "url": "https://mcp-a11y.wiabook.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "a11y": {
      "type": "http",
      "url": "https://mcp-a11y.wiabook.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

a11y
a11y_check_url
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개 자동 접근성 검사. 자동 검사는 준수를 증명하지 못하며 수동 확인이 남음.)
a11y_get_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. (저장된 접근성 검사 결과 요약 조회.)

Endpoints

URLTransportStateLatencyChecked
https://mcp-a11y.wiabook.com/mcp streamable-http answering 923 ms 1 min ago

Alternatives to WIA A11y Checker

same job, measured the same way
MCP Accessibility Scanner
by justasmonkev

MCP server for automated web accessibility scanning with Playwright and Axe-core.

1 590 installs/wk local only
EuroA11y
by euroa11y

Accessibility audit of a web page (WCAG 2.2 AA, RGAA) and European Accessibility Act scope check

2 tools answering
Page Fetch
by openkrill

Read one public web page as clean Markdown with its links, after a robots.txt check.

5 tools answering
Evolize
by evolize

Accessibility scans with evidence, public reports, and fresh checks after fixes.

3 tools answering
PageSpeed & Lighthouse Checker
by monietools

Lighthouse scores, Core Web Vitals (LCP, CLS, INP/TBT) and top fixes for any URL, mobile or desktop.

answering
A11y Check
by a11ychk

Web accessibility scanning (WCAG 2.2 AA + KWCAG 2.2) with Korean remediation guides

60 installs/wk local only
webrecipe
by pillsoon

Save how to read a public web page once, then fetch fresh items as JSON without a browser.

24 installs/wk local only
Bulk PageSpeed & Lighthouse Checker: Core Web Vitals from CSV
by nero-engine

Google PageSpeed Insights (Lighthouse) scores, Core Web Vitals and top speed fixes for every URL...

answering

WIA A11y Checker — questions

Answers built from our own checks of this server.

What can WIA A11y Checker do?
It exposes 2 tools, read directly from the server on our last check. Among them: a11y_check_url, a11y_get_result. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is WIA A11y Checker working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 918 ms. The bar chart above shows every period we have measured.
How do I connect WIA A11y Checker?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does WIA A11y Checker need an API key?
No. WIA A11y Checker completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is WIA A11y Checker?
It answers our handshake in 918 ms on average, which is faster than 8% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.