io.github.sebastienrousseau/camt-exceptions
PYPI · CAMT-EXCEPTIONS · SCANNED SEP 20
Generate + XSD-validate ISO 20022 E&I camt messages (camt.056 cancellation, camt.029 resolution).
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 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 native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 36 dependencies flagged as unhealthy. View diagnostics → Pass
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 Usability84
- 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
- Tool/resource definitions use about 323 tokens (~64/item across 5 items; 4 tools + 1 resources), lean.Pass
- 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 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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
{
"mcpServers": {
"sebastienrousseau-camt-exceptions": {
"command": "uvx",
"args": [
"camt-exceptions"
]
}
}
} {
"servers": {
"sebastienrousseau-camt-exceptions": {
"command": "uvx",
"args": [
"camt-exceptions"
]
}
}
} codex mcp add sebastienrousseau-camt-exceptions -- uvx camt-exceptions
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sebastienrousseau-camt-exceptions": {
"type": "local",
"command": [
"uvx",
"camt-exceptions"
],
"enabled": true
}
}
} openclaw mcp add sebastienrousseau-camt-exceptions --command uvx --arg camt-exceptions
mcp_servers:
sebastienrousseau-camt-exceptions:
command: "uvx"
args: ["camt-exceptions"] {
"McpServers": {
"sebastienrousseau-camt-exceptions": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"camt-exceptions"
]
}
}
} assistant mcp add sebastienrousseau-camt-exceptions -t stdio -c uvx -a camt-exceptions
{
"mcpServers": {
"sebastienrousseau-camt-exceptions": {
"command": "uvx",
"args": [
"camt-exceptions"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 20 Sept 2026 · Analysed pypi/camt-exceptions@0.0.18
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 36 packages
| Packages resolved | 36 |
|---|---|
| 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 ~125
Generate a validated ISO 20022 E&I XML message from a record. For camt.056, the record cancels/recalls a previously sent payment (assignment ids + agent BICs + a list of 'transactions' with the original payment references and a cancellation reason code). Output is validated against the bundled XSD before it is returned.
| 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 ~54
Return the required top-level fields for an E&I message type.
| 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 ~38
List the supported ISO 20022 Exceptions & Investigations message types (e.g. camt.056 payment cancellation request) and their names.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
validate_xml ~81
Validate raw ISO 20022 XML against an E&I message type's bundled XSD; returns is_valid plus any schema errors.
| 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.
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 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 298 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 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/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.