Ext Ops Panel
Open dashboard
Comparison

scout vs io.github.copus-io/copus

scout is a plugin bundle for AI coding tools published by shidoyu. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.copus-io/copus is an MCP server published by copus-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacescoutio.github.copus-io/copus
Claude Code: claude-plugins-community Listed
Version: 2.5.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (npm): 154
Downloads/week (npm): 35
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

scout vs io.github.copus-io/copus
Factscoutio.github.copus-io/copus
Marketplaces that list it11
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.exa.ai/mcp)On your machine (copus-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)6Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/shidoyu/scoutgithub.com/copus-io/copus-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded less than an hour 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

scout

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

Web search and content fetching with privacy-aware tool selection. Turns vague questions into optimized multi-engine queries, evaluates result quality, and re-searches when needed. Includes HyDE semantic search via Exa and automatic privacy classification for URL fetching.

io.github.copus-io/copus

In its own words, on Official MCP Registry:

Search human-curated content recommendations from Copus - The Internet Treasure Map

How to run each

scout As a Claude Code plugin

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

io.github.copus-io/copus As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio copus -- npx -y copus-mcp-server

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

Only scout 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: scout · What it can do: io.github.copus-io/copus · 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