Bitrefill vs tikkie-webhooks
Bitrefill is an MCP server published by bitrefill. Marketplaces we read that list it: 1 (Docker MCP Catalog). tikkie-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-25. 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7ff5cc499284 Forks (GitHub): 1 Pulls (Docker Hub): 39 627 Stars (Docker Hub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Community marketplace hookdeck/webhook-skills | Not listed | Listed Version: not stated Forks (GitHub): 16 Stars (GitHub): 94 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
| Fact | Bitrefill | tikkie-webhooks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 94 (better) |
| Pulls (Docker Hub) (differs) | 39 627 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 (worse) | 16 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/bitrefill) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bitrefill/bitrefill-mcp-server | github.com/hookdeck/webhook-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-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
Bitrefill
A Model Context Protocol Server connector for Bitrefill public API, to enable AI agents to search and shop on Bitrefill.
tikkie-webhooks
Receive Tikkie (ABN AMRO) API v2 notifications. Use when setting up a Tikkie payment request, refund or transaction bundle webhook handler, subscribing via POST /paymentrequestssubscription or /transactionssubscription, or asking how to verify a Tikkie webhook signature. Tikkie notifications are UNSIGNED (no signature header, no secret, no HMAC), so this skill teaches the subscriptionId check plus re-fetching the record from the Tikkie API, and dispatching on notificationType PAYMENT, REFUND and BUNDLE.
How to run each
Bitrefill As a local MCP server: Docker image
claude mcp add --env "BITREFILL_API_SECRET=<YOUR_BITREFILL_API_SECRET>" --transport stdio bitrefill -- docker run -i --rm -e BITREFILL_API_SECRET mcp/bitrefill
Requires: BITREFILL_API_SECRET (secret)
tikkie-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install tikkie-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 tikkie-webhooks publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of tikkie-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: Bitrefill · What it can do: tikkie-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.