# SepaCheck Validator (npm · sepa-validator-mcp)

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

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- npm · `sepa-validator-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/wenboteng-sepa-validator/sepa-validator-mcp.md), [page](https://verifymcp.io/servers/wenboteng-sepa-validator/sepa-validator-mcp)

## Channel facts

- Registry: `npm`
- Package: `sepa-validator-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add wenboteng-sepa-validator -- npx -y sepa-validator-mcp
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "wenboteng-sepa-validator": {
      "command": "npx",
      "args": [
        "-y",
        "sepa-validator-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wenboteng-sepa-validator -- npx -y sepa-validator-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wenboteng-sepa-validator": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "sepa-validator-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wenboteng-sepa-validator --command npx --arg -y --arg sepa-validator-mcp
```

### Hermes

```yaml
mcp_servers:
  wenboteng-sepa-validator:
    command: "npx"
    args: ["-y", "sepa-validator-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "wenboteng-sepa-validator": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "sepa-validator-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add wenboteng-sepa-validator -t stdio -c npx -a -y sepa-validator-mcp
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-21 (score 71, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-20 (score 55, −1)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.1.0 → 0.2.0

### 2026-10-19 (score 56)

First indexed and scored.

## MCP tools (3)

### `validate_sepa` (~153 tokens)

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.

Input parameters:

- `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.

Output parameters:

- `errors` (array)
- `format` (string|null)
- `valid` (boolean)
- `version` (string|null)
- `warnings` (array)

### `camt_validate` (~192 tokens)

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.

Input parameters:

- `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.

Output parameters:

- `errors` (array)
- `format` (string|null)
- `valid` (boolean)
- `version` (string|null)
- `warnings` (array)

### `camt_convert` (~210 tokens)

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.

Input parameters:

- `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.

Output parameters:

- `csv` (string)
- `format` (string|null)
- `statements` (array)
- `version` (string|null)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/wenboteng-sepa-validator/sepa-validator-mcp#diagnostics

## Score history

- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 55
- 2026-10-19: 56

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/sepa-validator-mcp
- Socket report: https://socket.dev/npm/package/sepa-validator-mcp
- Repository: https://github.com/wenboteng/sepa-validator
- Website: https://checksepa.com/
- Changelog RSS feed: https://verifymcp.io/servers/wenboteng-sepa-validator/sepa-validator-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wenboteng-sepa-validator/sepa-validator-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wenboteng-sepa-validator/sepa-validator-mcp