whatnot-webhooks vs Post & Present
whatnot-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Post & Present is an MCP server published by postandpresent.co.uk. 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
| Marketplace |  Post & Present | |
|---|---|---|
| Community marketplace hookdeck/webhook-skills | Listed Version: not stated Forks (GitHub): 17 Stars (GitHub): 99 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | Post & Present |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 99 | No figure on GitHub |
| Forks (GitHub) (differs) | 17 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (postandpresent.co.uk/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hookdeck/webhook-skills | github.com/tobinbc/post-and-present |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-21 | 2026-10-26 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 45 h ago returned HTTP 406 |
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 developer app that handles topics like orders.created, orders.updated, shows.started, shows.ended, shipments.label_generated or products.updated, when debugging webhook-id / webhook-timestamp / webhook-signature (Standard Webhooks) verification with a wn_wh_ secret, or when migrating off the deprecated X-Whatnot-Webhook-Signature scheme. Whatnot signs base64 HMAC-SHA256 over `{webhook-id}.{webhook-timestamp}.{raw body}`, keyed with the base64-decoded secret after stripping `wn_wh_`, with a 5-minute timestamp tolerance. Route on the body's `type`; the payload is under `data`.
Post & Present
Buy and send UK digital gift cards with a message from chat.
How to run each
whatnot-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install whatnot-webhooks@webhook-skillsPost & Present As a remote MCP server
claude mcp add --transport http gifts https://postandpresent.co.uk/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Post & Present 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: whatnot-webhooks · What it can do: Post & Present · 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.