Ext Ops Panel
Open dashboard
Comparison

com.nexaaly/a11y-check vs io.github.First-CH/tools-mcp

com.nexaaly/a11y-check is an MCP server published by nexaaly.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.First-CH/tools-mcp is an MCP server published by First-CH. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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
Marketplacecom.nexaaly/a11y-checkio.github.First-CH/tools-mcp
Official MCP Registry Listed, marked deprecated
Version: 1.2.0
No figure published
Not marked · First seen
Listed
Version: 0.39.0
Downloads/month (npm): 1 742
Downloads/week (npm): 119
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.39.0
Downloads/month (npm): 1 742
Downloads/week (npm): 119
Forks (GitHub): 0
Stars (GitHub): 0
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

com.nexaaly/a11y-check vs io.github.First-CH/tools-mcp
Factcom.nexaaly/a11y-checkio.github.First-CH/tools-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-29
Where it runs (differs)Remote server (nexaaly.com/mcp)On your machine (@first-ch/tools-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/first-ch/firstch-tools-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-26no remote endpoint we check

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

com.nexaaly/a11y-check

In its own words, on Official MCP Registry:

Real-browser WCAG audit that also finds keyboard-inoperable controls axe-core misses, with fixes.

io.github.First-CH/tools-mcp

In its own words, on Official MCP Registry:

Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more

How to run each

com.nexaaly/a11y-check As a remote MCP server

Claude Code
claude mcp add --transport http a11y-check https://nexaaly.com/mcp

io.github.First-CH/tools-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio tools-mcp -- npx -y @first-ch/tools-mcp

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

Only com.nexaaly/a11y-check 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

The marketplaces of com.nexaaly/a11y-check publish no settings it asks for, so we do not compare settings.

What it can do: com.nexaaly/a11y-check · What it can do: io.github.First-CH/tools-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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