Ext Ops Panel
Open dashboard
Comparison

testdino vs Argus Testing — Autonomous QA MCP

testdino is a plugin bundle for AI coding tools published by TestDino. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Argus Testing — Autonomous QA MCP is an MCP server published by chriswu727. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplacetestdinoArgus Testing — Autonomous QA MCP
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 343
Stars (GitHub): 4 748
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.0
Downloads/month (PyPI): 184
Downloads/week (PyPI): 73
Forks (GitHub): 0
Stars (GitHub): 3
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

testdino vs Argus Testing — Autonomous QA MCP
FacttestdinoArgus Testing — Autonomous QA MCP
Marketplaces that list it11
Stars (GitHub) (differs)4 748 (better)3 (worse)
Forks (GitHub) (differs)343 (better)0 (worse)
Last release (differs)Not published2026-10-19
Where it runs (differs)Remote server (mcp.testdino.com)On your machine (argus-testing)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)8Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/anthropics/claude-plugins-communitygithub.com/chriswu727/argus
Changes in the last 7 days (differs)01
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 3 days agono 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

testdino

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

Use TestDino inside Claude Code through the hosted remote MCP server to inspect test runs, debug failing test cases, manage manual tests, and run TestDino audits.

Argus Testing — Autonomous QA MCP

In its own words, on Official MCP Registry:

Autonomous QA MCP for web and macOS that tests like a real engineer, finds bugs, and verifies them.

How to run each

testdino As a Claude Code plugin

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

Argus Testing — Autonomous QA MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio argus -- uvx argus-testing

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

Only testdino 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: testdino · What it can do: Argus Testing — Autonomous QA MCP · 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