SepaCheck Validator MCP server
io.github.wenboteng/sepa-validator·v0.2.0Validate SEPA pain.001 and camt.053/054 files with the free checksepa.com API.
0 stars0 downloads/wk
Reviews
Write oneNobody has reviewed SepaCheck Validator yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
SepaCheck Validator tools (3)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
camt_convertConvert one camt.053 or camt.054 statement (.02 or .08) to normalized JSON or CSV via
camt_validateValidate one ISO 20022 bank statement (camt.053.001.02, camt.053.001.08, camt.054.001.02, or camt.054.001.08)
validate_sepaValidate one SEPA XML document (pain.001.001.03 or pain.001.001.09).
Public scan report
scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it
- Code scan6 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 5 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How SepaCheck Validator compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 3 read
Install SepaCheck Validator in Claude Code, Cursor or VS Code
Runs npx -y sepa-validator-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add sepa-validator -- npx -y sepa-validator-mcp
What the publisher says
From the SepaCheck Validator repository's README, as published. We do not edit it. Read it on GitHub
SEPA pain.001 and camt validator — free API, CLI, and MCP server
Client tools for the free, keyless API at checksepa.com. Send one SEPA credit-transfer XML file (ISO 20022 pain.001.001.03 or pain.001.001.09), or a camt.053 / camt.054 bank statement (.02 or .08).
This repository is only the public client: CLI, MCP server, OpenAPI copy, samples, and examples. It does not contain the validator engine.
The file is uploaded to POST https://checksepa.com/v1/validate for that request. The service does not store it.
Free limits
Higher limits and API keys: waitlist (joining is free; planned from EUR 79/month, charged only after confirmation). Docs: https://checksepa.com/docs. Machine-readable contract: openapi.json (copy in openapi/openapi.json).
A file can pass here and still be rejected by a bank. Bank implementation guidelines are out of scope. This is not a bank login, EBICS client, Verification of Payee check, or payment initiation.
pain.008 is recognised (format and version) on POST /v1/validate and returned with valid: false. camt.053 and camt.054 versions .02 and .08 are checked on POST /v1/camt/validate and converted on POST /v1/camt/convert. A camt file sent to POST /v1/validate is still only recognised.
curl
Using the published valid sample:
curl -F "file=@samples/valid-pain001-001-03.xml" https://checksepa.com/v1/validateRaw XML body:
curl -X POST https://checksepa.com/v1/validate \
-H "Content-Type: application/xml" \
--data-binary @samples/valid-pain001-001-09.xmlexamples/curl.sh wraps the multipart request.
Sample request and response
curl -F "file=@samples/invalid-pain001-001-03.xml" https://checksepa.com/v1/validateThe invalid sample is published as failing. The report has seven errors. The first one:
{
"valid": false,
"format": "pain.001",
"version": "pain.001.001.03",
"errors": [
{
"code": "EPC-CTRLSUM",
"message": "CtrlSum is 999.00 but the transactions sum to 175.50.",
"path": "/Document/CstmrCdtTrfInitn/GrpHdr/CtrlSum",
"line": 8
}
],
"warnings": []
}valid: true means the file passed the free baseline. errors and warnings use code, message, path, and line. line is 1-based, or null when the parser cannot place the finding.
Samples
Copied from the checksepa.com sample set. Synthetic data and dummy IBANs, not real payments.
CLI
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
SepaCheck Validator: common questions
- Is SepaCheck Validator MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the SepaCheck Validator safety report
- How do I install SepaCheck Validator?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does SepaCheck Validator need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is SepaCheck Validator maintained?
- The last commit was 14 days ago (2026-10-21). The latest release is v0.2.0.
- What can I use instead of SepaCheck Validator?
- Servers from other publishers that do the same job: Oh My Posh Validator MCP server.
- How does SepaCheck Validator compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to SepaCheck Validator
Same job from other publishers: the closest match first, then the best rated.
- Oh My Posh ValidatorValidate oh-my-posh configurations and segment snippets against the official schema.not reviewedEstablishedA