ValidateFin
NPM · @VALIDATEFIN/MCP · SCANNED AUG 3
Validate SEPA, UBL/Peppol, XRechnung, camt, ACH & IBAN files locally — no data leaves your machine.
Available components
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. How we score →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (111 of 112), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (111 of 112), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @validatefin/mcp
claude mcp add elnicaise-validatefin -- npx -y @validatefin/mcp
codex mcp add elnicaise-validatefin -- npx -y @validatefin/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"elnicaise-validatefin": {
"type": "local",
"command": [
"npx",
"-y",
"@validatefin/mcp"
],
"enabled": true
}
}
} openclaw mcp add elnicaise-validatefin --command npx --arg -y --arg @validatefin/mcp
mcp_servers:
elnicaise-validatefin:
command: "npx"
args: ["-y", "@validatefin/mcp"] {
"mcpServers": {
"elnicaise-validatefin": {
"command": "npx",
"args": [
"-y",
"@validatefin/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Licence: MIT functional
- 1 Aug 26 +16
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −23
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@validatefin/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 111 packages
111 packages in the resolved dependency tree · 109 deprecated · 32 stale · 1 without a linked repository.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
convert_bai2 ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The raw BAI2 file content (comma-delimited records: 01 file header, 02 group, 03 account, 16 transaction, 88 continuation) |
No output schema declared.
No examples provided.
convert_mt940 ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The raw MT940 file content (SWIFT tags :20:, :25:, :60F:, :61:, :86:, :62F:) |
No output schema declared.
No examples provided.
generate_camt_test ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| openingBalance | number | — | Opening balance of the statement (default 0) |
| xml | string | yes | The SEPA pain.001 or pain.008 XML content |
No output schema declared.
No examples provided.
validate_aba ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| routingNumber | string | yes | The 9-digit ABA routing number to validate, e.g. 111000025 |
No output schema declared.
No examples provided.
validate_ach ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The raw ACH / NACHA file content (fixed-width, 94-character records) |
No output schema declared.
No examples provided.
validate_camt ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The XML file content to validate |
No output schema declared.
No examples provided.
validate_iban ~55
Validate an IBAN: length, country code and mod-97 checksum. 100% local.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | The IBAN to validate, e.g. FR7630006000011234567890189 |
No output schema declared.
No examples provided.
validate_sepa ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The XML file content to validate |
No output schema declared.
No examples provided.
validate_ubl ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The XML file content to validate |
No output schema declared.
No examples provided.
validate_xrechnung ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The XML file content to validate |
No output schema declared.
No examples provided.