Ext Ops Panel
Open dashboard
Comparison

airwallex-webhooks vs io.github.codespar/mcp-airwallex

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

Where each is published
Marketplaceairwallex-webhooksio.github.codespar/mcp-airwallex
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: 0.2.2
Downloads/month (npm): 112
Downloads/week (npm): 25
Forks (GitHub): 51
Stars (GitHub): 274
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

airwallex-webhooks vs io.github.codespar/mcp-airwallex
Factairwallex-webhooksio.github.codespar/mcp-airwallex
Marketplaces that list it11
Stars (GitHub) (differs)92 (worse)274 (better)
Forks (GitHub) (differs)16 (worse)51 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@codespar/mcp-airwallex)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/codespar/mcp-dev-latam
Changes in the last 7 days (differs)20
First seen (differs)2026-10-212026-10-11

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

airwallex-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Airwallex webhooks. Use when setting up Airwallex webhook handlers, debugging x-signature / x-timestamp signature verification, or handling payment events like payment_intent.succeeded, payment_attempt.paid, refund.settled, payment_consent.verified, or payment_dispute.requires_response.

io.github.codespar/mcp-airwallex

In its own words, on Official MCP Registry:

MCP server for Airwallex — cross-border collection + payouts, global accounts, FX, transfers

How to run each

airwallex-webhooks As a Claude Code plugin

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

io.github.codespar/mcp-airwallex As a local MCP server: npm package

Claude Code
claude mcp add --env "AIRWALLEX_API_KEY=<YOUR_AIRWALLEX_API_KEY>" --env "AIRWALLEX_CLIENT_ID=<YOUR_AIRWALLEX_CLIENT_ID>" --transport stdio mcp-airwallex -- npx -y @codespar/mcp-airwallex

Requires: AIRWALLEX_API_KEY (secret), AIRWALLEX_CLIENT_ID

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

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 airwallex-webhooks publish no settings it asks for, so we do not compare settings.

What it can do: airwallex-webhooks · What it can do: io.github.codespar/mcp-airwallex · 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