Ext Ops Panel
Open dashboard
Comparison

agentic-tests vs Hermoso

agentic-tests is a plugin bundle for AI coding tools published by Jin-Guo Liu. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Hermoso is an MCP server published by hermoso-ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. 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
Marketplaceagentic-testsHermoso
Community marketplace giggleliu/agentic-tests Listed
Version: 0.1.0
Forks (GitHub): 3
Stars (GitHub): 12
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.435
Downloads/month (npm): 13 689
Downloads/week (npm): 632
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.1.435
Downloads/month (npm): 13 689
Downloads/week (npm): 632
Forks (GitHub): 0
Stars (GitHub): 2
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

agentic-tests vs Hermoso
Factagentic-testsHermoso
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)12 (better)2 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last release (differs)Not published2026-10-20
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)4Not a bundle
LicenceMITMIT
Repository (differs)github.com/giggleliu/agentic-testsgithub.com/hermoso-ai/hermoso
Changes in the last 7 days (differs)220 or more
First seen (differs)2026-10-192026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago, requires a key

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

agentic-tests

In its own words, on Community GitHub marketplaces:

Agent-driven testing toolkit: test skills via role-play and test project features via simulated users

Hermoso

In its own words, on Official MCP Registry:

AI marketing agent and AI ad generator: 922 tools, usable alone. No markup on models.

How to run each

agentic-tests As a Claude Code plugin

Claude Code
/plugin marketplace add giggleliu/agentic-tests
/plugin install agentic-tests@agentic-tests

Hermoso

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: HERMOSO_TOKEN (secret)

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

Only Hermoso 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

The marketplaces of agentic-tests publish no settings it asks for, so we do not compare settings.

What it can do: agentic-tests · What it can do: Hermoso · 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. Package data comes from the public npm registry (registry.npmjs.org). 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