Pandus MCP server

• Registry nameonline.pandus/accessibilityverified in the MCP registry

The registry name sits under pandus.online. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools3
• Server calls itselfPandus
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 209 ms.

• Its tools do none of the product's use cases we checked: run weekly WCAG 2.2 AA checks across client sites; send plain-language fix reports to business owners.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score72 of 100answers 100 · does the job 0 · definitions 100 · context 100 · connects 100
• What an agent can do with it0 of 2 use cases
• Answered100% of days8 of 8 daily checks
• Median first answer210 ms
• Space in an agent's context≈ 460 tokensthe definitions of all its tools (3), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

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

• 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…

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