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/structured-address-fix-mcp

PYPI · STRUCTURED-ADDRESS-FIX-MCP · SCANNED SEP 20

MCP server for ISO 20022 postal-address remediation ahead of the Nov 2026 CBPR+ cliff.

+4 this week 68 Trust /100
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 Security49
  • Malware scan not yet available for this package.Unverified
  • 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
  • 3 of 33 dependencies flagged as unhealthy (1 deprecated). 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 Usability82
  • 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 2474 tokens (~164/item across 15 items; 13 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 Management77
  • Stability observed for 23 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
Install

How do I install the io.github.sebastienrousseau/structured-address-fix-mcp server?

io.github.sebastienrousseau/structured-address-fix-mcp runs locally as a PyPI package, launched with uvx structured-address-fix-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 · structured-address-fix-mcp

# add to Claude Code
claude mcp add sebastienrousseau-structured-address-fix-mcp -- uvx structured-address-fix-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "sebastienrousseau-structured-address-fix-mcp": {
      "command": "uvx",
      "args": [
        "structured-address-fix-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sebastienrousseau-structured-address-fix-mcp": {
      "command": "uvx",
      "args": [
        "structured-address-fix-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add sebastienrousseau-structured-address-fix-mcp -- uvx structured-address-fix-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sebastienrousseau-structured-address-fix-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "structured-address-fix-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sebastienrousseau-structured-address-fix-mcp --command uvx --arg structured-address-fix-mcp
# ~/.hermes/config.yaml
mcp_servers:
  sebastienrousseau-structured-address-fix-mcp:
    command: "uvx"
    args: ["structured-address-fix-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sebastienrousseau-structured-address-fix-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "structured-address-fix-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add sebastienrousseau-structured-address-fix-mcp -t stdio -c uvx -a structured-address-fix-mcp
// mcp.json
{
  "mcpServers": {
    "sebastienrousseau-structured-address-fix-mcp": {
      "command": "uvx",
      "args": [
        "structured-address-fix-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 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.

  • 13 Sept 26 +1
    • Security disclosure: unverified → pass functional
  • 12 Sept 26 −1
    • Security disclosure: pass → unverified functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 20 Sept 2026 · Analysed pypi/structured-address-fix-mcp@0.0.4

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 33 packages
Packages resolved 33
Deprecated 1
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~2,433 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
assess_address ~253

Score a single address against a policy and return its findings. Args: address: The postal address to assess. policy_id: The policy to assess against (defaults to cbpr-2026). as_of: The assessment date (YYYY-MM-DD); defaults to today. country_hint: Country to assume when the address has none.

NameTypeReqDescription
addressobjectyesAn ISO 20022 postal address as a JSON object using canonical field names, e.g. {'street_name': 'Downing St', 'building_number': '10', 'post_code': 'SW1A 2AA', 'town_name': 'London', 'country': 'GB'}…
as_ofThe assessment date as an ISO 8601 string (YYYY-MM-DD). Decides cliff wording; defaults to today.
country_hintISO 3166-1 alpha-2 hint when the address has no country of its own.
policy_idThe policy to assess against (see list_policies). Defaults to 'cbpr-2026' when omitted.

Structured output declared, but exposes no named fields.

No examples provided.

assess_message ~143

Assess every addressed party in a pacs.008 / pain.001 message. Args: xml: The ISO 20022 message document. policy_id: The policy to assess against (defaults to cbpr-2026). as_of: The assessment date (YYYY-MM-DD); defaults to today.

NameTypeReqDescription
as_ofThe assessment date as an ISO 8601 string (YYYY-MM-DD). Decides cliff wording; defaults to today.
policy_idThe policy to assess against (see list_policies). Defaults to 'cbpr-2026' when omitted.
xmlstringyesAn ISO 20022 message as XML.

Structured output declared, but exposes no named fields.

No examples provided.

classify_address ~158

Classify a postal address as structured, hybrid, or unstructured. Use this for a quick shape check before deciding whether to remediate. For the specific compliance findings under a policy, use ``assess_address`` instead. Args: address: The postal address to classify.

NameTypeReqDescription
addressobjectyesAn ISO 20022 postal address as a JSON object using canonical field names, e.g. {'street_name': 'Downing St', 'building_number': '10', 'post_code': 'SW1A 2AA', 'town_name': 'London', 'country': 'GB'}…

Structured output declared, but exposes no named fields.

No examples provided.

explain_finding ~59

Explain what a finding code means and how to resolve it. Args: code: The finding code to explain.

NameTypeReqDescription
codestringyesA finding code, e.g. 'SAF001' (see the codes in any assessment result).

Structured output declared, but exposes no named fields.

No examples provided.

get_cutover_date ~203

Report when the structured-address requirement binds, if it yet does. Swift accepted a community request on 27 August 2026 and deferred every payments change in Standards Release 2026, the structured-address requirement among them. No replacement date has been set; Swift will confirm timing by December 2026 at the latest. ``date`` is therefore ``None``. It is left null rather than filled with the withdrawn date because an agent reading this hands the answer to somebody planning a migration, and a date with no force is worse than no date at all. The requirement itself was agreed by the community in 2023 and stands: ``status`` says deferred, not withdrawn. The deferral is Swift's, and covers CBPR+. Domestic market infrastructures set their own timing and several were aligned to the same November date; check the schemes you settle through rather than assuming they moved with Swift.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_policies ~88

List every available address policy (rulebook) with its tier. Use this first to discover the ``policy_id`` values the other tools accept (e.g. ``cbpr-2026``, ``sepa``, ``hvps-plus``, ``generic-structured``). Returns a list of ``{"id": ..., "title": ..., "tier": ...}`` objects.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultyes

No examples provided.

normalize_country_code ~174

Resolve a country name or code to its ISO 3166-1 alpha-2 code. Accepts English names, common local-language endonyms (Deutschland, España, Nippon), everyday aliases (UK, USA, Holland, UAE), and existing 2- or 3-letter codes. Matching is case-, accent-, and punctuation- insensitive. Args: country_name_or_code: The country name, alias, or code to resolve. Returns a ``{"country_code": "DE"}`` object, or ``{"error": ...}`` when the input matches no known country.

NameTypeReqDescription
country_name_or_codestringyesA country name, endonym, alias, or 2/3-letter code, e.g. 'Deutschland', 'UK', 'U.S.A.', 'DEU'.

Structured output declared, but exposes no named fields.

No examples provided.

parse_address_libpostal ~279

Parse a free-text address into ISO 20022 postal fields. Uses the optional libpostal statistical parser (the ``postal`` binding, which requires the system libpostal C library) when it is installed, and otherwise degrades to this repo's own regex heuristics. Either way the address is mapped to ``StrtNm``, ``BldgNb``, ``PstCd``, ``TwnNm`` and ``Ctry``. The result's ``parser`` field is ``"libpostal"`` or ``"fallback"`` so callers know which path ran. Runs purely on CPU with no network or filesystem access, though the libpostal path depends on an external C library. Args: unstructured_address: The free-text address to parse. country_hint: Country to assume when the text names none. Returns ``{"parser": ..., "address": {StrtNm, BldgNb, PstCd, TwnNm, Ctry}}``.

NameTypeReqDescription
country_hintAn ISO 3166-1 alpha-2 hint (or country name) used when the address text does not name its own country.
unstructured_addressstringyesA single free-text postal address, e.g. '12 Rue de Rivoli, 75001 Paris, France'.

Structured output declared, but exposes no named fields.

No examples provided.

preview_patch ~140

Return the patch operations remediation would apply (a dry run). Args: xml: The ISO 20022 message document. policy_id: The policy to remediate for (defaults to cbpr-2026). as_of: The assessment date (YYYY-MM-DD); defaults to today.

NameTypeReqDescription
as_ofThe assessment date as an ISO 8601 string (YYYY-MM-DD). Decides cliff wording; defaults to today.
policy_idThe policy to assess against (see list_policies). Defaults to 'cbpr-2026' when omitted.
xmlstringyesAn ISO 20022 message as XML.
NameTypeReqDescription
resultyes

No examples provided.

remediate_address ~280

Propose the compliant form of an address, with explained changes. Returns the findings, the before/after addresses, and the patch operations (each carrying the finding it resolves, the source token, and a confidence score). Args: address: The postal address to remediate. policy_id: The policy to remediate for (defaults to cbpr-2026). as_of: The assessment date (YYYY-MM-DD); defaults to today. country_hint: Country to assume when the address has none.

NameTypeReqDescription
addressobjectyesAn ISO 20022 postal address as a JSON object using canonical field names, e.g. {'street_name': 'Downing St', 'building_number': '10', 'post_code': 'SW1A 2AA', 'town_name': 'London', 'country': 'GB'}…
as_ofThe assessment date as an ISO 8601 string (YYYY-MM-DD). Decides cliff wording; defaults to today.
country_hintISO 3166-1 alpha-2 hint.
policy_idThe policy to assess against (see list_policies). Defaults to 'cbpr-2026' when omitted.

Structured output declared, but exposes no named fields.

No examples provided.

remediate_message ~175

Assess and remediate every addressed party in a message. Args: xml: The ISO 20022 message document. policy_id: The policy to remediate for (defaults to cbpr-2026). apply: Whether to apply the operations and return patched XML. as_of: The assessment date (YYYY-MM-DD); defaults to today.

NameTypeReqDescription
applybooleanWhen true, apply the operations and return the patched XML in 'patched_xml'.
as_ofThe assessment date as an ISO 8601 string (YYYY-MM-DD). Decides cliff wording; defaults to today.
policy_idThe policy to assess against (see list_policies). Defaults to 'cbpr-2026' when omitted.
xmlstringyesAn ISO 20022 message as XML.

Structured output declared, but exposes no named fields.

No examples provided.

split_street_and_building ~207

Split a street line into street name, building, and sub-building. Handles the leading-number convention (US/UK: ``10 Downing Street``), the trailing-number convention (much of continental Europe: ``Rue de Rivoli 12``), and an optional sub-building marker (``Flat 2``, ``Apt 3B``, ``Suite 400``). When no building number is present the whole line is returned as ``street_name`` (never an error). Args: street_line: The free-text street line to split. Returns ``{"street_name", "building_number", "sub_building"}`` with ``building_number`` / ``sub_building`` set to ``null`` when absent.

NameTypeReqDescription
street_linestringyesA single free-text street line, e.g. '10 Downing Street', 'Rue de Rivoli 12', or 'Flat 2, 221B Baker Street'.

Structured output declared, but exposes no named fields.

No examples provided.

validate_postal_policy ~274

Validate an address's post_code against a country's format policy. Supported policies: US (5-digit ZIP or ZIP+4), GB (alphanumeric UK postcode), DE and FR (5 digits), JP (3-then-4 digits). The address is a canonical-field JSON object; only its ``post_code`` is inspected. Args: address: The structured address whose post_code to validate. country_code: The alpha-2 code selecting the policy. Returns ``{"is_compliant": bool, "policy_errors": [...]}``. An unknown country or a missing post_code is reported as non-compliant with a descriptive error rather than raising.

NameTypeReqDescription
addressobjectyesAn ISO 20022 postal address as a JSON object using canonical field names, e.g. {'street_name': 'Downing St', 'building_number': '10', 'post_code': 'SW1A 2AA', 'town_name': 'London', 'country': 'GB'}…
country_codestringyesThe ISO 3166-1 alpha-2 code whose post_code policy to apply (US, GB, DE, FR, JP).

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.sebastienrousseau/structured-address-fix-mcp server?

io.github.sebastienrousseau/structured-address-fix-mcp is listed in the public MCP registry as io.github.sebastienrousseau/structured-address-fix-mcp. MCP server for ISO 20022 postal-address remediation ahead of the Nov 2026 CBPR+ cliff. This page covers its PyPI package (structured-address-fix-mcp).

Is the io.github.sebastienrousseau/structured-address-fix-mcp server safe to use?

io.github.sebastienrousseau/structured-address-fix-mcp scores 68 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/structured-address-fix-mcp server expose?

io.github.sebastienrousseau/structured-address-fix-mcp exposes 13 tools: list_policies, classify_address, assess_address, assess_message, remediate_address, and 8 more. Their descriptions and schemas cost roughly 2,433 tokens of context every time the server is loaded.

Is the io.github.sebastienrousseau/structured-address-fix-mcp server still maintained?

io.github.sebastienrousseau/structured-address-fix-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/structured-address-fix-mcp server under?

io.github.sebastienrousseau/structured-address-fix-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.