Evidence row 574552

What was observed

{
  "count": 3,
  "tools": [
    {
      "description": "Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the TheRundown API documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.\n\nThis is how you read documentation pages: there is no separate \"get page\" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`.\n\n**Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il \"keyword\" /` to find where it is covered.\n\n**Workflow:** Start with the search tool for broad or conceptual queries like \"how to authenticate\" or \"rate limiting\". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.\n\nSupported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage.\n\nEach call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call.\n\nExamples (replace the placeholder paths with real ones from `tree` or search):\n- `tree / -L 2` — see the top-level directory layout\n- `rg -il \"rate limit\" /` — find all files mentioning \"rate limit\"\n- `rg -C 3 \"apiKey\" /some-directory/` — show matches with 3 lines of context around each hit\n- `head -80 /some/page.mdx` — read the top 80 lines of a specific page\n- `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call\n- `cat /some/page.mdx` — read a full page when you need everything\n- `head -100 /openapi/openapi.yaml` — read the start of an OpenAPI spec\n\nOpenAPI specs for this site are mounted at: `/openapi/openapi.yaml`, `/openapi/tools/chatgpt-actions/openapi.yaml`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication.\n\nOutput is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 \"pattern\" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible.\n\nWhen referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "command": {
            "description": "A shell command to run against the virtualized documentation filesystem (e.g., `rg -il \"keyword\" /`, `tree / -L 2`, `head -80 /path/file.mdx`).",
            "type": "string"
          }
        },
        "required": [
          "command"
        ],
        "type": "object"
      },
      "name": "query_docs_filesystem_the_rundown_api"
    },
    {
      "description": "Search across the TheRundown API knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about TheRundown API, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "query": {
            "description": "Search query",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "type": "object"
      },
      "name": "search_the_rundown_api"
    },
    {
      "description": "Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "feedback": {
            "description": "A clear description of the documentation issue or suggestion — what is incorrect, outdated, missing, or confusing.",
            "minLength": 1,
            "type": "string"
          },
          "path": {
            "description": "The URL path of the documentation page the feedback is about (the page you were reading, without the `.mdx` extension).",
            "minLength": 1,
            "type": "string"
          }
        },
        "required": [
          "path",
          "feedback"
        ],
        "type": "object"
      },
      "name": "submit_feedback"
    }
  ]
}

What the leaf hashes

{"body":"5635b80ad171061edafc4e3d74c675e9eb5b1ddd2cd796149c6ebcd78d089d55","id":574552,"kind":"mcp.tools","method":"probe.mcp/1","observed_us":1793141578136951,"prev":null,"subject":"e06f7a07-d2ca-43c2-9058-8170d6ed6562","subject_kind":"endpoint"}

Proof

Fold these into the leaf in order, hashing each sorted pair with keccak256, to reach the root of 2026-10-27 (273461 rows).

1. 0x996a2c9cf28d233970e3002612a7ba3f6f2540cd896da57f8665bb30e81bfe44
2. 0x7c6feb9822ec33befc5af2c36f0ae9bddd460faa6d21066f0f6fe7e87119799d
3. 0x6789ead7a4ba0681df5005b5b85ff3700203e8e9a3996561df4778f1155ddd96
4. 0x3618bf7761c02491b9358e0f0f61861b9ada655809d78d10618116c9f9023c90
5. 0xbc13d5a98b5de64f7fd25a76227add600e9495f54751de25505c65dbe71e1e42
6. 0x2977ae39c471c32176aa8d5208eb417c4ad1ff29814bcab390b0d3632c95ec8c
7. 0x79aadbab086a1237e478e559bb9d248ea620e9d60ad92d2e5fc24c85f156acb6
8. 0x9ae9170d5a6a5b416c1628780c1ef6dd6d05962bcdcf8d93bb6095dda39fb28f
9. 0x958c41e2efbce04af91bcb1333624cb9c0ec93bf1454475a392ebe31fbd73cb9
10. 0xfafd7acbbf81c514ccd69cca332a22472485a9a7b44a7be505ade4139587597a
11. 0xa41abe253efa912fb9578616717d0a43d778c1509c3109fa4cfcc00433d8500d
12. 0xff66a3c0db6d61623a5ee399a8625355b32e95a4eb77e6d9f9ca4ae4dcbc5937
13. 0xfe6d2e9a468b7e99de9162a2ef30ac0b0e3b318387b4356bf524493aa67b295b
14. 0xa3c9c760ee424c178bab782711c2b9d3e15a80a6fde99165972cb75b306bb8b4
15. 0xb4f7223140c8a36cb87a63d77cf617086d9968dc4658f03e102571ebe06e9ed6
16. 0xfecf3d4646dd4984a13dd715499e842c3fde63692336d97394c2bfd8e877ca5d
17. 0xf30fddbf4811226c58e8f0daf36fddd79fc5f1356b592bb1d99a8061ddbabe66
18. 0x2bf8151e5f157dd183b9de6fa00469551932a7a6e3f33a694895000ac9061197
19. 0x9fc354c0ea3efc3f1b6548bb77ea902a50f2c9647647ea61592efce2bd795699

Day root

0xdd77e5e99da32c3f154180d63e3c3e6fe11e896a2c6896412ef6b5c4bcf7e795

Chained

0x23bb4dfd09f55c15ac3962f53578e02c6114d5bfd9bb451cf8794fb6e2817ef4

Published

On Arc Testnet, block 69414147: 0xb2ebd83aafeb765a0ce66e76aefb133ed06606c98038fd56191e2bcd1dcb77b4