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