Norma 43
PYPI · NORMA43-MCP · 2 COMPONENTS
Parse Spanish Norma 43 bank statements, reconcile against invoices, validate IBAN/NIF/SEPA ids.
Available components
Last scanned (13 hours ago)
Scores higher than 60% of PyPI servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ArceeDev/norma43-mcp). View diagnostics → Pass
- License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (16)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 19 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 18 Nov 26 +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.
- 16 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.3.0 → 0.3.1 functional
- 14 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 +16
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed pypi/norma43-mcp@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ArceeDev/norma43-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ArceeDev/norma43-mcp/.github/workflows/release.yml@refs/tags/v0.3.1 |
| Rekor log index | 3906623155 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:ea724c0dfbea8e957b91dcc5b40ef1cc22c4433a8c0f5bb4816e3935903b5f64 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
credits_balance Check credit balance ~19
Remaining credits on your KeyFlint license. Free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
norma43_to_csv Convert Norma 43 to CSV ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| content_base64 | string | – | – |
| decimal_comma | boolean | – | – |
| delimiter | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
parse_norma43 Read Norma 43 bank statement ~272
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).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| content_base64 | string | – | – |
| include_movements | boolean | – | – |
| max_movements | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pricing Show tool prices ~20
Credit price of each tool and where to buy credits. Free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
reconcile_movements Reconcile bank movements with invoices ~451
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).
| Name | Type | Req | Description |
|---|---|---|---|
| amount_tolerance | string | – | – |
| content | string | – | – |
| content_base64 | string | – | – |
| date_window_days | integer | – | – |
| expected | array | yes | – |
| max_group_size | integer | – | – |
| min_score | integer | – | – |
| movements | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sepa_credit_transfers Build SEPA credit transfer batch ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | – | – |
| debtor | object | yes | – |
| execution_date | string | yes | – |
| payments | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sepa_creditor_id Build SEPA creditor identifier ~106
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_code | string | – | – |
| nif | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sepa_direct_debits Build SEPA direct debit batch (remesa de recibos) ~406
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.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_date | string | yes | – |
| created_at | string | – | – |
| creditor | object | yes | – |
| debits | array | yes | – |
| scheme | string | – | – |
| sequence_type | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
validate_identifier Validate Spanish ID or IBAN ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| value | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · norma43-mcp
claude mcp add arceedev-norma43-mcp -- uvx norma43-mcp
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.