Ext Ops Panel
Open dashboard
Comparison

auto-research vs xpay Content Research

auto-research is a plugin bundle for AI coding tools published by gyoz-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). xpay Content Research is an MCP server published by xpaysh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
Marketplaceauto-researchxpay Content Research
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

auto-research vs xpay Content Research
Factauto-researchxpay Content Research
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (content.mcp.xpay.sh/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/gyoz-ai/auto-researchgithub.com/xpaysh/mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

auto-research

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

Autonomous skill improvement through parallel research agents. Inspired by Karpathy's autoresearch methodology, it spawns 5 parallel agents (domain expert, quality auditor, competitive analyst, gap analyst, tech scout), synthesizes findings into ranked proposals, then runs an iterative keep/discard experiment loop to improve any Claude Code skill. Scores skills on 7 quality dimensions and only keeps changes that genuinely improve the composite score.

xpay Content Research

In its own words, on Official MCP Registry:

40+ content research tools. Perplexity, Tavily, Semantic Scholar, FLUX, Ideogram, Recraft.

How to run each

auto-research As a Claude Code plugin

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

xpay Content Research

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

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

Only xpay Content Research 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: auto-research · What it can do: xpay Content Research · 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