Ext Ops Panel
Open dashboard
Comparison

frontend-visual-qa vs Axcess — Design Accessibility Evaluation

frontend-visual-qa is a plugin bundle for AI coding tools published by daymade. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-11-11. 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
Marketplacefrontend-visual-qaAxcess — Design Accessibility Evaluation
Community marketplace daymade/claude-code-skills Listed
Version: 1.21.43
Forks (GitHub): 235
Stars (GitHub): 1 524
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

frontend-visual-qa vs Axcess — Design Accessibility Evaluation
Factfrontend-visual-qaAxcess — Design Accessibility Evaluation
Marketplaces that list it11
Stars (GitHub) (differs)1 524No figure on GitHub
Forks (GitHub) (differs)235No figure on GitHub
Last release (differs)2026-11-11Not published
Where it runs (differs)Installs as a plugin bundleRemote server (axcess-mcp-server.fly.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/daymade/claude-code-skillsNot stated
Changes in the last 7 days (differs)40
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 25 h 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

frontend-visual-qa

In its own words, on Community GitHub marketplaces:

Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI implementation to find typography, overflow, responsive, routing, data-viz, browser-output, or native-shell defects, or to compare a render against a reference. Not for greenfield UI design (use ui-designer) or QA-program setup (use qa-expert).

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

frontend-visual-qa As a Claude Code plugin

Claude Code
/plugin marketplace add daymade/claude-code-skills
/plugin install frontend-visual-qa@daymade-skills

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: frontend-visual-qa · What it can do: Axcess — Design Accessibility Evaluation · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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