SepaCheck Validator

io.github.wenboteng由 GitHub 账号 wenboteng 发布v0.2.0更新于 Nov 4, 2026

Validate SEPA pain.001 and camt.053/054 files with the free checksepa.com API.

发布方自己的服务：check.tattoo: tattoo size and placement guide

已验证STDIO仅桌面金融开发者工具

服务详情

标识符: io.github.wenboteng/sepa-validator
传输: STDIO
运行时: Desktop only
信任: Verified
发布于: Oct 19, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此条目所属的 GitHub 账号 wenboteng。这并不表明该账号就是产品方。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.wenboteng%2Fsepa-validator.svg)](https://sourceweft.com/mcp/io.github.wenboteng%2Fsepa-validator?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

通过免费的 checksepa.com API 校验 SEPA pain.001 付款文件和 camt.053/054 银行对账单，并可将对账单转换为 JSON 或 CSV。

可以做什么: 校验 SEPA pain.001.001.03 或 .09 付款文件，返回是否有效、格式、版本以及带行号的错误和警告
按官方 XML Schema 校验 camt.053 或 camt.054 对账单（.02 或 .08）
把 camt.053 或 camt.054 对账单转换为规范化 JSON 或 CSV，包含 IBAN、余额和明细条目
输入可以是本地文件路径，也可以直接以字符串形式传入 XML 文档
适用场景: 适合在把 SEPA 付款或银行对账单 XML 提交给银行前做检查，或把 camt 对账单转成 JSON、CSV 以便进一步分析。更适合少量、偶发的校验，而非大批量处理。
运行要求: 以 stdio 本地进程运行，通常通过 npx 启动 npm 包 sepa-validator-mcp，因此需要 Node.js。无需 API 密钥或环境变量。每次调用都需要访问 checksepa.com 的网络连接。

安装前请注意

每次调用都会把 XML 文档上传到第三方 API，付款和账户数据会离开本机；README 称文件不会被存储。免费额度为每 IP 每小时 30 次、每 UTC 日 200 次、单文件 2 MB，三个工具共用。pain.008 会被识别但始终报告为无效。

安装

在 SourceWeft 中

打开控制台中的 SepaCheck Validator，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照仓库中的启动说明。

README

sepa-validator-mcp

Stdio MCP server, version 0.2.0. Tools: validate_sepa (POST https://checksepa.com/v1/validate), camt_validate (POST https://checksepa.com/v1/camt/validate), and camt_convert (POST https://checksepa.com/v1/camt/convert, format json or csv).

Input: exactly one of file_path (read by this process) or xml (the document as a string).

Output: valid, format, version, errors[], and warnings[]. Each finding has code, message, path, and line (line is an integer or null).

validate_sepa covers pain.001.001.03 and pain.001.001.09. camt_validate and camt_convert cover camt.053 and camt.054 versions .02 and .08. pain.008 is recognised by validate_sepa and returned with valid: false. The three routes share the free limit.

Free limit: 30 requests per IP per hour, 200 per UTC day, 2 MB. The file is not stored. The tool calls the network, so it is not a local read-only check. Higher limits and API keys: https://checksepa.com/api-waitlist

Package name: sepa-validator-mcp. Registry name in server.json: io.github.wenboteng/sepa-validator (mcpName matches). Not submitted to the MCP registry yet. Build with npm run build (node dist/index.js) or, after publish, npx -y sepa-validator-mcp.

Claude Desktop

claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json):

json

{  "mcpServers": {    "sepa-validator": {      "command": "npx",      "args": ["-y", "sepa-validator-mcp"]    }  }}

{  "mcpServers": {    "sepa-validator": {      "command": "npx",      "args": ["-y", "sepa-validator-mcp"]    }  }}

Cursor

~/.cursor/mcp.json or the project file .cursor/mcp.json:

json

{  "mcpServers": {    "sepa-validator": {      "command": "npx",      "args": ["-y", "sepa-validator-mcp"]    }  }}

{  "mcpServers": {    "sepa-validator": {      "command": "npx",      "args": ["-y", "sepa-validator-mcp"]    }  }}

From a checkout, before the npm publish:

json

{  "mcpServers": {    "sepa-validator": {      "command": "node",      "args": ["mcp/dist/index.js"]    }  }}

{  "mcpServers": {    "sepa-validator": {      "command": "node",      "args": ["mcp/dist/index.js"]    }  }}

VS Code

.vscode/mcp.json:

json

{  "servers": {    "sepa-validator": {      "type": "stdio",      "command": "npx",      "args": ["-y", "sepa-validator-mcp"]    }  }}

{  "servers": {    "sepa-validator": {      "type": "stdio",      "command": "npx",      "args": ["-y", "sepa-validator-mcp"]    }  }}

Docs: https://checksepa.com/docs · OpenAPI: https://checksepa.com/openapi.json

来源：mcp/README.md，提交 eef04df

工具

validate_sepa

Validate SEPA XML

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.

输入参数xmlfile_path

camt_validate

Validate camt.053 or camt.054

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.

输入参数xmlfile_path

camt_convert

Convert camt.053 or camt.054

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.

输入参数xmlformatfile_path