mcpField
S
SepaCheck Validator

SepaCheck Validator

Local
checksepa.comFinance0Updated 1w ago
RepositoryVisit website

About SepaCheck Validator

SepaCheck Validator is a stdio MCP server for validating SEPA pain.001 and camt.053/054 XML documents, and converting supported camt files to JSON or CSV. It is for workflows that need structured validation findings from the checksepa.com API.

Key features

  1. 01Validate pain.001 documents
  2. 02Validate camt.053 and camt.054 files
  3. 03Convert camt files to JSON or CSV
  4. 04Return structured errors and warnings

Use cases

  1. 01Check a pain.001 payment file
  2. 02Validate camt.053 or camt.054 reports
  3. 03Convert a camt document for downstream use

MCP support

Exposes SEPA validation and camt conversion as tools to MCP clients over stdio. It sends requests to the checksepa.com API; input can be an XML string or a file path.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "wenboteng-sepa-validator": {
      "command": "npx",
      "args": [
        "-y",
        "sepa-validator-mcp"
      ]
    }
  }
}
Run commandnpx -y sepa-validator-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmsepa-validator-mcp0.2.0

Tools

1

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
xmlstringNoSEPA XML as a string. Use this or file_path.
file_pathstringNoPath to a SEPA XML file. Resolved by this process.

Details

From the project 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):

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

Cursor

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

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

From a checkout, before the npm publish:

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

VS Code

.vscode/mcp.json:

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

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

MIT. Copyright (c) 2026 Bobook Limited.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.