Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.sebastienrousseau/iso20022-readiness-suite-mcp

PYPI · ISO20022-READINESS-SUITE-MCP

Orchestration MCP server: ISO 20022 readiness scoring, remediation, bank-response simulation.

0 this week 97 Trust /100

Last scanned (21 hours ago)

Scores higher than 99% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

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
  • 2 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-readiness-suite-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0 OR MIT).Pass
  • Actively maintained (last published 30 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
  • 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
  • Tool/resource definitions use about 389 tokens (~77/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 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
Changelog

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.

  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 0
    • Stability: pass → 0.97 functional
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 25 Oct 26 0
    • Stability: pass → 0.97 functional
  • 19 Oct 26 0
    • Stability: 0.97 → pass security
  • 17 Oct 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.

Diagnostics

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-readiness-suite-mcp@0.0.6

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-readiness-suite-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/sebastienrousseau/iso20022-readiness-suite-mcp/.github/workflows/release.yml@refs/tags/v0.0.6
Rekor log index 3077788152
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:caa383241f9f41f49dc32e72861e9754f198936dd06846cb85a9af2baaa4ecdd

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
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~349 tokens

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 →

Tool Tokens
list_profiles ~40

List the available clearing profiles (CBPR+, SEPA_Instant, ...). Use this to discover the ``target_profile`` values the other tools accept.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

remediate_payload ~79

Apply automated remediation (e.g. Nov 2026 structured addresses). Args: payload_content: The raw ISO 20022 message text. target_profile: The clearing profile driving the remediation policy.

NameTypeReqDescription
payload_contentstringyesRaw ISO 20022 payload text to remediate.
target_profilestring–Profile driving remediation.

Structured output declared, but exposes no named fields.

No examples provided.

run_readiness_check ~107

Detect, validate, profile-lint, and score a payload's readiness. Args: payload_content: The raw ISO 20022 message text. filename_hint: Optional original filename, for routing. target_profile: The clearing profile to lint against.

NameTypeReqDescription
filename_hint––Optional filename hint.
payload_contentstringyesRaw ISO 20022 payload text (not a path).
target_profilestring–Clearing profile to lint against (see list_profiles).

Structured output declared, but exposes no named fields.

No examples provided.

simulate_bank_response ~123

Emit a pacs.002 status report mocking a bank's response. Args: inbound_payload: The inbound initiation payload. desired_behavior: The status to simulate (ACCP / RJCT / PDNG). reason_code: The reason code (required when RJCT).

NameTypeReqDescription
desired_behaviorstringyesDesired outcome: 'ACCP', 'RJCT', or 'PDNG'.
inbound_payloadstringyesThe inbound initiation payload text.
reason_code––ISO status reason code, e.g. 'AM04'. Required for RJCT.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.sebastienrousseau/iso20022-readiness-suite-mcp server?

io.github.sebastienrousseau/iso20022-readiness-suite-mcp runs locally as a PyPI package, launched with uvx iso20022-readiness-suite-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-readiness-suite-mcp

# add to Claude Code
claude mcp add sebastienrousseau-iso20022-readiness-suite-mcp -- uvx iso20022-readiness-suite-mcp
Common questions

What is the io.github.sebastienrousseau/iso20022-readiness-suite-mcp server?

io.github.sebastienrousseau/iso20022-readiness-suite-mcp is listed in the public MCP registry as io.github.sebastienrousseau/iso20022-readiness-suite-mcp. Orchestration MCP server: ISO 20022 readiness scoring, remediation, bank-response simulation. This page covers its PyPI package (iso20022-readiness-suite-mcp).

Is the io.github.sebastienrousseau/iso20022-readiness-suite-mcp server safe to use?

io.github.sebastienrousseau/iso20022-readiness-suite-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-readiness-suite-mcp server expose?

io.github.sebastienrousseau/iso20022-readiness-suite-mcp exposes 4 tools: list_profiles, run_readiness_check, remediate_payload, simulate_bank_response. Their descriptions and schemas cost roughly 349 tokens of context every time the server is loaded.

Is the io.github.sebastienrousseau/iso20022-readiness-suite-mcp server still maintained?

io.github.sebastienrousseau/iso20022-readiness-suite-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-readiness-suite-mcp server under?

io.github.sebastienrousseau/iso20022-readiness-suite-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.