Ext Ops Panel
Open dashboard
Comparison

io.github.cammac-creator/ibanforge vs Openiban

io.github.cammac-creator/ibanforge is an MCP server published by cammac-creator. Marketplaces we read that list it: 1 (Official MCP Registry). Openiban is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
Marketplaceio.github.cammac-creator/ibanforgeOpeniban
Official MCP Registry Listed
Version: 1.9.0
Downloads/month (npm): 626
Downloads/week (npm): 200
Forks (GitHub): 4
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.cammac-creator/ibanforge vs Openiban
Factio.github.cammac-creator/ibanforgeOpeniban
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last release (differs)Not published2026-11-04
Where it runs (differs)Remote server (api.ibanforge.com/mcp)Remote server (gateway.pipeworx.io/openiban/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/cammac-creator/ibanforgegithub.com/pipeworx-io/mcp-openiban
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 405Status out of date: last check 34 h ago returned HTTP 200

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

io.github.cammac-creator/ibanforge

In its own words, on Official MCP Registry:

Check the bank behind an IBAN before you pay: bank-code check, BIC with source, bank-level sanctions

Openiban

In its own words, on Official MCP Registry:

OpenIBAN MCP — validate an IBAN's checksum + bank code and resolve the bank name / BIC / city.…

How to run each

io.github.cammac-creator/ibanforge As a remote MCP server

Claude Code
claude mcp add --transport http ibanforge https://api.ibanforge.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: IBANFORGE_API_KEY (secret), X-API-Key header

Openiban As a remote MCP server

Claude Code
claude mcp add --transport http openiban https://gateway.pipeworx.io/openiban/mcp

Requires: PIPEWORX_API_KEY (secret)

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of io.github.cammac-creator/ibanforge nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Only io.github.cammac-creator/ibanforge asks for

  • IBANFORGE_API_BASE
  • IBANFORGE_API_KEY (secret)

Only Openiban asks for

  • PIPEWORX_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.cammac-creator/ibanforge · What it can do: Openiban · Compare two other plugins

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