Ext Ops Panel
Open dashboard
Comparison

formstack-webhooks vs formcarry

formstack-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). formcarry is an MCP server published by formcarry.com. 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

Where each is published
Marketplaceformstack-webhooksformcarry
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.1
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

formstack-webhooks vs formcarry
Factformstack-webhooksformcarry
Marketplaces that list it11
Stars (GitHub) (differs)92No figure on GitHub
Forks (GitHub) (differs)16No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.formcarry.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/hookdeck/webhook-skillsNot stated
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 4 days ago, requires a key

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

formstack-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Formstack Forms webhooks (the "WebHook" submit action, aka "Send Data to an External URL"). Use when setting up a Formstack form submission webhook handler, debugging X-FS-Signature HMAC verification, handling application/x-www-form-urlencoded or JSON submission payloads, or working out which fields a form will POST. Formstack has NO event types — a WebHook fires on exactly one thing, a form submission — so handlers key off FormID, not an event name.

formcarry

In its own words, on Official MCP Registry:

Set up form handling for your site (email alerts, auto replies, webhooks) and query submissions.

How to run each

formstack-webhooks As a Claude Code plugin

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

formcarry As a remote MCP server

Claude Code
claude mcp add --transport http formcarry https://mcp.formcarry.com/mcp

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

Only formcarry 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: formstack-webhooks · What it can do: formcarry · 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