SepaCheck Validator
NPM · SEPA-VALIDATOR-MCP
Validate SEPA pain.001 and camt.053/054 files with the free checksepa.com API.
Available components
Last scanned (19 hours ago)
Scores higher than 40% of npm servers
Category Finance and Payments
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 555 tokens (~185/item across 3 items; 3 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 Management10
- Stability observed for 3 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 21 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 −1
- Malware scan: unverified → pass ▲ security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.0 → 0.2.0 functional
- 19 Oct 26 56
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 22 Oct 2026 · Analysed npm/sepa-validator-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
camt_convert Convert camt.053 or camt.054 ~210
Convert one camt.053 or camt.054 statement (.02 or .08) to normalized JSON or CSV via POST https://checksepa.com/v1/camt/convert. JSON statements include account IBAN, balances, and entries with amount, currency, creditDebit, bookingDate, valueDate, counterpartyName, counterpartyIban, remittanceInfo, and endToEndId. A credit uses the debtor as the counterparty. A debit uses the creditor. No API key. Shares the free limit: 30 per IP per hour, 200 per UTC day, 2 MB. The file is not stored. Provide exactly one of file_path or xml. format is json (default) or csv.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | – | Path to a camt XML file. Resolved by this process. |
| format | string | – | json (default) or csv. |
| xml | string | – | camt XML as a string. Use this or file_path. |
| Name | Type | Req | Description |
|---|---|---|---|
| csv | string | – | – |
| format | string|null | – | – |
| statements | array | – | – |
| version | string|null | – | – |
No examples provided.
camt_validate Validate camt.053 or camt.054 ~192
Validate one ISO 20022 bank statement (camt.053.001.02, camt.053.001.08, camt.054.001.02, or camt.054.001.08) against the official XML Schema via POST https://checksepa.com/v1/camt/validate. No API key. This route shares the free limit with pain.001 validate and camt convert: 30 requests per IP per hour, 200 per UTC day, 2 MB. The file is not stored. Provide exactly one of file_path or xml. Returns valid, format, version, errors, and warnings. Each finding has code, message, path, and line.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | – | Path to a camt XML file. Resolved by this process. |
| xml | string | – | camt XML as a string. Use this or file_path. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| format | string|null | yes | – |
| valid | boolean | yes | – |
| version | string|null | yes | – |
| warnings | array | yes | – |
No examples provided.
validate_sepa Validate SEPA XML ~153
Validate one SEPA XML document (pain.001.001.03 or pain.001.001.09). The file is uploaded to the free keyless API POST https://checksepa.com/v1/validate. Limits: 30 requests per IP per hour, 200 per UTC day, 2 MB. The file is not stored. Provide exactly one of file_path or xml. Returns valid, format, version, errors, and warnings. Each finding has code, message, path, and line.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | – | Path to a SEPA XML file. Resolved by this process. |
| xml | string | – | SEPA XML as a string. Use this or file_path. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| format | string|null | yes | – |
| valid | boolean | yes | – |
| version | string|null | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the SepaCheck Validator MCP server?
SepaCheck Validator runs locally as an npm package, launched with npx -y sepa-validator-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sepa-validator-mcp
claude mcp add wenboteng-sepa-validator -- npx -y sepa-validator-mcp
What is the SepaCheck Validator MCP server?
SepaCheck Validator is an MCP server listed in the public MCP registry as io.github.wenboteng/sepa-validator. Validate SEPA pain.001 and camt.053/054 files with the free checksepa.com API. This page covers its npm package (sepa-validator-mcp).
Is the SepaCheck Validator MCP server safe to use?
SepaCheck Validator scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SepaCheck Validator MCP server expose?
SepaCheck Validator exposes 3 tools: validate_sepa, camt_validate, camt_convert. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.
Is the SepaCheck Validator MCP server still maintained?
SepaCheck Validator is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the SepaCheck Validator MCP server under?
SepaCheck Validator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.