Ext Ops Panel
Open dashboard
Comparison

LiveVariant vs Stunt Double

LiveVariant is an MCP server published by livevariant. Marketplaces we read that list it: 1 (Official MCP Registry). Stunt Double is an MCP server published by stuntdouble.io. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). 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
MarketplaceLiveVariantStunt Double
Official MCP Registry Listed
Version: 0.1.5
Downloads/month (npm): 538
Downloads/week (npm): 62
Forks (GitHub): 2
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 1.15.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: db2886b
Forks (GitHub): 0
Stars (GitHub): 1
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

LiveVariant vs Stunt Double
FactLiveVariantStunt Double
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)Remote server (livevariant.com/mcp)Remote server (app.stuntdouble.io/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 2Not published
Parts of the bundle (differs)Not a bundle12
Licence (differs)Not statedMIT
Repository (differs)github.com/livevariant/livevariantgithub.com/stunt-double/stuntdouble-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 32 h agoResponded 5 days ago

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

LiveVariant

In its own words, on Official MCP Registry:

Build, inspect and read adaptive A/B tests. Config travels in the URL; no account or API key needed.

Stunt Double

In its own words, on Official MCP Registry:

Deploy AI user personas to validate user journeys at scale. Find UX friction before real users do.

How to run each

LiveVariant As a remote MCP server

Claude Code
claude mcp add --transport http livevariant https://livevariant.com/mcp

Requires: LIVEVARIANT_API_TOKEN (secret), LIVEVARIANT_ASSET_UPLOAD_TOKEN (secret)

Stunt Double As a remote MCP server

Claude Code
claude mcp add --transport http stunt-double https://app.stuntdouble.io/api/mcp

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

Both endpoints responded at the last daily 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 Stunt Double publish no settings it asks for, so we do not compare settings.

What it can do: LiveVariant · What it can do: Stunt Double · 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-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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