Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WIA A11y Checker

REMOTE · MCP-A11Y.WIABOOK.COM

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

+3 this week 80 Trust /100

Last scanned (8 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 321 tokens (~160/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp-a11y.wiabook.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wiabook.com CN=YE1,O=Let's Encrypt,C=US 17 Sept 2026 16 Dec 2026 ECDSA 256 ECDSA-SHA384 6a2ef2b106c6e35c11747549141189f07b4
SANs: *.wiabook.com, wiabook.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp-a11y.wiabook.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
wiabook.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp-a11y.wiabook.com/mcp Verified 200
http (plaintext) http://mcp-a11y.wiabook.com/mcp HTTPS enforced 301 https://mcp-a11y.wiabook.com/mcp
MCP tools · 2 exposed · ~275 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
a11y_check_url ~181

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개 자동 접근성 검사. 자동 검사는 준수를 증명하지 못하며 수동 확인이 남음.)

NameTypeReqDescription
max_violationsinteger–How many top violations to include
refreshboolean–Ignore the 10-minute cache (counts against limits)
urlstringyesPublic http:// or https:// page URL (no credentials, no private/localhost addresses)

No output schema declared.

No examples provided.

a11y_get_result ~94

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. (저장된 접근성 검사 결과 요약 조회.)

NameTypeReqDescription
idstringyesResult ID, e.g. WIA-A11Y-K7M2Q9XP
max_violationsinteger––

No output schema declared.

No examples provided.

Install

How do I install the WIA A11y Checker MCP server?

WIA A11y Checker is a hosted endpoint at https://mcp-a11y.wiabook.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp-a11y.wiabook.com

# add to Claude Code
claude mcp add --transport http com-wiabook-a11y 'https://mcp-a11y.wiabook.com/mcp'
Common questions

What is the WIA A11y Checker MCP server?

WIA A11y Checker is an MCP server listed in the public MCP registry as com.wiabook/a11y. Automated accessibility check (axe-core, Lighthouse) of one public web page; fetch saved results. This page covers its hosted endpoint (https://mcp-a11y.wiabook.com/mcp).

Is the WIA A11y Checker MCP server safe to use?

WIA A11y Checker scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the WIA A11y Checker MCP server expose?

WIA A11y Checker exposes 2 tools: a11y_check_url, a11y_get_result. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.

Does the WIA A11y Checker MCP server require authentication?

No. We connected to WIA A11y Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the WIA A11y Checker MCP server still maintained?

WIA A11y Checker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.