MCP.Market

Camt Exceptions MCP server

by sebastienrousseau·io.github.sebastienrousseau/camt-exceptions·v0.0.20·1 stars

Generate + XSD-validate ISO 20022 E&I camt messages (camt.056 cancellation, camt.029 resolution).

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

1 stars84 downloads/wk

Reviews

Write one

Nobody has reviewed Camt Exceptions yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Camt Exceptions tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • Code scan8 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Camt Exceptions compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
84
more than 59% of 12,191 servers with a package

Release history: 2 versions in the registry since 2026-08-29, latest 2026-10-04, typically one every 36 days.

Install Camt Exceptions in Claude Code, Cursor or VS Code

claude mcp add camt-exceptions -- uvx camt-exceptions
Add to Cursor

What the publisher says

From the Camt Exceptions repository's README, as published. We do not edit it. Read it on GitHub

camt-exceptions: ISO 20022 Exceptions & Investigations, generated + XSD-valid

Generate and validate ISO 20022 Exceptions & Investigations (E&I) camt messages — with an [MCP][mcp] server. Starts with camt.056 (FI-to-FI Payment Cancellation Request): the message a bank sends to recall or cancel a payment it already dispatched — a duplicate, an erroneous amount, a fraud recall. Output is validated against the official bundled XSD before it's returned.

Latest release: v0.0.18 — camt.056 + camt.029 generation + validation, 4 MCP

tools over stdio, streamable HTTP or SSE, 100% branch coverage, for Python 3.10+. Part of the

ISO 20022 MCP suite. Additional E&I messages (camt.029, camt.026,

camt.027, camt.087) plug into the same engine.

Why E&I

When a payment goes wrong, the fix is an Exceptions & Investigations message — and these are the least tooled corner of ISO 20022. camt.056 alone covers the single most common need: "I need to cancel/recall that payment." This library makes it a one-call, schema-valid operation for an agent, with the same depth as the credit-transfer generators elsewhere in the suite.

Install

pip install camt-exceptions
# or run the MCP server without installing:
uvx camt-exceptions

MCP client config (e.g. Claude Desktop):

{
  "mcpServers": {
    "camt-exceptions": {
      "command": "camt-exceptions-mcp"
    }
  }
}

Quick start — cancel a payment

from camt_exceptions import generator as g

xml = g.generate_message("camt.056.001.12", {
    "assignment_id": "CXL-001",
    "assigner_agent_bic": "DEUTDEFF",
    "assignee_agent_bic": "COBADEFF",
    "creation_date_time": "2026-03-02T10:00:00",
    "original_msg_id": "MSG-ORIG-001",
    "original_msg_nm_id": "pacs.008.001.08",
    "transactions": [{
        "original_end_to_end_id": "E2E-001",
        "original_interbank_settlement_amount": "1000.00",
        "original_interbank_settlement_currency": "EUR",
        "cancellation_reason_cd": "DUPL",       # duplicate payment
    }],
})
assert g.validate_xml("camt.056.001.12", xml)["is_valid"]   # True

Transports

One command line, three transports:

--host and --port change the bind address (defaults 127.0.0.1 and 8000). The HTTP transports carry no authentication of their own: bind loopback, or put the server behind a gateway you trust before binding a routable address. Every release is verified over streamable HTTP with scout in both protocol eras and over SSE with the MCP SDK client; see ADR 0001.

{
  "mcpServers": {
    "camt-exceptions": { "url": "http://127.0.0.1:8000/mcp" }
  }
}

Tools

  • listmessagetypes — List supported E&I message types and names.
  • getrequiredfields — Required top-level fields for a message type.
  • generate_message — Generate a validated E&I XML message from a record (validated against the bundled XSD before return).
  • validate_xml — Validate raw XML against a message type's bundled XSD.

Supported messages

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Camt Exceptions: common questions

Is Camt Exceptions MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Camt Exceptions safety report
How do I install Camt Exceptions?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Camt Exceptions need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Camt Exceptions maintained?
The last commit was 7 days ago (2026-10-28). The latest release is v0.0.20.
How does Camt Exceptions compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers); downloads a week 84 (more than 59% of 12,191 servers with a package). Full comparison.

More from sebastienrousseau →