ISO 20022 Navigator
REMOTE · MCP.ISONAVIGATOR.IO
Look up ISO 20022 messages, bank transaction codes, legacy MT replacements, schemes and code sets.
Available components
Last scanned (1 hour ago)
Scores higher than 85% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.93 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Nov 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.
- 2 Nov 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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 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.
- 27 Oct 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.
- 24 Oct 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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 5 Nov 2026 · Probed https://mcp.isonavigator.io/iso20022
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.isonavigator.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| isonavigator.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.isonavigator.io/iso20022 | Unreachable | ||
| http (plaintext) | http://mcp.isonavigator.io/iso20022 | HTTPS enforced |
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 →
iso20022_bank_transaction_codes ISO 20022 bank transaction codes ~445
Use for ANY question about ISO 20022 Bank Transaction Codes (BTC): the Domain / Family / SubFamily codes that classify entries in bank statements and account reports, such as PMNT, PMNT-RCDT or PMNT-RCDT-ESCT. Call it even when the code looks familiar: it returns the official names, descriptions and how the codes fit together. Send the code in one of these forms: - PMNT (a domain): its name and its families. - PMNT-RCDT (domain and family): both names and its subfamilies. - PMNT-RCDT-ESCT (all three): the three names and an explanation of the combination. - /RCDT (a family): its name, the domains it appears in and its subfamilies. - //ESCT (a subfamily): its name, the domains and families it appears in. - /RCDT/ESCT (family and subfamily): the domains where this pair exists. - PMNT//ESCT (domain and subfamily): the families under PMNT that contain ESCT. - ESCT (no level given): matched as a domain, a family and a subfamily; each level where it exists is returned separately. This tool matches codes, not meanings. To find the code for a type of transaction, browse from the domain down: PMNT, then its families, then their subfamilies. It covers the ISO external code list only; bank-specific (proprietary) codes are outside it. It has no information about message structure or how a bank fills in a code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | A Bank Transaction Code or part of one, written domain-family-subfamily with hyphens, e.g. 'PMNT-RCDT-ESCT'. Each part is four letters or digits. Begin with slashes to fix the level ('/RCDT' is a fam… |
| Name | Type | Req | Description |
|---|---|---|---|
| closest_paths | array | – | Not found only: up to 5 existing paths sharing a part with the input |
| found | boolean | yes | – |
| input | string | yes | The code as interpreted by the server, slash-separated by level, e.g. PMNT/RCDT, /RCDT, //ESCT |
| matches | array | – | – |
| notes | array | – | Caveats to pass on to the user |
| provenance | – | yes | – |
| segments | array | – | Not found only: where each part of the input exists in the ISO list |
No examples provided.
iso20022_code_sets ISO 20022 code sets ~546
Use for ANY question about ISO 20022 external code sets: the values of a code set (BalanceType, ReturnReason, Purpose, StatusReason, ...), what a code means (CLBD, OTHR, ...), whether a code is valid in a code set, which code sets a message uses (camt.053, pain.001, ...), or which messages use a code set. Call it even when the answer seems well known: it returns the sourced, current values with their official descriptions and flags deactivated ones. Send one identifier in `message`: - A code set (BalanceType, or ExternalBalanceType1Code): its description, its values (code, name, description) and the messages that use it. Add `code` to check a single value. - A code (CLBD): every code set that contains it, with the name and description in each. - An ISO 20022 message (camt.053): the code sets it uses, with their number of values. The values, code sets and matches are pipe-delimited text with a header row. Long lists are paged by whole rows: when `page.complete` is false, call again with the same input and the offset in `page.next_offset` until it is true, before answering about the whole list. Not covered: Bank Transaction Codes (PMNT, PMNT-RCDT-ESCT; use iso20022_bank_transaction_codes), which ISO 20022 message replaces a legacy message or which schemes use one (use iso20022_legacy_and_scheme_mappings), and what a message itself contains. Code set usage is message-level, not element-level. The code set description (concept_description) is AI-generated.
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | Optional, only when message is a code set: check one code in that set, e.g. message 'BalanceType' with code 'CLBD'. Returns just that value, so use it for 'is X a valid ...' questions instead of fetc… |
| message | string | yes | A code set (e.g. 'BalanceType', or its full name 'ExternalBalanceType1Code'), a code (e.g. 'CLBD', 'OTHR'), or an ISO 20022 message (e.g. 'camt.053', 'pacs.008.001.08'). |
| offset | integer | – | Row to start from; 0 (the default) is the first row. Use only to continue a list whose previous response said it was not complete, with the next_offset from that response. |
| Name | Type | Req | Description |
|---|---|---|---|
| code_set | – | – | Attributes of the code set (input_kind code_set) |
| code_sets | – | – | input_kind message: the code sets the message uses, pipe-delimited, one row per line. First line is the header: concept|navigator_group|code_count. code_count is the number of current values. |
| found | boolean | yes | – |
| input | string | yes | The identifier as interpreted by the server: the code set's short name, the ISO 20022 message, or the code |
| input_kind | string | yes | – |
| iso20022_deactivated_in | – | – | Navigator data load (quarter) in which the input message was marked deactivated; absent if current |
| iso20022_message_name | – | – | Name of the ISO 20022 message, when the input is one |
| matches | – | – | input_kind code: every code set containing the code, pipe-delimited, one row per line. First line is the header: concept|code|name|description|deactivated_in. |
| notes | array | – | Caveats to pass on to the user |
| page | – | – | Paging of the pipe-delimited list. Continue with next_offset until complete is true. |
| provenance | – | yes | – |
| used_in_messages | array | – | input_kind code_set: IDs of the messages (all variants) that use this code set. Complete on every page. |
| values | – | – | input_kind code_set: the values, pipe-delimited, one row per line. First line is the header: code|name|description|deactivated_in. deactivated_in is empty for current values. |
No examples provided.
iso20022_legacy_and_scheme_mappings ISO 20022 legacy and scheme mappings ~435
Use for ANY question about what replaces or corresponds to a legacy payment message (SWIFT MT such as MT103, MT202, MT940; NACHA; CHAPS), or which payment schemes use an ISO 20022 message (pacs.008, pain.001, pain.008, camt.053; SEPA, NPP, CHAPS, Lynx, CIPS and others). Call it even when the answer seems well known: it returns sourced, current mappings with status and caveats. For "which schemes use X", call once with only the message: the response lists every recorded scheme (without descriptions, to keep it compact). Omit `standard` unless the user names one scheme; with `standard`, the response includes that scheme's description. - Legacy input (MT103, 940, ACH Statement): returns its ISO 20022 equivalent(s) in legacy_equivalents. - ISO 20022 input (pacs.008): returns legacy_equivalents (legacy messages that map to it) and used_by_schemes (schemes that use it). Mappings are message-level only; this tool does not map individual fields and has no information about a message's structure, elements or rules. Do not cite it for those. ISO 20022 messages that have been retired are returned flagged with iso20022_deactivated_in, not hidden.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | A legacy message (e.g. 'MT103', 'MT 202COV', '940', 'ACH Statement') or an ISO 20022 message (e.g. 'pacs.008', 'camt.053.001.08'). |
| standard | – | – | Omit (or leave empty) unless the user names one specific standard or scheme. Omitted returns every recorded scheme and legacy equivalent in one call; do not use this to check schemes one by one. Exam… |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| input | string | yes | The message identifier as interpreted by the server |
| input_kind | string | yes | – |
| iso20022_deactivated_in | – | – | Navigator data load (quarter) in which the input message was marked deactivated; absent if current |
| iso20022_message_name | – | – | Name of the ISO 20022 message, when the input is one |
| legacy_equivalents | array | – | Legacy or non-ISO messages (SWIFT MT, NACHA, CHAPS legacy) and their ISO 20022 equivalent |
| notes | array | – | Caveats to pass on to the user |
| provenance | – | yes | – |
| used_by_schemes | array | – | Payment schemes that use this ISO 20022 message |
No examples provided.
iso20022_message_details ISO 20022 message details ~315
Use for ANY question about what an ISO 20022 message is: its official name, purpose, business area, latest version, and the size and shape of its structure. Send a message identifier such as pacs.008, camt.053 or pain.001. Call it even when the message looks familiar: it returns the official name, a plain-English description, the business area and domain, the Navigator's own functional grouping, whether the message is retired, structure statistics (total elements, maximum depth, element counts at each depth) and the number of external code sets the message uses. Covers the standard variant (variant 1) of each message, at the latest version held. For legacy equivalents (SWIFT MT, NACHA, CHAPS) and the schemes that use a message, use iso20022_legacy_and_scheme_mappings. For the list of code sets a message uses, use iso20022_code_sets (the response's next_calls names it).
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | An ISO 20022 message identifier: four letters and three digits, e.g. 'pacs.008' or 'camt.053'. Any case works, and a hyphen, underscore, space or no separator also works ('pacs-008', 'pacs008'). A fu… |
| Name | Type | Req | Description |
|---|---|---|---|
| business_area | – | – | – |
| closest_ids | array | – | Not found only: up to 5 held messages in the same business area, nearest number first |
| code_set_count | – | – | Number of external code sets the message uses |
| deactivated_in | – | – | Navigator data load (quarter) in which this message was marked deactivated; absent if current |
| description | – | – | AI-generated plain-English description of the message. |
| found | boolean | yes | – |
| input | string | yes | The message identifier as interpreted by the server, e.g. pacs.008 |
| latest_version | – | – | Full identifier of the latest version held, e.g. camt.053.001.14 |
| name | – | – | Official message name, e.g. BankToCustomerAccountReport |
| navigator_group | – | – | The Navigator's own functional grouping of messages. It is not part of the ISO 20022 standard. |
| next_calls | array | – | Follow-up calls that return related data too large to include here, each with the tool and the arguments to send; absent when there is nothing to follow up |
| notes | array | – | Caveats to pass on to the user |
| provenance | – | yes | – |
| structure | – | – | Size and shape of the message definition; absent when no structure is held |
No examples provided.
How do I install the ISO 20022 Navigator MCP server?
ISO 20022 Navigator is a hosted endpoint at https://mcp.isonavigator.io/iso20022, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.isonavigator.io
claude mcp add --transport http kreativemanish-iso20022-navigator 'https://mcp.isonavigator.io/iso20022'
What is the ISO 20022 Navigator MCP server?
ISO 20022 Navigator is an MCP server listed in the public MCP registry as io.github.kreativeManish/iso20022-navigator. Look up ISO 20022 messages, bank transaction codes, legacy MT replacements, schemes and code sets. This page covers its hosted endpoint (https://mcp.isonavigator.io/iso20022).
Is the ISO 20022 Navigator MCP server safe to use?
ISO 20022 Navigator scores 82 out of 100 on VerifyMCP. 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 ISO 20022 Navigator MCP server expose?
ISO 20022 Navigator exposes 4 tools: iso20022_bank_transaction_codes, iso20022_message_details, iso20022_legacy_and_scheme_mappings, iso20022_code_sets. Their descriptions and schemas cost roughly 1,741 tokens of context every time the server is loaded.
Does the ISO 20022 Navigator MCP server require authentication?
Its publisher declares no required credentials for ISO 20022 Navigator. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ISO 20022 Navigator MCP server still maintained?
ISO 20022 Navigator is still listed in the MCP registry, though our most recent checks did not reach this channel. 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.