addrbookFor publishers
← The evidence ledger

Evidence row 578093

Observed , by probe.mcp/1.

Kind
mcp.tools
About
endpoint cb476194-2712-4325-a057-4c6fadadbb31
Recorded
Previous row
None: the first of its kind about this subject
Body SHA-256
384a6dcfc846f6d43d9258ec3cc33cd63d37a17eef7f40c53c930bab7c10fa64
Leaf
0xab571e0522e9049380f9f759acefba3a52c0361d570d55c258c2980765cce850

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 Altss Data & Agent Docs documentation pages. 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\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_altss_data_agent_docs"
    },
    {
      "description": "Search across the Altss Data & Agent Docs knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Altss Data & Agent Docs, 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_altss_data_agent_docs"
    },
    {
      "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":"384a6dcfc846f6d43d9258ec3cc33cd63d37a17eef7f40c53c930bab7c10fa64","id":578093,"kind":"mcp.tools","method":"probe.mcp/1","observed_us":1793142856053909,"prev":null,"subject":"cb476194-2712-4325-a057-4c6fadadbb31","subject_kind":"endpoint"}

Proof

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

  1. 0xab57535ce64e87917e81232be2920859428dde72c14b03610942bedfc7159775
  2. 0x9faf2a2dc81b3be2f902876c48fff94278d5395c9236ebc8711dafeafcf17a27
  3. 0x1d813be19ae3511d8b2d2acfbfddb0c707fe181de42047355b760edabc35ec7f
  4. 0x34034dae3ae241042357e4ff97d1a4a09c91dea1f901861049c29d927d716212
  5. 0x3f7db979b4183979655a0ee5424218d53a51542c86d3339609bd4ba839df696b
  6. 0x991670901889f0ba8fce9dd905d5732cd5f84c228dfd5a0aff6839c7cb0c2e7f
  7. 0xdf4873a9a308dbf63c8f4915ba425b405ecefca39d7ecd1f48713f7c4c5444fc
  8. 0x4189c2b4f1b332feef75aff99838428c188e3df88c6b8c9d2a69c22b719a8492
  9. 0x8e3e9fcb61e0d1220281c20dd9ab84d28834ba04c9064ab60eb52af589d5c55a
  10. 0x4cbda852ccf1b96ff7c1de04eb698405e76be19d87a3deb7262011796e29b6d7
  11. 0x59cb41ec7d9ac9c74e0f576f6d9ea1041f1f440ad9c2ec9f6107b51d598a3ef5
  12. 0xe58ece954b3b0e80c16db5967815baeb4102983fd3dbc48dbb6146da839f558b
  13. 0x5e700087f2a5e8fb7372f2c2db037d66942006d666bb45dd92f745011295fa7b
  14. 0x98c6ed3e7b5bb7f1757a8660af410226a11dd563bf83010040c2ce059ab45e54
  15. 0xec7bb68216a4deb1960acfbbd75da88f7e468b58adb9cf3ec62f2790e46508b3
  16. 0x64c405a28e8819716221eb2529fe4ce277ab08025e17e685cbd5ece75ceb75c7
  17. 0xf30fddbf4811226c58e8f0daf36fddd79fc5f1356b592bb1d99a8061ddbabe66
  18. 0x2bf8151e5f157dd183b9de6fa00469551932a7a6e3f33a694895000ac9061197
  19. 0x9fc354c0ea3efc3f1b6548bb77ea902a50f2c9647647ea61592efce2bd795699
Day root
0xdd77e5e99da32c3f154180d63e3c3e6fe11e896a2c6896412ef6b5c4bcf7e795
Chained
0x23bb4dfd09f55c15ac3962f53578e02c6114d5bfd9bb451cf8794fb6e2817ef4
Published
On Arc Testnet, block 69414147: 0xb2ebd83aafeb765a0ce66e76aefb133ed06606c98038fd56191e2bcd1dcb77b4

How to check it · This row as JSON