Log inSubmit server
ValidateFin logo

ValidateFin

Validates SEPA, e-invoicing, ISO 20022, ACH, IBAN and MT940 files locally through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install ValidateFin

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "validatefin": {
      "command": "npx",
      "args": [
        "-y",
        "@validatefin/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 34 tools correctly ().

Overview

ValidateFin MCP server validates payment, banking and e-invoicing files entirely on the local machine. It exposes MCP tools for SEPA, UBL/Peppol, XRechnung, camt, ACH/NACHA and IBAN checks, plus MT940 conversion and camt test generation. XML inputs are passed as strings, while ACH and MT940 use raw content; results include validation details or generated camt XML. Reach for it when an agent needs local format and rule validation without uploading financial files.

Use cases

  • Validate SEPA payment and direct-debit XML before submission
  • Check UBL, Peppol or XRechnung invoices against business rules
  • Inspect camt statements and cash-management files locally
  • Convert MT940 bank statements into camt.053 XML
  • Verify ACH files and IBAN values in agent workflows

Key features

  • SEPA ISO 20022 and EPC rule validation
  • UBL, Peppol BIS and XRechnung Schematron checks
  • camt.052, camt.053 and camt.054 inspection
  • ACH/NACHA structure and control-total validation
  • MT940 to camt.053 conversion
  • Local processing without file uploads

Tools34

What ValidateFin lets your agent do. Expand a tool for its parameters.

Verified live~10.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

13/13 checks healthy over the last 61d

What it can do

From the 34 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 34
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age126 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · @validatefin/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commit4mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed34Callable tools this server registers over MCP.

How ValidateFin works

What ValidateFin MCP server does

ValidateFin MCP server brings local validation of financial file formats into an MCP-compatible workflow. It covers SEPA Credit Transfer and Direct Debit messages, UBL and Peppol BIS Billing 3.0 invoices, German XRechnung invoices, ISO 20022 camt files, US ACH/NACHA files and IBAN values. It also converts legacy SWIFT MT940 statements into camt.053.001.02 XML and can create a camt.053 test statement from a pain.001 or pain.008 document.

The tools apply format checks and, where specified, business-rule validation. SEPA checks use ISO 20022 schemas and EPC rules. UBL and XRechnung validation uses the stated EN 16931, Peppol and KoSIT rule sets, returning failed rules with their identifiers. ACH checks cover fixed-width structure, routing numbers, hashes and control totals.

How it works

The server runs as a local MCP process. A client sends XML text to the XML validation tools through an xml argument. validate_ach and convert_mt940 receive raw file data through content, while validate_iban accepts an iban string. Validation responses are JSON containing the result, errors and a summary. Conversion and test-generation tools return camt.053 XML.

The camt validator accepts camt.052, camt.053 and camt.054 messages in the documented .02, .06, .08, .10 and .11 versions. For camt.053, it extracts account, balance and entry information and also performs the stated ISO 20022 XSD validation. MT940 conversion checks whether the opening balance, turnover and closing balance reconcile, including RC and RD reversals.

Tools and capabilities

The ValidateFin MCP server exposes these capabilities:

  • Validate pain.001 and pain.008 messages against ISO 20022 and EPC checks.
  • Validate UBL or CII invoices against EN 16931 and Peppol BIS 3.0 rules.
  • Validate UBL or CII XRechnung documents against EN 16931 and KoSIT BR-DE rules.
  • Inspect camt.052, camt.053 and camt.054 files, including camt.053 schema validation.
  • Check ACH/NACHA record lengths, routing checksums, entry hashes and totals.
  • Check IBAN country, length and mod-97 checksum requirements.
  • Convert MT940 statements to camt.053.001.02 XML.
  • Generate a camt.053 test statement from a SEPA payment or direct-debit file.

Setup and configuration

Add the server to an MCP client using the npx -y @validatefin/mcp command. The documented configuration names the server validatefin and uses standard command-and-argument fields, so no service URL or separate account is described. No environment variables are required by the provided setup instructions.

The ValidateFin MCP server performs validation locally. The documentation states that files and other data are not uploaded to a remote server, which makes the local process appropriate for workflows that must keep payment or invoice content on the machine.

Limitations and notes

The project code is licensed under MIT, while bundled components and rule sets have separate licenses. The documentation specifically lists SaxonJS, EN 16931 rules, Peppol BIS 3.0 rules and libxml2 under their respective licenses.

Using official schemas or rule sets does not mean the tool is certified or endorsed by OpenPEPPOL, the European Commission or a Peppol Authority. That distinction matters when validation results are used in regulated invoicing or payment processes.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about ValidateFin

ValidateFin is an MCP server that connects AI clients to local validation tools for SEPA, UBL/Peppol, XRechnung, camt, ACH/NACHA and IBAN files. Its main tools validate these formats, convert MT940 statements to camt.053 XML, and generate camt.053 test statements from pain.001 or pain.008 files.

Install it by adding an MCP server entry that runs `npx -y @validatefin/mcp`. The documented configuration uses the `validatefin` server name with `command` set to `npx` and arguments for `-y` and `@validatefin/mcp`.

Add the same stdio MCP configuration using `npx -y @validatefin/mcp` to the client configuration.

No, validation runs entirely on the local machine.

XML validation tools accept file text through an `xml` string, while `validate_ach` and `convert_mt940` use raw `content`. `validate_iban` takes an `iban` string, and the generation and conversion tools return camt.053 XML.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewValidateFin AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/validatefin?style=directory)](https://allmcps.com/mcp/validatefin)
HTML Embed
<a href="https://allmcps.com/mcp/validatefin"><img src="https://allmcps.com/api/badge/validatefin?style=directory" alt="ValidateFin on AllMCPs" /></a>