The ISO 20022 Organization periodically republishes its official eRepository — the canonical source for every message definition, business component, code set, and validation rule in the standard. On September 4, 2026, they published a new snapshot, and our MCP server has already been updated to match it, moving up from the previous June 26, 2026 edition.
If that sounds like inside baseball, here’s the short version: our AI assistant’s knowledge of ISO 20022 is only as good as the data it’s built on. Every time the standards body publishes a refresh, we pull it in so that whatever your AI tool tells you — a field name, a data type, a constraint, whether a code is still valid — reflects the current official specification, not a stale copy from months ago.
What actually changed
Between June and September, the standard picked up:
- 1,397 new elements — new message fields, new links between business concepts, 7 new message components, 31 new code sets, and 2 new choice types
- 242 updates to existing definitions — clarified wording, corrected constraints, and similar refinements
- 34 retirements — elements formally removed from the spec, including a handful of superseded message-set groupings, rather than whole message types
That’s a bigger batch than our last update, spanning a longer ~10-week window — but it’s the same ordinary churn for a living international standard, not a disruption.
By the numbers
As of this update, the repository our server draws from contains:
- 3,340 message definitions, spanning payments, securities, trade services, cards, foreign exchange, and more, across 36 business areas
- 24,275 supporting structures underneath those — message components, code sets, business components, choice types, and simple data types
- 99%+ schema coverage — nearly every current message definition has a matching XML schema our tooling can point you to directly; the handful of known gaps (mostly provisional or access-restricted message types) haven’t grown with this update
Why this matters, even if you never think about it
Most people using an AI assistant through our MCP server won’t ever notice this update happened — and that’s the point. It should just work, and the answers you get should quietly reflect whichever version of the standard is actually current. That’s the promise: connect once, and the knowledge underneath stays fresh without you having to do anything.
If you haven’t connected your AI assistant to the ISO 20022 MCP server yet, now’s as good a time as any — you’ll be starting from the latest the standard has to offer.