Ext Ops Panel
Open dashboard
Comparison

recursive-research vs Hyperresearch

recursive-research is a plugin bundle for AI coding tools published by Anjos2. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Hyperresearch is an MCP server published by hyperresearch.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacerecursive-researchHyperresearch
Claude Code: claude-plugins-community Listed
Version: 15ed326
Forks (GitHub): 4
Stars (GitHub): 48
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

recursive-research vs Hyperresearch
Factrecursive-researchHyperresearch
Marketplaces that list it11
Stars (GitHub) (differs)48No figure on GitHub
Forks (GitHub) (differs)4No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.hyperresearch.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/anjos2/recursive-researchNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 42 h 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

recursive-research

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

Recursive research up to PhD level across any domain (science, tech, business, arts, humanities). Source tiering (Tier 1/2/3/rejected), WDM + Munger inversion for autonomous decisions, and disk checkpointing to survive context compaction. Works with web sources, local files, or mixed mode — interactive setup asks for seed, priority/excluded sources, and cycle cap before starting.

Hyperresearch

In its own words, on Official MCP Registry:

Start cited deep-research runs, read reports, search your source vault, and verify citations.

How to run each

recursive-research As a Claude Code plugin

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

Hyperresearch As a remote MCP server

Claude Code
claude mcp add --transport http hyperresearch https://mcp.hyperresearch.ai/mcp

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

Only Hyperresearch 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: recursive-research · What it can do: Hyperresearch · 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