Ext Ops Panel
Open dashboard
Comparison

io.github.HomenShum/nodebench vs x402 Bazaar Rank

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). x402 Bazaar Rank is an MCP server published by mike-lblc. 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.HomenShum/nodebenchx402 Bazaar Rank
Official MCP Registry Listed
Version: 2.31.2
Downloads/month (npm): 433
Downloads/week (npm): 52
Forks (GitHub): 3
Stars (GitHub): 15
Not marked · First seen
Listed
Version: 0.1.2
No figure published
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 x402 Bazaar Rank
Factio.github.HomenShum/nodebenchx402 Bazaar Rank
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)15No figure on GitHub
Forks (GitHub) (differs)3No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (nodebench-mcp)Remote server (x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/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/mike-lblc/project-zero
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

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.

x402 Bazaar Rank

In its own words, on Official MCP Registry:

Ranked search over 15k+ live x402 services by real 30-day usage; free top-5, paid depth via x402.

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

x402 Bazaar Rank As a remote MCP server

Claude Code
claude mcp add --transport http x402-bazaar-rank https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp

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

Only x402 Bazaar Rank has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of io.github.HomenShum/nodebench 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: io.github.HomenShum/nodebench · What it can do: x402 Bazaar Rank · 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