mcpbeat Sign in

Pandus Accessibility MCP Server

answering

Pandus Accessibility is answering right now. Last checked 12 min ago. It exposes 3 tools.

WCAG 2.2 rule reference for free; with an API key: what to fix on your sites and new checks.

Uptime history 12 days of history · worst day 99%
12 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
703 ms
Response time
average over 24h
open, no key
Access
streamable-http

Pandus Accessibility missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add accessibility --transport http https://pandus.online/mcp
Settings → Connectors → Add custom connector, then paste this address
https://pandus.online/mcp
~/.codex/config.toml
[mcp_servers.accessibility]
url = "https://pandus.online/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "accessibility": {
      "url": "https://pandus.online/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "accessibility": {
      "type": "http",
      "url": "https://pandus.online/mcp"
    }
  }
}

Available tools 3

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

explain
explain_rule
Explains one accessibility rule (an axe-core rule id such as image-alt or color-contrast): what is wrong, why it matters for customers, who is affected, how to fix it in code and on Shopify, WooCommerce, PrestaShop or Shoptet, and the WCAG 2.2 / EN 301 549 clauses. Free, no API token needed.
explain_wcag_criterion
Explains a WCAG 2.2 level A or AA success criterion (for example 2.4.7) in plain words: what it asks, examples, how to test it by hand and what automated checks can and cannot find. Free, no API token needed.
rules
search_rules
Searches the Pandus library of accessibility rule cards (the axe-core rules Pandus checks, explained for business owners) by words, an axe rule id or a WCAG success criterion such as 1.4.3. Free, no API token needed.

Endpoints

URLTransportStateLatencyChecked
https://pandus.online/mcp streamable-http answering 691 ms 12 min ago

Alternatives to Pandus Accessibility

same job, measured the same way
Inclusify Accessibility
by inclusifyapp

Accessibility and WCAG data for your own websites: fix lists, live checks, and fix validation.

answering
Siteaudit
by thegridwork

Audit websites for accessibility, performance, SEO, design, and mobile. 47 WCAG checks.

39 installs/wk local only
AccessLumens
by accesslumens

Free WCAG accessibility checks for any page, including localhost, with fix guidance for each issue.

486 installs/wk local only
Evolize
by evolize

Accessibility scans with evidence, public reports, and fresh checks after fixes.

3 tools answering
A11yScope
by perceivable

WCAG 2.2 AA accessibility checks for pages and HTML, run locally in headless Chrome.

89 installs/wk local only
geo-score
by jianruntech

Free 0-100 score: can AI engines cite a site? Plus citation checks with your own API keys.

191 installs/wk local only
Trail Fortress Fitment
by trailfortress

Free, read-only truck and Jeep parts fitment: what fits your vehicle, fit checks, tire sizes.

6 tools answering
Crawlbit
by amati032-dev

Four free tools to check if AI engines can find, read and recognise a site. No API key.

52 installs/wk local only

Pandus Accessibility — questions

Answers built from our own checks of this server.

What can Pandus Accessibility do?
It exposes 3 tools, read directly from the server on our last check. Among them: explain_rule, explain_wcag_criterion, search_rules. 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 Pandus Accessibility 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 703 ms. The bar chart above shows every period we have measured.
How do I connect Pandus Accessibility?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Pandus Accessibility need an API key?
No. Pandus Accessibility completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Pandus Accessibility?
It answers our handshake in 703 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.