# ValidateFin (npm · @validatefin/mcp)

Validate SEPA, UBL/Peppol, XRechnung, camt, ACH & IBAN files locally — no data leaves your machine.

- Trust score: 70/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@validatefin/mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/elnicaise-validatefin/validatefin-mcp.md), [page](https://verifymcp.io/servers/elnicaise-validatefin/validatefin-mcp)

## Channel facts

- Registry: `npm`
- Package: `@validatefin/mcp`
- Version: `1.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 88/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (111 of 112), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (111 of 112), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 18 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1128 tokens (~112/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add elnicaise-validatefin -- npx -y @validatefin/mcp
```

### Codex

```bash
codex mcp add elnicaise-validatefin -- npx -y @validatefin/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "elnicaise-validatefin": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@validatefin/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add elnicaise-validatefin --command npx --arg -y --arg @validatefin/mcp
```

### Hermes

```yaml
mcp_servers:
  elnicaise-validatefin:
    command: "npx"
    args: ["-y", "@validatefin/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "elnicaise-validatefin": {
      "command": "npx",
      "args": [
        "-y",
        "@validatefin/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 69, +48)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional] Licence: MIT

### 2026-08-01 (score 21, +16)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-31 (score 5, −23)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 28, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (10)

### `validate_sepa` (~95 tokens)

Validate a SEPA payment file — Credit Transfer (pain.001) or Direct Debit (pain.008) — against the EPC schemas: IBAN, BIC, amounts and control sums, plus, for direct debits, the mandate (MndtId + signature date), Creditor Scheme Identifier (ICS) and sequence type. 100% local.

Input parameters:

- `xml` (string, required): The XML file content to validate

### `validate_ubl` (~111 tokens)

Validate a UBL / Peppol BIS Billing 3.0 invoice or credit note by running the OFFICIAL EN 16931 + Peppol BIS 3.0 Schematron — the same rule sets used by the official European e-invoicing validators — plus UBL structure checks. Returns the failed business rules with their official IDs (BR-*, BR-CO-*, Peppol rules). 100% local.

Input parameters:

- `xml` (string, required): The XML file content to validate

### `validate_xrechnung` (~104 tokens)

Validate a German XRechnung (UBL) invoice — the German CIUS of EN 16931, mandatory for B2G — by running the OFFICIAL EN 16931 core Schematron + the KoSIT XRechnung BR-DE rules (the same rule sets used by the official German validator). Returns failed rules with their IDs (BR-*, BR-DE-*). 100% local.

Input parameters:

- `xml` (string, required): The XML file content to validate

### `validate_camt` (~96 tokens)

Validate an ISO 20022 camt cash-management file and extract account, balances and entries: camt.053 (bank-to-customer statement), camt.052 (account report / intraday) or camt.054 (debit/credit notification). Versions .02, .06, .08, .10 and .11. 100% local.

Input parameters:

- `xml` (string, required): The XML file content to validate

### `validate_ach` (~118 tokens)

Validate a US ACH / NACHA file in the fixed-width Nacha format: 94-character records, the record structure (File Header, Batch Header, Entry Detail, Addenda, Batch Control, File Control), the ABA routing-number check digit (3-7-1), the entry hash, and all batch and file control totals (debits, credits, entry/addenda count, block count). 100% local.

Input parameters:

- `content` (string, required): The raw ACH / NACHA file content (fixed-width, 94-character records)

### `validate_iban` (~55 tokens)

Validate an IBAN: length, country code and mod-97 checksum. 100% local.

Input parameters:

- `iban` (string, required): The IBAN to validate, e.g. FR7630006000011234567890189

### `validate_aba` (~90 tokens)

Validate a US ABA routing number (routing transit number, RTN): 9-digit structure, the ABA 3-7-1 check digit (mod 10) and the Federal Reserve routing symbol / district. The US counterpart of IBAN validation. 100% local.

Input parameters:

- `routingNumber` (string, required): The 9-digit ABA routing number to validate, e.g. 111000025

### `generate_camt_test` (~96 tokens)

Generate a valid camt.053 test bank statement from a SEPA pain.001 (credit transfer) or pain.008 (direct debit) file. Returns the camt.053 XML — ideal test data for reconciliation. 100% local.

Input parameters:

- `openingBalance` (number): Opening balance of the statement (default 0)
- `xml` (string, required): The SEPA pain.001 or pain.008 XML content

### `convert_mt940` (~158 tokens)

Convert a legacy SWIFT MT940 bank statement (Customer Statement Message) to an ISO 20022 camt.053.001.02 XML statement. MT940 was retired by SWIFT in November 2025 and is being replaced by camt.053. Parses the balances and transactions, checks that opening balance + turnover = closing balance, and returns the camt.053 XML with the real balances and mixed debit/credit entries (RC/RD reversals handled). If the file contains several statements, only the first is converted. 100% local.

Input parameters:

- `content` (string, required): The raw MT940 file content (SWIFT tags :20:, :25:, :60F:, :61:, :86:, :62F:)

### `convert_bai2` (~205 tokens)

Convert a BAI2 (Bank Administration Institute, version 2) cash-management bank statement — the dominant US/Canada statement format, the North-American counterpart of SWIFT MT940 — to an ISO 20022 camt.053.001.02 XML statement. Parses the 01/02/03/16/88 record hierarchy, infers debit/credit direction from the numeric type code (100–399 credit, 400–699 debit), scales integer minor-unit amounts by the currency, checks that opening ledger balance (010) + turnover = closing ledger balance (015), and returns the camt.053 XML with the real balances and mixed debit/credit entries. If the file contains several accounts, only the first is converted. 100% local.

Input parameters:

- `content` (string, required): The raw BAI2 file content (comma-delimited records: 01 file header, 02 group, 03 account, 16 transaction, 88 continuation)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/elnicaise-validatefin/validatefin-mcp#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 21
- 2026-07-31: 5
- 2026-07-30: 28
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/@validatefin/mcp
- Socket report: https://socket.dev/npm/package/@validatefin/mcp
- Repository: https://github.com/elnicaise/validatefin-mcp
- Website: https://validatefin.com/
- Changelog RSS feed: https://verifymcp.io/servers/elnicaise-validatefin/validatefin-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/elnicaise-validatefin/validatefin-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/elnicaise-validatefin/validatefin-mcp