Ext Ops Panel
Open dashboard
Comparison

content-analysis vs Scholar Sidekick

content-analysis is a plugin bundle for AI coding tools published by PeterMalmkjaer. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Scholar Sidekick is an MCP server published by mlava. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
Marketplacecontent-analysisScholar Sidekick
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 2
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.13
Downloads/month (npm): 660
Downloads/week (npm): 140
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

content-analysis vs Scholar Sidekick
Factcontent-analysisScholar Sidekick
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 (worse)11 (better)
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
Parts of the bundle22
Licence (differs)SEE LICENSEMIT
Repository (differs)github.com/petermalmkjaer/content-analysis-plugingithub.com/mlava/scholar-sidekick-mcp
Changes in the last 7 days (differs)05
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

content-analysis

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

Scientific content analysis for academic research. Supports the full workflow from research question to publication-ready output: codebook development, qualitative and quantitative coding, thematic analysis, and inter-coder reliability assessment. Follows established methodology from Krippendorff, Hsieh & Shannon, Mayring, and Braun & Clarke. Produces structured output files including coded data tables (.xlsx), theme summaries (.md), and reliability reports.

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

content-analysis As a Claude Code plugin

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

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