# Norma 43 (pypi · norma43-mcp)

Parse Spanish Norma 43 bank statements, reconcile against invoices, validate IBAN/NIF/SEPA ids.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.keyflint.dev`: 32/100, [markdown](https://verifymcp.io/servers/arceedev-norma43-mcp/norma43-mcp.md), [page](https://verifymcp.io/servers/arceedev-norma43-mcp/norma43-mcp)
- pypi · `norma43-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/arceedev-norma43-mcp/norma43-mcp-2.md), [page](https://verifymcp.io/servers/arceedev-norma43-mcp/norma43-mcp-2)

## Channel facts

- Registry: `pypi`
- Package: `norma43-mcp`
- Version: `0.3.1`
- 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-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 84/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to ArceeDev/norma43-mcp).
  - License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license.
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2013 tokens (~201/item across 10 items; 9 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Norma 43 MCP server?

Norma 43 runs locally as a PyPI package, launched with uvx norma43-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 arceedev-norma43-mcp -- uvx norma43-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "arceedev-norma43-mcp": {
      "command": "uvx",
      "args": [
        "norma43-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "arceedev-norma43-mcp": {
      "command": "uvx",
      "args": [
        "norma43-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add arceedev-norma43-mcp -- uvx norma43-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "arceedev-norma43-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "norma43-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add arceedev-norma43-mcp --command uvx --arg norma43-mcp
```

### Hermes

```yaml
mcp_servers:
  arceedev-norma43-mcp:
    command: "uvx"
    args: ["norma43-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "arceedev-norma43-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "norma43-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add arceedev-norma43-mcp -t stdio -c uvx -a norma43-mcp
```

### Other

```json
{
  "mcpServers": {
    "arceedev-norma43-mcp": {
      "command": "uvx",
      "args": [
        "norma43-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-11-21 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-20 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-19 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 64, 0)

- [security improvement] Malware scan: unverified → pass
- [functional] Package version: 0.3.0 → 0.3.1

### 2026-11-14 (score 64, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-12 (score 78, +16)

- [security improvement] Malware scan: unverified → pass

## MCP tools (9)

### `parse_norma43` (~272 tokens)

Read Norma 43 bank statement

Read a Spanish Norma 43 (Cuaderno 43 / AEB43 / CSB43) bank statement into structured JSON.

Returns every account (CCC, computed IBAN, bank, holder, period, opening/closing balance, debit/credit
totals, breakdown by AEB common concept) and its movements (dates, signed amount, running balance,
concept, references, record-23 texts, decoded SEPA fields in modalidad 3). Checks the file the way a
bank does: record 33 counts and totals, opening + movements = closing, record 88 record count, dates,
signs and field formats. `valid` is false when any error is found; each issue names its line.

Args:
    content: The file as text (paste the .n43/.txt content).
    content_base64: The raw file bytes as base64 (use for CP850/Latin-1 files with Ñ and accents).
    include_movements: False returns only accounts, totals and checks.
    max_movements: Cap on returned movements across all accounts (default 2000, max 20000).

Input parameters:

- `content` (string)
- `content_base64` (string)
- `include_movements` (boolean)
- `max_movements` (integer)

### `norma43_to_csv` (~97 tokens)

Convert Norma 43 to CSV

Convert a Norma 43 statement to CSV (one row per movement, with IBAN, running balance and concept names).

Defaults suit Spanish Excel (';' separator, decimal comma). Free-text cells are protected against
spreadsheet formula injection. Integrity issues are returned alongside the CSV.

Input parameters:

- `content` (string)
- `content_base64` (string)
- `decimal_comma` (boolean)
- `delimiter` (string)

### `reconcile_movements` (~451 tokens)

Reconcile bank movements with invoices

Bank reconciliation (conciliación bancaria): match bank movements to expected items, deterministically.

Bank side: a Norma 43 file (`content` / `content_base64`) or a `movements` list of
{id, date, amount, text}. Expected side: `expected` list of {id, date, amount, reference?, counterparty?}
such as issued invoices (+, cobros), supplier invoices or payroll (-, pagos), or ledger entries.
Signs: + is money in, - is money out, as on the statement.

Finds 1:1 matches, one transfer paying several invoices (1:N) and partial payments (N:1). Each match
has a 0-100 score, a confidence (alta/media/baja) and the evidence used (amount, invoice reference found
in the bank concept, counterparty name, date distance, uniqueness). Ties are never guessed: they are
returned under `ambiguous`. Weak candidates go to `suggestions`. Group matches require a unique exact
sum plus reference or name evidence.

Args:
    expected: Items to find in the bank (max 5000).
    content: Norma 43 file as text (alternative to `movements`).
    content_base64: Norma 43 raw bytes as base64.
    movements: Bank movements if you do not have a Norma 43 file (max 5000).
    date_window_days: Max days between bank date and item date (default 10, max 180).
    amount_tolerance: Max amount difference accepted, e.g. "0.50" for bank fees (default "0", max "10").
    max_group_size: Max items combined in 1:N / N:1 matches (1 disables grouping, max 5).
    min_score: Minimum score to confirm a match (default 50).

Input parameters:

- `amount_tolerance` (string)
- `content` (string)
- `content_base64` (string)
- `date_window_days` (integer)
- `expected` (array, required)
- `max_group_size` (integer)
- `min_score` (integer)
- `movements`

### `validate_identifier` (~145 tokens)

Validate Spanish ID or IBAN

Validate a Spanish/EU banking identifier. Free.

Recognises IBAN (any SEPA country, plus the inner CCC check for ES), CCC (20 digits, returns the IBAN),
NIF/NIE/CIF (also ES-prefixed VAT numbers), SEPA creditor identifier (AT-02) and Norma 43 Referencia 1.
Returns `valid`, the detected `kind`, normalized form and, when wrong, the expected control digits.

Args:
    value: The identifier, spaces and dashes allowed.
    kind: auto | iban | ccc | nif | creditor_id | reference1.

Input parameters:

- `kind` (string)
- `value` (string, required)

### `sepa_creditor_id` (~106 tokens)

Build SEPA creditor identifier

Compute the Spanish SEPA creditor identifier (AT-02, 'identificador de acreedor') from a NIF. Free.

Format: ES + 2 check digits + 3-character business code (default '000') + NIF, per EPC262-08.
Needed to issue SEPA direct debits (adeudos / remesas de recibos, Cuaderno 19.14).

Input parameters:

- `business_code` (string)
- `nif` (string, required)

### `sepa_direct_debits` (~406 tokens)

Build SEPA direct debit batch (remesa de recibos)

Remesa de recibos SEPA: the pain.008.001.02 XML (Cuaderno 19.14) Spanish banks accept for direct debits.

For despachos collecting monthly fees (cuotas) and for clients that charge their customers by recibo.
Every IBAN, the creditor identifier and each mandate are checked first; one wrong recibo refuses the
whole file with the reason (free), so a batch never reaches the bank half-wrong. Same input, same bytes.

Args:
    creditor: {"name": "Asesoría Pérez SL", "iban": "ES91...", "bic": optional, "creditor_id": "ES12000B..."
        or "nif": "B12345678" to compute it (business_code optional, default 000)}.
    collection_date: Requested collection date (YYYY-MM-DD). CORE needs it 1-2 business days ahead.
    debits: [{"name": "Talleres Ruiz SL", "iban": "ES...", "amount": "60.50", "mandate_id": "CUOTA-0012",
        "mandate_date": "2024-01-15", "concept": "Cuota marzo 2026", "end_to_end_id": optional,
        "sequence_type": optional per recibo}].
    sequence_type: Default for all recibos: RCUR (recurring, default), FRST (first), OOFF (one-off), FNAL.
    scheme: CORE (consumers and companies, default) or B2B.
    created_at: Optional YYYY-MM-DDTHH:MM:SS; defaults to collection_date 09:00 so the file is reproducible.

Input parameters:

- `collection_date` (string, required)
- `created_at` (string)
- `creditor` (object, required)
- `debits` (array, required)
- `scheme` (string)
- `sequence_type` (string)

### `sepa_credit_transfers` (~218 tokens)

Build SEPA credit transfer batch

Transferencias SEPA: the pain.001.001.03 XML (Cuaderno 34.14) to pay suppliers or payroll in one upload.

Every IBAN is checked first; one wrong payment refuses the whole file with the reason (free).

Args:
    debtor: The paying company {"name", "iban", "bic" optional, "nif" optional}.
    execution_date: YYYY-MM-DD.
    payments: [{"name": "Proveedor XYZ SL", "iban": "ES...", "amount": "300.00", "concept": "Fra. 5521",
        "end_to_end_id": optional, "purpose": optional ISO code, e.g. SALA (nómina) or SUPP (proveedor)}].
    created_at: Optional YYYY-MM-DDTHH:MM:SS; defaults to execution_date 09:00.

Input parameters:

- `created_at` (string)
- `debtor` (object, required)
- `execution_date` (string, required)
- `payments` (array, required)

### `pricing` (~20 tokens)

Show tool prices

Credit price of each tool and where to buy credits. Free.

### `credits_balance` (~19 tokens)

Check credit balance

Remaining credits on your KeyFlint license. Free.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/arceedev-norma43-mcp/norma43-mcp-2#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 82
- 2026-11-19: 66
- 2026-11-18: 81
- 2026-11-17: 80
- 2026-11-16: 80
- 2026-11-15: 64
- 2026-11-14: 64
- 2026-11-13: 78
- 2026-11-12: 78
- 2026-11-11: 62
- 2026-11-10: 62
- 2026-11-09: 61
- 2026-11-08: 55
- 2026-11-07: 60
- 2026-11-06: 60

## Common questions

### What is the Norma 43 MCP server?

Norma 43 is an MCP server listed in the public MCP registry as io.github.ArceeDev/norma43-mcp. Parse Spanish Norma 43 bank statements, reconcile against invoices, validate IBAN/NIF/SEPA ids. This page covers its PyPI package (norma43-mcp).

### Is the Norma 43 MCP server safe to use?

Norma 43 scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 Norma 43 MCP server expose?

Norma 43 exposes 9 tools: parse_norma43, norma43_to_csv, reconcile_movements, validate_identifier, sepa_creditor_id, and 4 more. Their descriptions and schemas cost roughly 1,734 tokens of context every time the server is loaded.

### Is the Norma 43 MCP server still maintained?

Norma 43 is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Norma 43 MCP server under?

Norma 43 declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

### What did VerifyMCP test on the Norma 43 MCP server?

VerifyMCP ran 16 checks on Norma 43, covering Known CVEs, Install scripts, Dependency health, Source repository and 12 more. One item could not be completed, a gap on our side rather than a finding about Norma 43: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/norma43-mcp/
- Socket report: https://socket.dev/pypi/package/norma43-mcp
- Repository: https://github.com/ArceeDev/norma43-mcp
- Website: https://mcp.keyflint.dev/
- Changelog RSS feed: https://verifymcp.io/servers/arceedev-norma43-mcp/norma43-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/arceedev-norma43-mcp/norma43-mcp-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/arceedev-norma43-mcp/norma43-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/arceedev-norma43-mcp/norma43-mcp-2
