ui-review vs UX-Auditor-Pro
ui-review is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
ui-review is a plugin bundle for AI coding tools published by cdmx-in. No marketplace we read lists it any more. UX-Auditor-Pro is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace cdmx-in/ui-review | Removed on 2026-10-16 Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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
| Fact | ui-reviewno longer listed · | UX-Auditor-Pro |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (ux-auditor-pro-mcp.vercel.app/api/mcp) |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cdmx-in/ui-review | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 402 (3 days ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of ui-review
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Run accessibility, contrast, and design token audits and file QA issues from your AI coding tool.
-
Audit, spec, and verify production-grade experiences for humans and agents alike.
-
Read visual design reviews from live web pages: comments, CSS selectors, styles, console errors.
-
Give Claude Code the ability to see running web applications. Visual Eyes captures screenshots via Playwright, lets Claude analyze the UI visually, auto-fix layout bugs, and run…
-
Skills for auditing and optimizing web quality (Performance, Accessibility, SEO, Core Web Vitals, Best Practices)
-
Check web pages for responsive design problems and screenshot them on phone, tablet and desktop.
What each says it does
ui-review
Automated UI/UX review via agent-browser: overflow, wrapping, responsiveness across breakpoints, with baseline/diff regression mode.
UX-Auditor-Pro
Visual UI/UX scanner auditing websites for heuristic compliance.
How to run each
ui-review
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
UX-Auditor-Pro As a remote MCP server
claude mcp add --transport sse ux-auditor-pro https://ux-auditor-pro-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only UX-Auditor-Pro 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: ui-review · What it can do: UX-Auditor-Pro · 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.