Ext Ops Panel
Open dashboard
Comparison

A11Y Toolkit vs Axcess — Design Accessibility Evaluation

A11Y Toolkit is an MCP server published by kinti. Marketplaces we read that list it: 1 (Official MCP Registry). Axcess — Design Accessibility Evaluation is an MCP server published by sicxz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceA11Y ToolkitAxcess — Design Accessibility Evaluation
Official MCP Registry Listed
Version: 5.14.0
Downloads/month (PyPI): 5 352
Downloads/week (PyPI): 1 192
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.2.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

A11Y Toolkit vs Axcess — Design Accessibility Evaluation
FactA11Y ToolkitAxcess — Design Accessibility Evaluation
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)2026-10-23Not published
Where it runs (differs)On your machine (a11y-toolkit)Remote server (axcess-mcp-server.fly.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/kinti/a11y-toolkitNot stated
Changes in the last 7 days (differs)60
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

A11Y Toolkit

In its own words, on Official MCP Registry:

The accessibility layer for AI coding agents: audit, fix, document and watch - WCAG 2.2.

Axcess — Design Accessibility Evaluation

In its own words, on Official MCP Registry:

Evaluates UI designs for WCAG accessibility issues automated scanners miss. Paid via x402 on Base.

How to run each

A11Y Toolkit As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio a11y-toolkit -- uvx a11y-toolkit --from a11y-toolkit a11y-toolkit-mcp

Axcess — Design Accessibility Evaluation As a remote MCP server

Claude Code
claude mcp add --transport http axcess https://axcess-mcp-server.fly.dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Axcess — Design Accessibility Evaluation has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: A11Y Toolkit · What it can do: Axcess — Design Accessibility Evaluation · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built