io.github.sebastienrousseau/iso20022-mcp
PYPI · ISO20022-MCP
Unified ISO 20022 MCP gateway routing across the pain, pacs, camt and acmt message families.
Available components
Last scanned (20 hours ago)
Scores higher than 99% 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs poetry.core.masonry.api at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sebastienrousseau/iso20022-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0 OR MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1669 tokens (~185/item across 9 items; 7 tools + 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- Package version: 0.0.17 → 0.0.18 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- Package version: 0.0.16 → 0.0.17 functional
- 19 Oct 26 +1
- Stability: pass → 0.97 functional
- Package version: 0.0.13 → 0.0.16 functional
- Package version: 0.0.13 → 0.0.15 functional
- Package version: 0.0.13 → 0.0.14 functional
- 17 Oct 26 +1
- Stability: 0.87 → 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 4 Nov 2026 · Analysed pypi/iso20022-mcp@0.0.18
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 | sebastienrousseau/iso20022-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sebastienrousseau/iso20022-mcp/.github/workflows/release.yml@refs/tags/v0.0.18 |
| Rekor log index | 3471512507 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:930ff1af917251033671082aca9ba00b2de5c6a18f811936145923e06fdba226 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | poetry.core.masonry.api |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| 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 →
describe ~168
Describe a message type: its required fields and input JSON Schema, resolved from the family's backing server. When to use: After 'search', to obtain the schema and required field names for the flat records that 'validate' and 'generate' take. Not for: Raw XML payloads; 'parse' reads those. Behavior: Read-only, idempotent resolution from local schemas. Errors return a structured {'error': ...} payload rather than raising.
| Name | Type | Req | Description |
|---|---|---|---|
| message_type | string | yes | ISO 20022 message type, e.g. 'pain.001.001.09', 'pacs.008' or 'camt.053'. For pain messages a fully-versioned type is preferred; the bare family name 'pain.001' resolves to 'pain.001.001.09'. |
Structured output declared, but exposes no named fields.
No examples provided.
generate ~339
Generate a validated ISO 20022 XML message from records; the XML document is returned in the 'xml' key. On failure the 'error' value lists every missing or invalid field at once — fix them all and retry once. When to use: Outbound initiation and interbank messages (pain.001, pacs.008, acmt.001, camt.056). Not for: Inbound statements (camt.053); they have no generator and return an explanatory error. Behavior: Pure transformation; read-only and idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| message_type | string | yes | ISO 20022 message type, e.g. 'pain.001.001.09', 'pacs.008' or 'camt.053'. For pain messages a fully-versioned type is preferred; the bare family name 'pain.001' resolves to 'pain.001.001.09'. |
| records | array | yes | List of flat record objects (field name → value). Field names come from the family's input schema — call describe(message_type) for the required fields. For pain.001 credit transfers the key fields a… |
Structured output declared, but exposes no named fields.
No examples provided.
list_families ~123
List every ISO 20022 family the gateway routes to (pain, pacs, camt, acmt): its capabilities, backing package, and whether that package is installed in this environment. When to use: Use to check environment readiness and verify whether optional backing packages (pain001-mcp, pacs008-mcp, camt053-mcp, acmt001-mcp) are installed. Not for: Searching specific schemas; 'search' and 'describe' cover those. Behavior: Pure in-memory introspection; read-only and idempotent.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_servers ~125
List the whole ISO 20022 suite the gateway knows: the message families (pain/pacs/camt/acmt), the Exceptions & Investigations messages (camt.056/camt.029), and the specialized servers (reconciliation, agent-payment bridge) with what each does. When to use: Use to discover available specialized servers across the suite and route cross-cutting payments workflows. Not for: Building or reading messages; the gateway tools 'generate', 'parse' and 'validate' do that. Behavior: Pure in-memory catalog listing; read-only and idempotent.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
parse ~256
Parse an inbound ISO 20022 XML message into structured data. Parse coverage is per-family: pacs (e.g. pacs.008) and camt (e.g. camt.053) only. The initiation families pain and acmt are outbound-only — they have NO parser here, so a generate→parse round-trip for pain.001 or acmt.001 fails; 'validate' or the backing server's XSD validation checks those instead. When to use: Use to extract structured transactions, entries, debtor/creditor data, and balances from inbound messages (pacs.008 customer credit transfers, camt.053 statements). Not for: Outbound initiation families (pain.001, acmt.001). Behavior: Pure in-memory XML parsing; read-only and idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| message_type | string | yes | ISO 20022 message type, e.g. 'pain.001.001.09', 'pacs.008' or 'camt.053'. For pain messages a fully-versioned type is preferred; the bare family name 'pain.001' resolves to 'pain.001.001.09'. |
| xml | string | yes | Raw ISO 20022 XML to parse. |
Structured output declared, but exposes no named fields.
No examples provided.
search ~147
Search the ISO 20022 catalogue by use-case, message type or keyword (e.g. 'reconciliation', 'make a payment', 'pacs.008') and get the matching message types, their family, and which package provides them. When to use: First, to discover which ISO 20022 message type fits your workflow and which backing package supplies it. Not for: Inspecting fields or checking records once the message type is known; 'describe' and 'validate' cover those. Behavior: Pure in-memory lookup; read-only and idempotent with zero network or filesystem I/O.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Use-case, message type or keyword. Empty = all. |
Structured output declared, but exposes no named fields.
No examples provided.
validate ~319
Validate records for a message type against its JSON Schema, via the family's backing server. When to use: Ahead of 'generate', to verify record field types, required fields, date formats (YYYY-MM-DD), and IBAN/BIC constraints without generating XML. Not for: Raw XML documents; the backing server's XSD validation tools and 'parse' handle those. Behavior: Pure deterministic validation; read-only and idempotent with zero network I/O.
| Name | Type | Req | Description |
|---|---|---|---|
| message_type | string | yes | ISO 20022 message type, e.g. 'pain.001.001.09', 'pacs.008' or 'camt.053'. For pain messages a fully-versioned type is preferred; the bare family name 'pain.001' resolves to 'pain.001.001.09'. |
| records | array | yes | List of flat record objects (field name → value). Field names come from the family's input schema — call describe(message_type) for the required fields. For pain.001 credit transfers the key fields a… |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.sebastienrousseau/iso20022-mcp server?
io.github.sebastienrousseau/iso20022-mcp runs locally as a PyPI package, launched with uvx iso20022-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 · iso20022-mcp
claude mcp add sebastienrousseau-iso20022-mcp -- uvx iso20022-mcp
What is the io.github.sebastienrousseau/iso20022-mcp server?
io.github.sebastienrousseau/iso20022-mcp is listed in the public MCP registry as io.github.sebastienrousseau/iso20022-mcp. Unified ISO 20022 MCP gateway routing across the pain, pacs, camt and acmt message families. This page covers its PyPI package (iso20022-mcp).
Is the io.github.sebastienrousseau/iso20022-mcp server safe to use?
io.github.sebastienrousseau/iso20022-mcp scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 io.github.sebastienrousseau/iso20022-mcp server expose?
io.github.sebastienrousseau/iso20022-mcp exposes 7 tools: search, list_families, list_servers, describe, validate, and 2 more. Their descriptions and schemas cost roughly 1,477 tokens of context every time the server is loaded.
Is the io.github.sebastienrousseau/iso20022-mcp server still maintained?
io.github.sebastienrousseau/iso20022-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.sebastienrousseau/iso20022-mcp server under?
io.github.sebastienrousseau/iso20022-mcp declares the Apache-2.0 OR MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.