io.github.sebastienrousseau/iso20022-mcp
PYPI · ISO20022-MCP · SCANNED SEP 20
Unified ISO 20022 MCP gateway routing across the pain, pacs, camt and acmt message families.
Available components
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 Security96
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 32 of 36 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs poetry.core.masonry.api at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 32 of 36 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0 OR MIT).Pass
- Actively maintained (last published 21 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 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 1214 tokens (~134/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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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
{
"mcpServers": {
"sebastienrousseau-iso20022-mcp": {
"command": "uvx",
"args": [
"iso20022-mcp"
]
}
}
} {
"servers": {
"sebastienrousseau-iso20022-mcp": {
"command": "uvx",
"args": [
"iso20022-mcp"
]
}
}
} codex mcp add sebastienrousseau-iso20022-mcp -- uvx iso20022-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sebastienrousseau-iso20022-mcp": {
"type": "local",
"command": [
"uvx",
"iso20022-mcp"
],
"enabled": true
}
}
} openclaw mcp add sebastienrousseau-iso20022-mcp --command uvx --arg iso20022-mcp
mcp_servers:
sebastienrousseau-iso20022-mcp:
command: "uvx"
args: ["iso20022-mcp"] {
"McpServers": {
"sebastienrousseau-iso20022-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"iso20022-mcp"
]
}
}
} assistant mcp add sebastienrousseau-iso20022-mcp -t stdio -c uvx -a iso20022-mcp
{
"mcpServers": {
"sebastienrousseau-iso20022-mcp": {
"command": "uvx",
"args": [
"iso20022-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.77 functional
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 20 Sept 2026 · Analysed pypi/iso20022-mcp@0.0.11
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 |
|---|---|
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 ~97
Describe a message type: its required fields and input JSON Schema, resolved from the family's backing server.
| 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 ~305
Generate a validated ISO 20022 XML message from records; the XML document is returned in the 'xml' key. Supported for initiation and interbank families (pain, pacs, acmt); statement families (camt) are inbound-only and return an explanatory error. On failure the 'error' value lists every missing or invalid field at once — fix them all and retry once.
| 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 ~49
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_servers ~65
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
parse ~187
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 do not attempt a generate→parse round-trip for pain.001 or acmt.001; use 'validate' or the backing server's XSD validation instead.
| 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 ~75
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.
| 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 ~244
Validate records for a message type against its JSON Schema, via the family's backing server.
| 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.
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 84 out of 100 on VerifyMCP. 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,022 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 20 September 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.