io.github.sebastienrousseau/camt-exceptions
PYPI · CAMT-EXCEPTIONS
Generate + XSD-validate ISO 20022 E&I camt messages (camt.056 cancellation, camt.029 resolution).
Available components
Last scanned (7 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 35 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/camt-exceptions). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0 OR MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 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 740 tokens (~148/item across 5 items; 4 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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Stability: pass → 0.97 functional
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 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.
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 5 Nov 2026 · Analysed pypi/camt-exceptions@0.0.20
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/camt-exceptions |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sebastienrousseau/camt-exceptions/.github/workflows/release.yml@refs/tags/v0.0.20 |
| Rekor log index | 3078538780 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d42e3649dba74fb51c17573bb15a26d350132aa7f4098d40b5a68772d994e591 |
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 35 packages
| Packages resolved | 35 |
|---|---|
| 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 →
generate_message ~214
Generate a schema-validated ISO 20022 E&I XML message from a record. Purpose: Renders a complete, XSD-compliant ISO 20022 XML document (e.g. camt.056 payment cancellation or camt.029 investigation resolution) from structured field dictionaries, validating the result against the bundled official schema before returning. When to use: - When raising payment cancellation, recall, or investigation response messages for interbank transmission. - When requiring guaranteed XSD-valid XML output for downstream payment processing. When NOT to use: - Do NOT use to validate pre-existing XML files without generating; use validate_xml instead. - Do NOT pass incomplete records; check get_required_fields first. Behavioral transparency: Pure template rendering and in-memory schema validation; side-effect-free and idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| message_type | string | yes | An E&I message type, e.g. 'camt.056.001.12' (see list_message_types). |
| record | object | yes | Message fields; see get_required_fields. |
Structured output declared, but exposes no named fields.
No examples provided.
get_required_fields ~157
Get required schema fields for an ISO 20022 E&I message type. Purpose: Returns the list of mandatory top-level data fields required to construct a valid message record (e.g. assignment identification, instruct team agent, and transaction arrays). When to use: - When preparing input payloads before calling generate_message. - When validating payload completeness prior to XML serialization. When NOT to use: - Do NOT use with unsupported message types; discover supported types via list_message_types. Behavioral transparency: Deterministic field dictionary lookup; pure, read-only, and idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| message_type | string | yes | An E&I message type, e.g. 'camt.056.001.12' (see list_message_types). |
Structured output declared, but exposes no named fields.
No examples provided.
list_message_types ~139
List supported ISO 20022 Exceptions & Investigations message types. Purpose: Returns the catalog of supported E&I message identifiers (e.g. camt.056.001.12 Payment Cancellation Request, camt.029.001.14 Resolution of Investigation) and their human-readable definitions. When to use: - When discovering valid message_type parameters before generating or validating messages. - When verifying schema version support for payment recall or resolution workflows. When NOT to use: - Do NOT use for payment initiation (pain) or statement (camt.053) messages. Behavioral transparency: Static catalogue retrieval; pure, deterministic, and side-effect-free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
validate_xml ~205
Validate raw ISO 20022 E&I XML against bundled XSD schemas. Purpose: Validates an XML string against the official bundled XSD schema for the specified E&I message type, returning validation status and detailed schema violation diagnostics. When to use: - When inspecting received or pre-generated ISO 20022 E&I XML before ingesting or routing. - When diagnosing schema structural, datatype, or constraint errors in message payloads. When NOT to use: - Do NOT use for payment initiation (pain) or statement (camt.053) documents. - Do NOT pass unparseable binary content; requires valid XML text. Behavioral transparency: Pure, in-memory schema validation using local bundled XSDs; zero network access or side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| message_type | string | yes | An E&I message type, e.g. 'camt.056.001.12' (see list_message_types). |
| xml | string | yes | Raw ISO 20022 XML to validate. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.sebastienrousseau/camt-exceptions MCP server?
io.github.sebastienrousseau/camt-exceptions runs locally as a PyPI package, launched with uvx camt-exceptions. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · camt-exceptions
claude mcp add sebastienrousseau-camt-exceptions -- uvx camt-exceptions
What is the io.github.sebastienrousseau/camt-exceptions MCP server?
io.github.sebastienrousseau/camt-exceptions is an MCP server listed in the public MCP registry as io.github.sebastienrousseau/camt-exceptions. Generate + XSD-validate ISO 20022 E&I camt messages (camt.056 cancellation, camt.029 resolution). This page covers its PyPI package (camt-exceptions).
Is the io.github.sebastienrousseau/camt-exceptions MCP server safe to use?
io.github.sebastienrousseau/camt-exceptions scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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/camt-exceptions MCP server expose?
io.github.sebastienrousseau/camt-exceptions exposes 4 tools: list_message_types, get_required_fields, generate_message, validate_xml. Their descriptions and schemas cost roughly 715 tokens of context every time the server is loaded.
Is the io.github.sebastienrousseau/camt-exceptions MCP server still maintained?
io.github.sebastienrousseau/camt-exceptions is still listed as active in the MCP registry. We last reached this channel on 5 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/camt-exceptions MCP server under?
io.github.sebastienrousseau/camt-exceptions 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.