Ext Ops Panel
Open dashboard
Comparison

io.github.Saidiibrahim/search-papers vs ScholarFetch

io.github.Saidiibrahim/search-papers is an MCP server published by Saidiibrahim. Marketplaces we read that list it: 1 (Official MCP Registry). ScholarFetch is an MCP server published by laibniz. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceio.github.Saidiibrahim/search-papersScholarFetch
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (npm): 119
Downloads/week (npm): 7
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 1
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

io.github.Saidiibrahim/search-papers vs ScholarFetch
Factio.github.Saidiibrahim/search-papersScholarFetch
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (search-papers)Remote server (laibniz-scholarfetch-web.hf.space/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/saidiibrahim/search-papersgithub.com/laibniz/scholarfetch
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 39 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

io.github.Saidiibrahim/search-papers

In its own words, on Official MCP Registry:

An MCP server to search papers from arXiv

ScholarFetch

In its own words, on Official MCP Registry:

Multi-engine scholarly research server for search, traversal, full text, and reading lists.

How to run each

io.github.Saidiibrahim/search-papers As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio search-papers -- npx -y search-papers

ScholarFetch As a remote MCP server

Claude Code
claude mcp add --transport http scholarfetch https://laibniz-scholarfetch-web.hf.space/mcp/

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

Only ScholarFetch 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: io.github.Saidiibrahim/search-papers · What it can do: ScholarFetch · Compare two other plugins

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