wcagc — accessibility scanning MCP Server
io.github.WCAG-Compliance/mcp
answering
wcagc — accessibility scanning is answering right now. Last checked 6 min ago. 1 231 installs a week from npm. Last commit 4 Aug 2026.
Deterministic axe-core accessibility scans (WCAG 2.1 AA, EN 301 549, PDF/UA) via your account.
Installs per day
peak 1 527 · avg 96 · -26% w/w
a month agotoday
Uptime history
41 hours of history · worst hour 67%
41 hours agonow
98.9%
Uptime 24h
90 of 91 checks
—
Tools
hidden behind auth
270 ms
Response time
average over 24h
1 231
Installs / week
npm and PyPI
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
run in your terminal
claude mcp add mcp --transport http https://mcp.wcagc.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.wcagc.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.wcagc.com/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.wcagc.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.wcagc.com/mcp"
}
}
}This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.wcagc.com/mcp | streamable-http | needs key | 273 ms | 6 min ago |
wcagc — accessibility scanning — questions
Answers built from our own checks of this server.
Why is there no tool list for wcagc — accessibility scanning?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 98.9% of checks in the last 24 hours got a reply.
Is wcagc — accessibility scanning working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 270 ms. The bar chart above shows every period we have measured.
How do I connect wcagc — accessibility scanning?
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. You will need your own key or an OAuth login: it refuses anonymous clients.
Does wcagc — accessibility scanning need an API key?
Yes. Every time we knock, wcagc — accessibility scanning answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is wcagc — accessibility scanning?
It answers our handshake in 270 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use wcagc — accessibility scanning?
The npm package @wcagc/mcp was installed 1 231 times in the last week. Week over week that is -26%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is wcagc — accessibility scanning open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.