WIA A11y Checker MCP server
com.wiabook/a11ywiabook.comstreamable-httpv1.0.0Scanned
Automated accessibility check (axe-core, Lighthouse) of one public web page; fetch saved results.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the WIA A11y Checker MCP server can do
The WIA A11y Checker MCP server is published by wiabook.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: a11y_check_url), but cannot delete data. 1 tool only reads.
2 tools bring in text other people can write (a11y_check_url and a11y_get_result); 1 tool can send data out of your system (a11y_check_url).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
a11y_check_urlRun 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 …Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Info
The input schema at properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.url.description: "Public http:// or https:// page URL (no credentials, no private/localhost addresses)"
Description, as the server wrote it 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개 자동 접근성 검사. 자동 검사는 준수를 증명하지 못하며 수동 확인이 남음.)
Annotations the server declares
- title: Check a public web page for accessibility issues
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
a11y_get_resultFetch the summary of a previously saved web accessibility check by its result ID (WIA-A11Y-XXXXXXXX), including top violations.Reads text others writeNo findings
Why it is in this group
- The name "a11y_get_result" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it 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. (저장된 접근성 검사 결과 요약 조회.)
Annotations the server declares
- title: Get a saved accessibility check result
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp-a11y.wiabook.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://login.smilestory.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp-a11y.wiabook.com/mcp: tools/list returned 2 tools to an anonymous client, including a11y_check_url (write)
Findings
Matches of fixed checks, with the text they matched.
- Infoa11y_check_url
The input schema at properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.url.description: "Public http:// or https:// page URL (no credentials, no private/localhost addresses)"
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http a11y https://mcp-a11y.wiabook.com/mcpclaude mcp add --transport http a11y https://mcp-a11y.wiabook.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__a11y__a11y_get_result"
],
"ask": [
"mcp__a11y__a11y_check_url"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as a11y. Review it before you use it.
Capability tags behind 2 rules
- mcp__a11y__a11y_check_url untrusted-input, outbound
- mcp__a11y__a11y_get_result untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.wiabook/a11y/verify?hash=7926d8d33ba3ea2bdfa7277caf0ba7b9851cd4cd2b870f8ad5edd18bc9db45da" | jq -e '.changed == false'Pinned hash 7926d8d33ba3, from Nov 14, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.wiabook/a11y/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.wiabook/a11y)Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.
WIA A11y Checker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the WIA A11y Checker MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the WIA A11y Checker MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the WIA A11y Checker MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the WIA A11y Checker MCP server have?
- 2 tools: 1 write, 1 read. a11y_check_url and a11y_get_result.
Does the WIA A11y Checker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the WIA A11y Checker MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): a11y_check_url.
Has the WIA A11y Checker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.