whatnot-webhooks vs io.github.DeviceIngineering/wb-mcp-server
whatnot-webhooks is a plugin bundle for AI coding tools published by Hookdeck. 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: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
| Marketplace |  io.github.DeviceIngineering/wb-mcp-server | |
|---|---|---|
| Community marketplace hookdeck/webhook-skills | Listed Version: not stated Forks (GitHub): 16 Stars (GitHub): 92 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.6.1 Downloads/month (PyPI): 1 001 Downloads/week (PyPI): 293 Forks (GitHub): 5 Stars (GitHub): 4 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
| Fact | whatnot-webhooks | io.github.DeviceIngineering/wb-mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 92 (better) | 4 (worse) |
| Forks (GitHub) (differs) | 16 (better) | 5 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (wb-mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hookdeck/webhook-skills | github.com/deviceingineering/wb-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-21 | 2026-10-11 |
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
whatnot-webhooks
Receive and verify Whatnot webhooks (whatnot.com — the live-shopping and livestream-auction marketplace). Use when building a Whatnot Seller API app that handles webhook topics like order/created, order/updated, product/sold, listing/created, livestream/stopped or bulk_operation/finished, or when debugging X-Whatnot-Webhook-Signature verification. Whatnot signs with HMAC-SHA256 over the RAW request body, lowercase hex, keyed with the app's webhook secret key (issued by a Whatnot representative). No timestamp, no prefix. The topic is in the JSON body (`topic`), the payload under `object`.
io.github.DeviceIngineering/wb-mcp-server
Wildberries Seller API, 197 tools; responses measured and trimmed: 770k to 75k tokens.
How to run each
whatnot-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install whatnot-webhooks@webhook-skillsio.github.DeviceIngineering/wb-mcp-server As a local MCP server: PyPI package
claude mcp add --env "WB_API_TOKEN=<YOUR_WB_API_TOKEN>" --transport stdio wb-mcp-server -- uvx wb-mcp-serverRequires: WB_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 whatnot-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: whatnot-webhooks · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.