Ext Ops Panel
Open dashboard
Comparison

io.github.HomenShum/nodebench vs io.github.rpconroy/gdex-mcp

io.github.HomenShum/nodebench is an MCP server published by HomenShum. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). io.github.rpconroy/gdex-mcp is an MCP server published by rpconroy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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.HomenShum/nodebenchio.github.rpconroy/gdex-mcp
Official MCP Registry Listed
Version: 2.31.2
Downloads/month (npm): 594
Downloads/week (npm): 119
Forks (GitHub): 3
Stars (GitHub): 15
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 9d6bf19
Forks (GitHub): 3
Stars (GitHub): 15
Not marked · First seen
Not listed

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.HomenShum/nodebench vs io.github.rpconroy/gdex-mcp
Factio.github.HomenShum/nodebenchio.github.rpconroy/gdex-mcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)15 (better)0 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (nodebench-mcp)Remote server (gdex-mcp.k8s.ucar.edu/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)5Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/homenshum/nodebench-aigithub.com/ncar/gdex-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 47 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.HomenShum/nodebench

In its own words, on Official MCP Registry:

260 MCP tools across 49 domains. AI Flywheel, quality gates, research, web scraping.

io.github.rpconroy/gdex-mcp

In its own words, on Official MCP Registry:

MCP server for the GDEX (Geoscience Data Exchange) data portal: datasets, files, metrics, subsetting

How to run each

io.github.HomenShum/nodebench As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio nodebench -- npx -y nodebench-mcp

io.github.rpconroy/gdex-mcp As a remote MCP server

Claude Code
claude mcp add --transport http gdex-mcp https://gdex-mcp.k8s.ucar.edu/mcp

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

Only io.github.rpconroy/gdex-mcp 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.HomenShum/nodebench · What it can do: io.github.rpconroy/gdex-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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