_ registry / mcp streamable-http · checked 1h ago

iso20022-navigator

https://mcp.isonavigator.io

Registry code: 6c9e5f1720496c2e

api record

Read-only reference data for ISO 20022 financial messaging, from the ISO 20022 Navigator (https://www.isonavigator.io/iso20022/). Use these tools for any question about which ISO 20022 message replaces or corresponds to a legacy message (SWIFT MT, NACHA, CHAPS legacy), or which payment schemes use an ISO 20022 message, even when the answer seems well known: they return sourced, current data. For 'which schemes use X', call once without a standard filter. Answer from the returned data. If a response has found=false or notes saying data is not recorded, tell the user so; do not fill gaps from…

endpoint
https://mcp.isonavigator.io/iso20022
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is iso20022-navigator live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is iso20022-navigator free to use?
Yes — the hub reached it with no key and no payment.
What tools does iso20022-navigator have?
1 tool: iso20022_legacy_and_scheme_mappings.
Is iso20022-navigator safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
432ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 1 tools
1 never probed 0 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • iso20022_legacy_and_scheme_mappings unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "find_mappingsArguments",
      "required": [
        "message"
      ],
      "properties": {
        "message": {
          "type": "string",
          "title": "Message",
          "pattern": "^[A-Za-z0-9 .\\-/()]+$",
          "maxLength": 40,
          "minLength": 2,
          "description": "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": {
          "anyOf": [
            {
              "type": "string",
              "pattern": "^[A-Za-z0-9 _+/()\\-]*$",
              "maxLength": 30
            },
            {
              "type": "null"
            }
          ],
          "title": "Standard",
          "default": null,
          "description": "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. Examples when the user names one: 'SWIFT_MT', 'SEPA', 'NPP', 'CHAPS'."
        }
      }
    }
    arguments 32 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6c9e5f1720496c2e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6c9e5f1720496c2e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6c9e5f1720496c2e/badge.svg)](https://brick.blue/agent/6c9e5f1720496c2e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
50%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.