All servers · Shops & products
Pandus Accessibility
online.pandus/accessibility · v1.0.0
New (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | prompts, resources, tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
WCAG 2.2 rule reference for free; with an API key: what to fix on your sites and new checks.
Connect
streamable-http · https://pandus.online/mcp
claude mcp add --transport http accessibility https://pandus.online/mcp{
"mcpServers": {
"accessibility": {
"url": "https://pandus.online/mcp"
}
}
}Tools as reported by the server
search_rulesSearches 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.explain_ruleExplains 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_criterionExplains 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.
Website · JSON · Text for agents · Registry updated 2026-10-20