Ext Ops Panel
Open dashboard
Comparison

com.nexaaly/a11y-check vs io.github.fastslack/e2e-runner

com.nexaaly/a11y-check is an MCP server published by nexaaly.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.fastslack/e2e-runner is an MCP server published by fastslack. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). 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.fastslack/e2e-runner
Official MCP Registry Listed, marked deprecated
Version: 1.2.0
No figure published
Not marked · First seen
Listed
Version: 1.3.0
Downloads/month (npm): 435
Downloads/week (npm): 333
Forks (GitHub): 1
Stars (GitHub): 7
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.5.1
Forks (GitHub): 1
Stars (GitHub): 7
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.fastslack/e2e-runner
Factcom.nexaaly/a11y-checkio.github.fastslack/e2e-runner
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub7
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (nexaaly.com/mcp)On your machine (@matware/e2e-runner)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle9
Licence (differs)Not statedApache-2.0
Repository (differs)Not statedgithub.com/fastslack/mtw-e2e-runner
Changes in the last 7 days00
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.fastslack/e2e-runner

In its own words, on Official MCP Registry:

JSON-driven E2E test runner with parallel Chrome pool execution and 16 MCP tools.

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.fastslack/e2e-runner As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio e2e-runner -- npx -y @matware/e2e-runner

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

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

What it can do: com.nexaaly/a11y-check · What it can do: io.github.fastslack/e2e-runner · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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