Ext Ops Panel
Open dashboard
Comparison

gadgethumans-mcp vs dev.nexbid/discovery

gadgethumans-mcp is an MCP server published by gadgethumans-dev. Marketplaces we read that list it: 1 (npm registry (MCP servers)). dev.nexbid/discovery is an MCP server published by nexbid.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
Marketplacegadgethumans-mcpdev.nexbid/discovery
npm registry (MCP servers) Listed
Version: 1.2.4
Downloads/month (npm): 642
Downloads/week (npm): 134
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 0 (last published figure)
Not marked · First seen
Not listed
Official MCP Registry Removed on 2026-11-08
Version: 1.0.15
Downloads/month (npm): 642
Downloads/week (npm): 134
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 0 (last published figure)
Not marked · First seen
Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 0
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

gadgethumans-mcp vs dev.nexbid/discovery
Factgadgethumans-mcpdev.nexbid/discovery
Marketplaces that list it11
Stars (GitHub) (differs)0 (last published figure)0
Forks (GitHub) (differs)0 (last published figure)0
Last release (differs)2026-11-06Not published
Where it runs (differs)On your machine (gadgethumans-mcp)Remote server (mcp.nexbid.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/gadgethumans-dev/api-hubgithub.com/nexbid-dev/protocol-commerce
Changes in the last 7 days (differs)20 or more0
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 35 h ago returned HTTP 405

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

gadgethumans-mcp

In its own words, on npm registry (MCP servers):

MCP server for the GadgetHumans API: 226 tools in one install (ocr, ens, token safety, translate, sentiment, whois, hash, geocode, dns, weather, vat, timezone, ip, search, and a free x402 catalogue search ranked by measured 30-day call volume). Prepaid cr

dev.nexbid/discovery

In its own words, on Official MCP Registry:

Search and discover advertiser products through an open marketplace for AI agents.

How to run each

gadgethumans-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

dev.nexbid/discovery As a remote MCP server

Claude Code
claude mcp add --transport http discovery https://mcp.nexbid.dev/mcp

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

Only dev.nexbid/discovery 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: gadgethumans-mcp · What it can do: dev.nexbid/discovery · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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