Ext Ops Panel
Open dashboard
Comparison

agentiqa vs UI Verify

agentiqa is a plugin bundle for AI coding tools published by Agentiqa. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). UI Verify is an MCP server published by igrlk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceagentiqaUI Verify
Claude Code: claude-plugins-community Listed
Version: 0.5.3
Forks (GitHub): 2
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 1
Stars (GitHub): 23
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

agentiqa vs UI Verify
FactagentiqaUI Verify
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)23 (better)
Forks (GitHub) (differs)2 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (uiverify.ai/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/agentiqa/agentiqa-plugingithub.com/uiverify/uiverify
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

agentiqa

In its own words, on Claude Code: claude-plugins-community:

AI-powered QA testing agent for web and mobile apps. Agentiqa explores your app visually - like a real user with fresh eyes - and reports bugs with severity, confidence scores, and step-by-step reproduction instructions. No selectors, no scripts, no test code to maintain. Just describe what to test in plain English. Supports web (any URL or localhost), Android (emulator/device), and iOS (simulator/device). Finds visual bugs, logical errors, UX issues, and accessibility problems that unit tests and linters miss.

UI Verify

In its own words, on Official MCP Registry:

MCP server for visual regression testing: triage a PR's UI diffs from your coding agent.

How to run each

agentiqa As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agentiqa@claude-community

UI Verify As a remote MCP server

Claude Code
claude mcp add --transport http uiverify https://uiverify.ai/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

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: agentiqa · What it can do: UI Verify · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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