Ext Ops Panel
Open dashboard
Comparison

Droplinked vs io.github.DeviceIngineering/wb-mcp-server

Droplinked is a plugin bundle for AI coding tools published by droplinked. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.DeviceIngineering/wb-mcp-server is an MCP server published by DeviceIngineering. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-15. 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
MarketplaceDroplinkedio.github.DeviceIngineering/wb-mcp-server
Community marketplace hashgraph-online/awesome-codex-plugins Listed
Version: 0.1.0
Forks (GitHub): 491
Stars (GitHub): 1 576
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.6.1
Downloads/month (PyPI): 1 001
Downloads/week (PyPI): 757
Forks (GitHub): 5
Stars (GitHub): 9
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 2.6.1
Downloads/month (PyPI): 1 001
Downloads/week (PyPI): 757
Forks (GitHub): 5
Stars (GitHub): 9
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

Droplinked vs io.github.DeviceIngineering/wb-mcp-server
FactDroplinkedio.github.DeviceIngineering/wb-mcp-server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 576 (better)9 (worse)
Forks (GitHub) (differs)491 (better)5 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.droplinked.com/mcp)On your machine (wb-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/hashgraph-online/awesome-codex-pluginsgithub.com/deviceingineering/wb-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-11-142026-10-11
Endpoint at the last check (differs)Responded 23 h agono remote endpoint we check

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

Droplinked

In its own words, on Community GitHub marketplaces:

Verified-inventory agentic commerce over a hosted MCP server, with merchant and product discovery, agent-initiated checkout, and onchain brand, credit-risk, and repayment attestations.

io.github.DeviceIngineering/wb-mcp-server

In its own words, on Official MCP Registry:

Wildberries Seller API, 197 tools; responses measured and trimmed: 770k to 75k tokens.

How to run each

Droplinked As a Codex plugin

Codex
codex plugin marketplace add hashgraph-online/awesome-codex-plugins

io.github.DeviceIngineering/wb-mcp-server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "WB_API_TOKEN=<YOUR_WB_API_TOKEN>" --transport stdio wb-mcp-server -- uvx wb-mcp-server

Requires: WB_API_TOKEN (secret)

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

Only Droplinked 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

The marketplaces of Droplinked publish no settings it asks for, so we do not compare settings.

What it can do: Droplinked · What it can do: io.github.DeviceIngineering/wb-mcp-server · 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 Python Package Index (pypi.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