# WIA A11y Checker (remote · mcp-a11y.wiabook.com)

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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp-a11y.wiabook.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-wiabook-a11y/mcp-a11y.md), [page](https://verifymcp.io/servers/com-wiabook-a11y/mcp-a11y)

## Channel facts

- Endpoint: `https://mcp-a11y.wiabook.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-wiabook-a11y 'https://mcp-a11y.wiabook.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-wiabook-a11y": {
      "url": "https://mcp-a11y.wiabook.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-wiabook-a11y": {
      "type": "http",
      "url": "https://mcp-a11y.wiabook.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-wiabook-a11y]
url = "https://mcp-a11y.wiabook.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wiabook-a11y": {
      "type": "remote",
      "url": "https://mcp-a11y.wiabook.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wiabook-a11y --url 'https://mcp-a11y.wiabook.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wiabook-a11y:
    url: "https://mcp-a11y.wiabook.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-wiabook-a11y": {
      "Transport": "http",
      "Url": "https://mcp-a11y.wiabook.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-wiabook-a11y -t streamable-http -u 'https://mcp-a11y.wiabook.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-wiabook-a11y": {
      "type": "http",
      "url": "https://mcp-a11y.wiabook.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 80, +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.

### 2026-11-02 (score 79, +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.

### 2026-10-31 (score 78, +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.

### 2026-10-29 (score 77, +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.

### 2026-10-27 (score 76, +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.

### 2026-10-25 (score 75, +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.

### 2026-10-23 (score 74, +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.

### 2026-10-20 (score 73, +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.

## MCP tools (2)

### `a11y_check_url` (~181 tokens)

Check a public web page for accessibility issues

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

Input parameters:

- `max_violations` (integer): How many top violations to include
- `refresh` (boolean): Ignore the 10-minute cache (counts against limits)
- `url` (string, required): Public http:// or https:// page URL (no credentials, no private/localhost addresses)

### `a11y_get_result` (~94 tokens)

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

Input parameters:

- `id` (string, required): Result ID, e.g. WIA-A11Y-K7M2Q9XP
- `max_violations` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-wiabook-a11y/mcp-a11y#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 71
- 2026-10-16: 71
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 69

## 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.

## Links

- Remote endpoint: https://mcp-a11y.wiabook.com/mcp
- Website: https://a11y.wiabook.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-wiabook-a11y/mcp-a11y.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wiabook-a11y/mcp-a11y.json
- HTML version of this page: https://verifymcp.io/servers/com-wiabook-a11y/mcp-a11y