Lazynext Accessibility Checker vs Chrome DevTools MCP
Lazynext Accessibility Checker is an MCP server published by lazynext.com. Marketplaces we read that list it: 1 (Official MCP Registry). Chrome DevTools MCP is an MCP server published by ChromeDevTools. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Copilot CLI: github/awesome-copilot, Community GitHub marketplaces, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-20. 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
| Marketplace |  Lazynext Accessibility Checker |  Chrome DevTools MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.11.0 Downloads/month (npm): 7 942 550 Downloads/week (npm): 1 737 496 Forks (GitHub): 6 984 Stars (GitHub): 53 815 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 1.11.0 Forks (GitHub): 6 984 Stars (GitHub): 53 815 Not marked · First seen |
| Copilot CLI: github/awesome-copilot | Not listed | Listed Version: 1.0.1 Forks (GitHub): 6 984 Stars (GitHub): 53 815 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.6.0 Forks (GitHub): 6 984 Stars (GitHub): 53 815 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
| Fact | Lazynext Accessibility Checker | Chrome DevTools MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 5 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 53 815 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 6 984 (better) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Remote server (api.lazynext.com/mcp) | On your machine (chrome-devtools-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 8 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/lazynext-ai/accessibility-checker | github.com/chromedevtools/chrome-devtools-mcp |
| Changes in the last 7 days (differs) | 0 | 9 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago | no 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
Lazynext Accessibility Checker
Scan URLs or HTML for WCAG 2.2 violations. 75-rule manifest, weighted score, shareable reports.
Chrome DevTools MCP
MCP server for Chrome DevTools
How to run each
Lazynext Accessibility Checker As a remote MCP server
claude mcp add --transport http accessibility-checker https://api.lazynext.com/mcpChrome DevTools MCP As a local MCP server: npm package
claude mcp add --transport stdio chrome-devtools-mcp -- npx -y chrome-devtools-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Lazynext Accessibility Checker 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: Lazynext Accessibility Checker · What it can do: Chrome DevTools MCP · 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-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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.