mcpbeat

A11y Check MCP Server

com.nexaaly/a11y-check
answering

A11y Check is answering right now. Last checked 3 min ago. It exposes 1 tools.

Real-browser WCAG audit that also finds keyboard-inoperable controls axe-core misses, with fixes.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
170 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add a11y-check --transport http https://nexaaly.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "a11y-check": {
      "url": "https://nexaaly.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.a11y-check]
url = "https://nexaaly.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "a11y-check": {
      "url": "https://nexaaly.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "a11y-check": {
      "url": "https://nexaaly.com/mcp"
    }
  }
}

Available tools 1

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

accessibility
check_accessibility
Audit one web page for accessibility problems using a real browser. Runs axe-core (WCAG 2.1 AA) plus checks that standard scanners do not perform: controls that look clickable but cannot be operated by keyboard, error messages not programmatically linked to their field, CAPTCHA barriers, duplicate main landmarks, and missing skip links. Returns findings WITH the code change that fixes each one. Use this when someone asks whether a site is accessible, whether it meets WCAG or the European Accessibility Act, or whether keyboard and screen-reader users can operate its controls.

Endpoints

URLTransportStateLatencyChecked
https://nexaaly.com/mcp streamable-http answering 223 ms 3 min ago

A11y Check — questions

Answers built from our own checks of this server.

What can A11y Check do?
It exposes 1 tools, read directly from the server on our last check. Among them: check_accessibility. 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 A11y Check working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 170 ms. The bar chart above shows every period we have measured.
How do I connect A11y Check?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does A11y Check need an API key?
No. A11y Check completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is A11y Check?
It answers our handshake in 170 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.