Ext Ops Panel
Open dashboard
Comparison

qonto-webhooks vs io.github.paivapiovesan/next-finance

qonto-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.paivapiovesan/next-finance is an MCP server published by paivapiovesan. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-14. 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
Marketplaceqonto-webhooksio.github.paivapiovesan/next-finance
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.9.163
Downloads/month (npm): 3 977
Downloads/week (npm): 2 292
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.9.231
Downloads/month (npm): 3 977
Downloads/week (npm): 2 292
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

qonto-webhooks vs io.github.paivapiovesan/next-finance
Factqonto-webhooksio.github.paivapiovesan/next-finance
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)101No figure on GitHub
Forks (GitHub) (differs)16No figure on GitHub
Last release (differs)Not published2026-11-12
Where it runs (differs)Installs as a plugin bundleOn your machine (next-finance-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceMITMIT
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/paivapiovesan/next-finance-mcp
Changes in the last 7 days (differs)04
First seen (differs)2026-11-062026-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

qonto-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Qonto webhooks. Use when setting up Qonto Business API webhook subscriptions, debugging X-Qonto-Signature verification, or handling events like v1/transactions, v1/cards, and v1/transfers.

io.github.paivapiovesan/next-finance

In its own words, on Official MCP Registry:

MCP Server for NEXT Finance ERP (finance.net.br) — browser login, wallets, accounts, transactions.

How to run each

qonto-webhooks As a Claude Code plugin

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

io.github.paivapiovesan/next-finance As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio next-finance -- npx -y next-finance-mcp

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

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

What it can do: qonto-webhooks · What it can do: io.github.paivapiovesan/next-finance · 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. Package data comes from the public npm registry (registry.npmjs.org). 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