addrbookFor publishers
← The evidence ledger

Evidence row 257913

Observed , by probe.mcp/1.

Kind
mcp.tools
About
endpoint 987bd58e-b2b3-4244-b9c5-9bfd7093fab3
Recorded
Previous row
None: the first of its kind about this subject
Body SHA-256
38c3d0521903d525cc55a6efec90075d356346d870cb962d4c79ef464b6903bd
Leaf
0x42e7a05f4005fafd03a0af057a5c89c24578cd6de3fd6abc20fd4627a1f048a8

What was observed

{
  "count": 4,
  "tools": [
    {
      "description": "Use for ANY question about ISO 20022 Bank Transaction Codes (BTC): the Domain / Family /\nSubFamily codes that classify entries in bank statements and account reports, such as PMNT,\nPMNT-RCDT or PMNT-RCDT-ESCT. Call it even when the code looks familiar: it returns the\nofficial names, descriptions and how the codes fit together.\n\nSend the code in one of these forms:\n- PMNT (a domain): its name and its families.\n- PMNT-RCDT (domain and family): both names and its subfamilies.\n- PMNT-RCDT-ESCT (all three): the three names and an explanation of the combination.\n- /RCDT (a family): its name, the domains it appears in and its subfamilies.\n- //ESCT (a subfamily): its name, the domains and families it appears in.\n- /RCDT/ESCT (family and subfamily): the domains where this pair exists.\n- PMNT//ESCT (domain and subfamily): the families under PMNT that contain ESCT.\n- ESCT (no level given): matched as a domain, a family and a subfamily; each level\n  where it exists is returned separately.\n\nThis tool matches codes, not meanings. To find the code for a type of transaction, browse\nfrom the domain down: PMNT, then its families, then their subfamilies. It covers the ISO\nexternal code list only; bank-specific (proprietary) codes are outside it. It has no\ninformation about message structure or how a bank fills in a code.\n",
      "inputSchema": {
        "properties": {
          "code": {
            "description": "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 family, '//ESCT' is a subfamily) and leave a level empty to skip it ('PMNT//ESCT'). Slash, comma or space also work as separators.",
            "maxLength": 30,
            "minLength": 1,
            "pattern": "^[A-Za-z0-9 ,./_\\-]+$",
            "title": "Code",
            "type": "string"
          }
        },
        "required": [
          "code"
        ],
        "title": "find_transaction_codesArguments",
        "type": "object"
      },
      "name": "iso20022_bank_transaction_codes"
    },
    {
      "description": "Use for ANY question about ISO 20022 external code sets: the values of a code set (BalanceType,\nReturnReason, Purpose, StatusReason, ...), what a code means (CLBD, OTHR, ...), whether a code is\nvalid in a code set, which code sets a message uses (camt.053, pain.001, ...), or which messages\nuse a code set. Call it even when the answer seems well known: it returns the sourced, current\nvalues with their official descriptions and flags deactivated ones.\n\nSend one identifier in `message`:\n- A code set (BalanceType, or ExternalBalanceType1Code): its description, its values (code, name,\n  description) and the messages that use it. Add `code` to check a single value.\n- A code (CLBD): every code set that contains it, with the name and description in each.\n- An ISO 20022 message (camt.053): the code sets it uses, with their number of values.\n\nThe values, code sets and matches are pipe-delimited text with a header row. Long lists are paged\nby whole rows: when `page.complete` is false, call again with the same input and the offset in\n`page.next_offset` until it is true, before answering about the whole list.\n\nNot covered: Bank Transaction Codes (PMNT, PMNT-RCDT-ESCT; use iso20022_bank_transaction_codes),\nwhich ISO 20022 message replaces a legacy message or which schemes use one (use\niso20022_legacy_and_scheme_mappings), and what a message itself contains. Code set usage is\nmessage-level, not element-level. The code set description (concept_description) is AI-generated.\n",
      "inputSchema": {
        "properties": {
          "code": {
            "anyOf": [
              {
                "maxLength": 10,
                "pattern": "^[A-Za-z0-9 ._+\\-/()]*$",
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "description": "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 fetching the whole set.",
            "title": "Code"
          },
          "message": {
            "description": "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').",
            "maxLength": 60,
            "minLength": 1,
            "pattern": "^[A-Za-z0-9 .\\-/()_]+$",
            "title": "Message",
            "type": "string"
          },
          "offset": {
            "default": 0,
            "description": "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.",
            "maximum": 100000,
            "minimum": 0,
            "title": "Offset",
            "type": "integer"
          }
        },
        "required": [
          "message"
        ],
        "title": "find_code_setsArguments",
        "type": "object"
      },
      "name": "iso20022_code_sets"
    },
    {
      "description": "Use for ANY question about what replaces or corresponds to a legacy payment message\n(SWIFT MT such as MT103, MT202, MT940; NACHA; CHAPS), or which payment schemes use an\nISO 20022 message (pacs.008, pain.001, pain.008, camt.053; SEPA, NPP, CHAPS, Lynx, CIPS\nand others). Call it even when the answer seems well known: it returns sourced, current\nmappings with status and caveats.\n\nFor \"which schemes use X\", call once with only the message: the response lists every\nrecorded scheme (without descriptions, to keep it compact). Omit `standard` unless the\nuser names one scheme; with `standard`, the response includes that scheme's description.\n\n- Legacy input (MT103, 940, ACH Statement): returns its ISO 20022 equivalent(s)\n  in legacy_equivalents.\n- ISO 20022 input (pacs.008): returns legacy_equivalents (legacy messages that map to\n  it) and used_by_schemes (schemes that use it).\n\nMappings are message-level only; this tool does not map individual fields and has no\ninformation about a message's structure, elements or rules. Do not cite it for those.\nISO 20022 messages that have been retired are returned flagged with\niso20022_deactivated_in, not hidden.\n",
      "inputSchema": {
        "properties": {
          "message": {
            "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').",
            "maxLength": 40,
            "minLength": 2,
            "pattern": "^[A-Za-z0-9 .\\-/()]+$",
            "title": "Message",
            "type": "string"
          },
          "standard": {
            "anyOf": [
              {
                "maxLength": 30,
                "pattern": "^[A-Za-z0-9 _+/()\\-]*$",
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "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'.",
            "title": "Standard"
          }
        },
        "required": [
          "message"
        ],
        "title": "find_mappingsArguments",
        "type": "object"
      },
      "name": "iso20022_legacy_and_scheme_mappings"
    },
    {
      "description": "Use for ANY question about what an ISO 20022 message is: its official name, purpose, business\narea, latest version, and the size and shape of its structure. Send a message identifier such\nas pacs.008, camt.053 or pain.001. Call it even when the message looks familiar: it returns the\nofficial name, a plain-English description, the business area and domain, the Navigator's own\nfunctional grouping, whether the message is retired, structure statistics (total elements,\nmaximum depth, element counts at each depth) and the number of external code sets the message uses.\n\nCovers the standard variant (variant 1) of each message, at the latest version held. For legacy\nequivalents (SWIFT MT, NACHA, CHAPS) and the schemes that use a message, use\niso20022_legacy_and_scheme_mappings. For the list of code sets a message uses, use\niso20022_code_sets (the response's next_calls names it).\n",
      "inputSchema": {
        "properties": {
          "message_id": {
            "description": "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 full identifier with variant and version ('pacs.008.001.13') is accepted; the response gives the latest version held and notes any difference.",
            "maxLength": 24,
            "minLength": 7,
            "pattern": "^ *[A-Za-z]{4}[ ._\\-]?[0-9]{3}([ ._\\-][0-9]{3}([ ._\\-][0-9]{2})?)? *$",
            "title": "Message Id",
            "type": "string"
          }
        },
        "required": [
          "message_id"
        ],
        "title": "get_message_detailsArguments",
        "type": "object"
      },
      "name": "iso20022_message_details"
    }
  ]
}

What the leaf hashes

{"body":"38c3d0521903d525cc55a6efec90075d356346d870cb962d4c79ef464b6903bd","id":257913,"kind":"mcp.tools","method":"probe.mcp/1","observed_us":1793029820707246,"prev":null,"subject":"987bd58e-b2b3-4244-b9c5-9bfd7093fab3","subject_kind":"endpoint"}

Proof

Fold these into the leaf in order, hashing each sorted pair with keccak256, to reach the root of (296695 rows).

  1. 0x42e822fac210b4918e4e3c966eca179602b8f674a14e01970ef340c29aa59159
  2. 0x110945c11c528ef95878eabacd60823fadd527a545d70421e657fe507ecfa8f6
  3. 0xbca41f449214ce4bf6c7dcaf1aae1196dd1e017637b62466f9bcbe920412d2d0
  4. 0x7016ce41b24f192df26f07a972e4e8c9c25f7b977c3bafea289c524dcb50356f
  5. 0xac2e730978c06ca93d367616c3c4a28cfd23cc2993638551fa2ae3e7ae6c86f1
  6. 0x56c6b12126a163c31fdd8ca8458d66f8d72d3726cceb691978265c2e9bab1691
  7. 0x3265f0416610b9ecdb908b33e3a90477b791b3a1fa080f23f6b222b8b1c5e374
  8. 0x9f43eb8a618013b4272c656207c98697a0af93823f1738a0e2e05168abc33695
  9. 0x5ca33861f9ff5c729505165c540f038bde12f94c4e993e4a54d39fe9d51c4199
  10. 0xc268ff3f1dd69d7c668cdb05ded405db6f682a95f21c57e98e683c14e6e2ff89
  11. 0x5209b44231d259fd8508722a1ae64f1b73c7b7f19b456b1ecd950d5b281c35b6
  12. 0x58f4330f9ac32da273a2a76d85bc0768d037638cddbd3d1f09d9b64094bfd942
  13. 0xd406739acce2ba016f8d49081b15f266a4ea4a0b0fc5ef171c89c8fd2dda4d80
  14. 0x8b27a4c21bf4ba962fd008c8f4300bc6953764a5032b9ab0cfe696b318c45326
  15. 0x4b52a97f7a80ff7778a702b85267b8d2e5c93ce160942656435c29ae7be68bf4
  16. 0x2e6a32eb32761c210560e852405e2f865f958ddbe01027894f8b9c1b3433b9f0
  17. 0x9a83be955a206deb65b995adfd92c58fa31c95fbbf926bd199d300e70b08b26d
  18. 0x20704208aa6923d6b2450ef74ede87a6e0265d46447926038fe9506e9e154b2d
  19. 0x9b9ce5b74b9bab5121612ef6b64920a8d453cbf311096a423eef9702747e868a
Day root
0xf43e8dcc3d451a4788b26be904c55e8c4c0fa75c9666796c51db38d37e2c0df8
Chained
0x702d5ac508f08b0d1accf36af25822d8e5660367494edd17a642fb61e158a57a
Published
On Arc Testnet, block 69251483: 0x495162f8936e19f0039918feebe6c307f327cd6bf8c37219620b1970041fa9ae

How to check it · This row as JSON