Ext Ops Panel
Open dashboard
Comparison

superRA vs Scholar Sidekick

superRA is a plugin bundle for AI coding tools published by Julie Zhiyu Fu. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Scholar Sidekick is an MCP server published by mlava. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). 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
MarketplacesuperRAScholar Sidekick
Community marketplace fuzhiyu/superra Listed
Version: 0.5.0
Forks (GitHub): 2
Stars (GitHub): 11
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.13
Downloads/month (npm): 983
Downloads/week (npm): 525
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.8.13
Downloads/month (npm): 983
Downloads/week (npm): 525
Forks (GitHub): 0
Stars (GitHub): 11
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

superRA vs Scholar Sidekick
FactsuperRAScholar Sidekick
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub)1111
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)Not published2026-10-16
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 forNot publishedNot published
Hooks it runs (differs)11Not published
Parts of the bundle (differs)252
LicenceMITMIT
Repository (differs)github.com/fuzhiyu/superragithub.com/mlava/scholar-sidekick-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-192026-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

superRA

In its own words, on Community GitHub marketplaces:

Disciplined AI Research Assistant for economists: plan-implement-integrate workflow with implementer–reviewer pair, data-analysis discipline, and drift-test-verified integration.

Scholar Sidekick

In its own words, on Official MCP Registry:

Catch AI-fabricated citations (real DOI + fake title). Retraction, open-access, 10,000+ CSL styles.

How to run each

superRA As a Claude Code plugin

Claude Code
/plugin marketplace add fuzhiyu/superra
/plugin install superRA@superRA

Scholar Sidekick As a remote MCP server

Claude Code
claude mcp add --transport http scholar-sidekick-mcp https://scholar-sidekick.com/api/mcp

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

Only Scholar Sidekick has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of superRA nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: superRA · What it can do: Scholar Sidekick · 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