Ext Ops Panel
Open dashboard
Comparison

felloh-webhooks vs Boundra — Payment Approval Gateway for AI Agents

felloh-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Boundra — Payment Approval Gateway for AI Agents is an MCP server published by gobeyondfj-cmd. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacefelloh-webhooksBoundra — Payment Approval Gateway for AI Agents
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 101
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (PyPI): 0
Downloads/week (PyPI): 41
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

felloh-webhooks vs Boundra — Payment Approval Gateway for AI Agents
Factfelloh-webhooksBoundra — Payment Approval Gateway for AI Agents
Marketplaces that list it11
Stars (GitHub) (differs)101 (better)1 (worse)
Forks (GitHub) (differs)16 (better)0 (worse)
Last release (differs)Not published2026-11-10
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedstdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/gobeyondfj-cmd/boundra
Changes in the last 7 days (differs)21
First seen (differs)2026-11-062026-10-18
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 37 h ago returned HTTP 406

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

felloh-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Felloh webhooks. Use when setting up a Felloh webhook endpoint, debugging X-Signature HMAC-SHA256 verification, or handling transaction status, refund status, booking and user events for UK travel payments.

Boundra — Payment Approval Gateway for AI Agents

In its own words, on Official MCP Registry:

Policy decision point for agent payments — allow, ask, or veto before signing

How to run each

felloh-webhooks As a Claude Code plugin

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

Boundra — Payment Approval Gateway for AI Agents As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio boundra -- uvx boundra-mcp

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

Only Boundra — Payment Approval Gateway for AI Agents has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of felloh-webhooks nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: felloh-webhooks · What it can do: Boundra — Payment Approval Gateway for AI Agents · 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