Ext Ops Panel
Open dashboard
Comparison

sendoso-webhooks vs io.github.yaotsakpo/inbin

sendoso-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.yaotsakpo/inbin is an MCP server published by yaotsakpo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacesendoso-webhooksio.github.yaotsakpo/inbin
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 94
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 106
Downloads/week (npm): 18
Forks (GitHub): 0
Stars (GitHub): 1
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

sendoso-webhooks vs io.github.yaotsakpo/inbin
Factsendoso-webhooksio.github.yaotsakpo/inbin
Marketplaces that list it11
Stars (GitHub) (differs)94 (better)1 (worse)
Forks (GitHub) (differs)16 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.inbin.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/yaotsakpo/inbin-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-212026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 15 h 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

sendoso-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Sendoso webhooks for corporate gifting and direct mail send status updates. Use when enabling Sendoso webhooks, subscribing an endpoint in the Sendoso webhooks portal (Svix), debugging Svix signature verification (svix-id, svix-timestamp, svix-signature, whsec_ secret), allowlisting Sendoso webhook IPs, or handling send status events like send.delivered, send.shipped, send.redeemed, send.opened, send.bounced, send.undeliverable and send.failed.

io.github.yaotsakpo/inbin

In its own words, on Official MCP Registry:

Query Inbin's parsed email events (newsletters, invoices, alerts) as typed JSON tools.

How to run each

sendoso-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install sendoso-webhooks@webhook-skills

io.github.yaotsakpo/inbin As a remote MCP server

Claude Code
claude mcp add --transport http inbin https://api.inbin.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: INBIN_API_KEY (secret), Authorization header

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

Only io.github.yaotsakpo/inbin 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 sendoso-webhooks publish no settings it asks for, so we do not compare settings.

What it can do: sendoso-webhooks · What it can do: io.github.yaotsakpo/inbin · 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.

Where the data comes from: how the catalog is built