Ext Ops Panel
Open dashboard
Comparison

Iaptic vs bridge-api-webhooks

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

Where each is published
MarketplaceIapticbridge-api-webhooks
Docker MCP Catalog Listed
Version: sha256:7f86e3becb71
Forks (GitHub): 6
Pulls (Docker Hub): 16 401
Stars (Docker Hub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Community marketplace hookdeck/webhook-skills Not listed Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 92
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

Iaptic vs bridge-api-webhooks
FactIapticbridge-api-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)9 (worse)92 (better)
Pulls (Docker Hub) (differs)16 401No figure on Docker Hub
Forks (GitHub) (differs)6 (worse)16 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/iaptic)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)17Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceMITMIT
Repository (differs)github.com/iaptic/mcp-server-iapticgithub.com/hookdeck/webhook-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-21

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

Iaptic

In its own words, on Docker MCP Catalog:

Model Context Protocol server for interacting with iaptic.

bridge-api-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Bridge API (bridgeapi.io) webhooks, the open-banking aggregator by Bridge/Bankin' (NOT bridge.xyz). Use when setting up Bridge API webhook handlers, debugging BridgeApi-Signature HMAC-SHA256 verification, or handling events like item.created, item.refreshed, item.account.updated, payment.transaction.created, and user.deleted.

How to run each

Iaptic As a local MCP server: Docker image

Claude Code
claude mcp add --env "IAPTIC_API_KEY=<YOUR_IAPTIC_API_KEY>" --transport stdio iaptic -- docker run -i --rm -e IAPTIC_API_KEY mcp/iaptic

Requires: IAPTIC_API_KEY (secret)

bridge-api-webhooks As a Claude Code plugin

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

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

Tools each declares

The marketplaces of bridge-api-webhooks publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of bridge-api-webhooks publish no settings it asks for, so we do not compare settings.

What it can do: Iaptic · What it can do: bridge-api-webhooks · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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