io.github.sebastienrousseau/iso20022-evidence-pack-mcp
PYPI · ISO20022-EVIDENCE-PACK-MCP · SCANNED SEP 20
MCP server: seal & sign ISO 20022 readiness evidence into tamper-evident audit packs.
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
- 1 of 35 dependencies flagged as unhealthy. 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 Usability83
- 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
- Context-footprint check failed: tool/resource definitions use about 1492 tokens (~114/item across 13 items; 11 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 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
How do I install the io.github.sebastienrousseau/iso20022-evidence-pack-mcp server?
io.github.sebastienrousseau/iso20022-evidence-pack-mcp runs locally as a PyPI package, launched with uvx iso20022-evidence-pack-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-evidence-pack-mcp
claude mcp add sebastienrousseau-iso20022-evidence-pack-mcp -- uvx iso20022-evidence-pack-mcp
{
"mcpServers": {
"sebastienrousseau-iso20022-evidence-pack-mcp": {
"command": "uvx",
"args": [
"iso20022-evidence-pack-mcp"
]
}
}
} {
"servers": {
"sebastienrousseau-iso20022-evidence-pack-mcp": {
"command": "uvx",
"args": [
"iso20022-evidence-pack-mcp"
]
}
}
} codex mcp add sebastienrousseau-iso20022-evidence-pack-mcp -- uvx iso20022-evidence-pack-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sebastienrousseau-iso20022-evidence-pack-mcp": {
"type": "local",
"command": [
"uvx",
"iso20022-evidence-pack-mcp"
],
"enabled": true
}
}
} openclaw mcp add sebastienrousseau-iso20022-evidence-pack-mcp --command uvx --arg iso20022-evidence-pack-mcp
mcp_servers:
sebastienrousseau-iso20022-evidence-pack-mcp:
command: "uvx"
args: ["iso20022-evidence-pack-mcp"] {
"McpServers": {
"sebastienrousseau-iso20022-evidence-pack-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"iso20022-evidence-pack-mcp"
]
}
}
} assistant mcp add sebastienrousseau-iso20022-evidence-pack-mcp -t stdio -c uvx -a iso20022-evidence-pack-mcp
{
"mcpServers": {
"sebastienrousseau-iso20022-evidence-pack-mcp": {
"command": "uvx",
"args": [
"iso20022-evidence-pack-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.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 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.
- 16 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.
- 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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/iso20022-evidence-pack-mcp@0.0.5
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 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 →
build_evidence_pack Build an evidence pack ~120
Fold readiness, remediation, and simulations into a sealed pack. Args: readiness_content: A readiness result, as JSON text. remediation_content: An optional remediation result, as JSON text. simulation_content: An optional JSON array of simulated responses. metadata: Free-form audit metadata (institution, reference, ...).
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | – | – | Free-form audit metadata. |
| readiness_content | string | yes | A readiness result as raw JSON text. |
| remediation_content | – | – | Optional remediation JSON text. |
| simulation_content | – | – | Optional simulated-responses JSON. |
Structured output declared, but exposes no named fields.
No examples provided.
export_pack_to_s3 Export a pack to Amazon S3 ~188
Upload a signed evidence pack to Amazon S3. **Requires the ``[aws]`` extra** (``pip install iso20022-evidence-pack-mcp[aws]``) and **reaches AWS S3 over the network** -- unlike the closed-world tools, this one has a network surface. Only the ``s3://`` scheme is supported; ``gs://`` / ``az://`` return a clear error. Returns the object's ``bucket``, ``key``, and ``etag``. Args: signed_pack_json: The signed pack to upload, as JSON text. s3_uri: The destination, of the form ``s3://bucket/key``.
| Name | Type | Req | Description |
|---|---|---|---|
| s3_uri | string | yes | Destination of the form s3://bucket/key. |
| signed_pack_json | string | yes | A signed evidence pack as raw JSON text. |
Structured output declared, but exposes no named fields.
No examples provided.
render_markdown Render an evidence pack ~50
Render an evidence pack as a markdown compliance report. Args: pack_content: The evidence pack to render, as JSON text.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_content | string | yes | An evidence pack as raw JSON text. |
Structured output declared, but exposes no named fields.
No examples provided.
seal_pack Seal an evidence pack ~51
Compute the deterministic SHA-256 seal for an evidence pack. Args: pack_content: The evidence pack to seal, as JSON text.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_content | string | yes | An evidence pack as raw JSON text. |
Structured output declared, but exposes no named fields.
No examples provided.
sign_pack Sign an evidence pack ~120
Sign a pack's canonical content with the server's Ed25519 key. The private key is configured by the operator via the environment (see :mod:`iso20022_evidence_pack_mcp.signing`); it never crosses the tool boundary. Returns the detached signature, the public key, and a key id; fails with ``EP_NO_SIGNING_KEY`` when no key is configured. Args: pack_content: The evidence pack to sign, as JSON text.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_content | string | yes | An evidence pack as raw JSON text. |
Structured output declared, but exposes no named fields.
No examples provided.
sign_pack_aws_kms Sign a pack with AWS KMS ~204
Sign a pack's SHA-256 canonical digest with AWS KMS. **Requires the ``[aws]`` extra** (``pip install iso20022-evidence-pack-mcp[aws]``) and **reaches AWS KMS over the network** -- unlike the closed-world tools, this one has a network surface. The private key never leaves KMS; the tool submits only the pack's digest. Returns the pack with an ``aws_kms_signature`` block attached. Args: evidence_pack_json: The evidence pack to sign, as JSON text. key_arn: The ARN of the KMS ``SIGN_VERIFY`` key. aws_region: The AWS region hosting the key.
| Name | Type | Req | Description |
|---|---|---|---|
| aws_region | string | – | The AWS region. |
| evidence_pack_json | string | yes | An evidence pack as raw JSON text. |
| key_arn | string | yes | The ARN of the KMS SIGN_VERIFY key. |
Structured output declared, but exposes no named fields.
No examples provided.
sign_pack_vault Sign a pack with Vault Transit ~212
Sign a pack's canonical bytes with HashiCorp Vault Transit. **Requires the ``[vault]`` extra** (``pip install iso20022-evidence-pack-mcp[vault]``) and **reaches a Vault server over the network** -- unlike the closed-world tools, this one has a network surface. POSTs to ``/v1/transit/sign/{key_name}`` and returns the pack with a ``vault_signature`` block attached. Args: evidence_pack_json: The evidence pack to sign, as JSON text. vault_url: The base URL of the Vault server. key_name: The Transit key to sign with. token: The Vault access token.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_pack_json | string | yes | An evidence pack as raw JSON text. |
| key_name | string | yes | The Transit key name to sign with. |
| token | string | yes | The Vault access token. |
| vault_url | string | yes | The base URL of the Vault server. |
Structured output declared, but exposes no named fields.
No examples provided.
verify_cosign_signature Verify a cosign signature ~180
Verify a container image signature with ``cosign``. **Reaches an external system**: shells out to a locally installed ``cosign`` binary (which contacts the registry and transparency log). No optional Python extra is required, but the binary must be on ``PATH`` -- otherwise the tool returns an ``EP_EXTERNAL_TOOL`` error. For keyless verification, supply ``certificate_identity`` and ``certificate_oidc_issuer``. Args: image_ref: The container image reference to verify. certificate_identity: The keyless certificate identity (optional). certificate_oidc_issuer: The keyless OIDC issuer URL (optional).
| Name | Type | Req | Description |
|---|---|---|---|
| certificate_identity | – | – | Keyless certificate identity. |
| certificate_oidc_issuer | – | – | Keyless OIDC issuer URL. |
| image_ref | string | yes | The container image reference to verify. |
Structured output declared, but exposes no named fields.
No examples provided.
verify_pack_signature Verify an evidence-pack signature ~106
Verify a detached Ed25519 signature over a pack's canonical content. Args: pack_content: The evidence pack to check, as JSON text. signature: The base64-encoded detached signature. public_key: The signer's PEM public key.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_content | string | yes | An evidence pack as raw JSON text. |
| public_key | string | yes | The signer's PEM public key. |
| signature | string | yes | The base64 Ed25519 signature to check. |
Structured output declared, but exposes no named fields.
No examples provided.
verify_seal Verify an evidence-pack seal ~82
Recompute a pack's seal and compare it to an expected digest. Args: pack_content: The evidence pack to check, as JSON text. expected_digest: The seal the pack is expected to carry.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_digest | string | yes | The seal to check the pack against. |
| pack_content | string | yes | An evidence pack as raw JSON text. |
Structured output declared, but exposes no named fields.
No examples provided.
verify_slsa_provenance Verify SLSA provenance ~146
Verify an artifact's SLSA provenance with ``slsa-verifier``. **Reaches an external system**: shells out to a locally installed ``slsa-verifier`` binary (which may fetch metadata). No optional Python extra is required, but the binary must be on ``PATH`` -- otherwise the tool returns an ``EP_EXTERNAL_TOOL`` error. Args: artifact_path: Path to the artifact whose provenance is checked. provenance_path: Path to the SLSA provenance attestation.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_path | string | yes | Path to the artifact to verify. |
| provenance_path | string | yes | Path to the SLSA provenance attestation. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.sebastienrousseau/iso20022-evidence-pack-mcp server?
io.github.sebastienrousseau/iso20022-evidence-pack-mcp is listed in the public MCP registry as io.github.sebastienrousseau/iso20022-evidence-pack-mcp. MCP server: seal & sign ISO 20022 readiness evidence into tamper-evident audit packs. This page covers its PyPI package (iso20022-evidence-pack-mcp).
Is the io.github.sebastienrousseau/iso20022-evidence-pack-mcp server safe to use?
io.github.sebastienrousseau/iso20022-evidence-pack-mcp scores 87 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/iso20022-evidence-pack-mcp server expose?
io.github.sebastienrousseau/iso20022-evidence-pack-mcp exposes 11 tools: build_evidence_pack, seal_pack, verify_seal, render_markdown, sign_pack, and 6 more. Their descriptions and schemas cost roughly 1,459 tokens of context every time the server is loaded.
Is the io.github.sebastienrousseau/iso20022-evidence-pack-mcp server still maintained?
io.github.sebastienrousseau/iso20022-evidence-pack-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-evidence-pack-mcp server under?
io.github.sebastienrousseau/iso20022-evidence-pack-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.