Ext Ops Panel
Open dashboard
Comparison

kabbo vs Scholar Sidekick

kabbo is a plugin bundle for AI coding tools published by Johan Fourie. 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-25. 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
MarketplacekabboScholar Sidekick
Community marketplace johanfourieza/econtools Listed
Version: 1.1.0
Forks (GitHub): 9
Stars (GitHub): 38
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

kabbo vs Scholar Sidekick
FactkabboScholar Sidekick
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)38 (better)11 (worse)
Forks (GitHub) (differs)9 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (jydnsbaztvmjkebhmoia.supabase.co/functions/v1/mcp-server)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)32
LicenceMITMIT
Repository (differs)github.com/johanfourieza/econtoolsgithub.com/mlava/scholar-sidekick-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-232026-10-11
Endpoint at the last check (differs)not checked yetResponded 4 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

kabbo

In its own words, on Community GitHub marketplaces:

Manage your academic publication pipeline from Claude Code — list, search, create, move, analyse, export, and track reminders via the Kabbo MCP server.

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

kabbo As a Claude Code plugin

Claude Code
/plugin marketplace add johanfourieza/econtools
/plugin install kabbo@econtools

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 kabbo 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: kabbo · 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