webhook-skills vs app.vercel.stripecheckup/stripecheckup
webhook-skills is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). app.vercel.stripecheckup/stripecheckup is an MCP server published by stripecheckup.vercel.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 | ||
|---|---|---|
| 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: 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 | webhook-skills | app.vercel.stripecheckup/stripecheckup |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 92 | No figure on GitHub |
| Forks (GitHub) (differs) | 16 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (stripecheckup.vercel.app/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 219 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hookdeck/webhook-skills | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-21 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days 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
webhook-skills
Bundle of all webhook integration skills in this repo: 214 provider skills (Stripe, Shopify, GitHub, and 211 others) for verifying signatures and handling provider-specific events, framework-agnostic webhook handler patterns covering idempotency, error handling and retries, three Hookdeck infrastructure skills for the Event Gateway and Outpost, and a webhook DX audit skill for scoring how a platform sends outbound webhooks. Each provider skill includes Express, Next.js, and FastAPI examples. Install this plugin to get all 219 skills; install individual `<name>-webhooks@webhook-skills` plugins for narrower per-provider use.
app.vercel.stripecheckup/stripecheckup
Scan pasted Stripe webhook/checkout code for common integration bugs.
How to run each
webhook-skills As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install webhook-skills@webhook-skillsapp.vercel.stripecheckup/stripecheckup As a remote MCP server
claude mcp add --transport http stripecheckup https://stripecheckup.vercel.app/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only app.vercel.stripecheckup/stripecheckup 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: webhook-skills · What it can do: app.vercel.stripecheckup/stripecheckup · 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.