Iban Validator Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Validate and format IBAN bank account numbers locally. No network and no key.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

A local MCP server that lets an assistant validate and format IBAN bank account numbers, working entirely offline with no keys.

What you can do
Validate IBAN bank account numbers, checking their structure and checksum locally. Format IBAN values into a standard readable layout. Runs entirely on the user's machine, so no lookup or verification request leaves the device.
When to use it
Useful when an assistant handles European or other IBAN account numbers and needs to check that they are well-formed or present them consistently, for example in invoices, payment details or data cleanup.
Requirements
Runs as a local process on the user's machine, installed from the npm package iban-validator-mcp over stdio. Desktop only; no web executable. No authentication, environment variables or headers are declared, and no network access is needed.
Before you install
Validation only confirms that an IBAN is structurally valid and correctly checksummed; it does not prove the account exists or is active. Treat results as a formatting and syntax check, not as payment verification.

Installation

In SourceWeft

  1. Open Iban Validator Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.