Evidence row 1253321

What was observed

{
  "count": 4,
  "tools": [
    {
      "description": "Get one news event in detail. A cluster is a single real-world event grouped from the outlets covering it and deduplicated into one item, so you get one event rather than 20 near-duplicate headlines. Returns its summary, a significance score (1 to 10, where 8 and above is exceptional), a source count, the situation it belongs to if any, and links to its source articles (outlet, headline, URL and date). It returns up to 100 of those links, one per outlet; `sources` and `articles_total` are the full count, and `articles_truncated` says whether the list was cut. Use this when the user wants the specifics of one event. Get a cluster id from search_situations, get_situation_timeline, or a clstr.news URL. Results carry canonical clstr.news links. (Requires sign-in, or a free API key: https://clstr.news/developers)",
      "inputSchema": {
        "properties": {
          "articles": {
            "description": "How many source articles to return, 1 to 100. Default 100. Lower it when you only need a few citations; the source count is reported separately and is unaffected.",
            "maximum": 100,
            "minimum": 1,
            "type": "integer"
          },
          "cluster_id": {
            "description": "Cluster id or slug (from timelines, search, or clstr.news URLs).",
            "type": "string"
          }
        },
        "required": [
          "cluster_id"
        ],
        "type": "object"
      },
      "name": "get_cluster"
    },
    {
      "description": "Get the full chronological timeline of one situation. A situation is an ongoing storyline (story arc) that groups related news events over time; it carries a maintained summary plus every event in order, so you see not just what happened but how it developed. Each event is a cluster (one happening grouped from the outlets covering it and deduplicated) with its date, a significance score (1 to 10, where 8 and above is exceptional), a source count, and a canonical clstr.news link. Use this to brief on a story's history or answer 'how did this develop'. Get a situation id from search_situations or get_top_situations, or from a clstr.news URL. An id that was retired when two situations merged resolves to the successor, flagged with merged_into_shown. Results carry canonical clstr.news links.",
      "inputSchema": {
        "properties": {
          "situation_id": {
            "description": "Situation id or slug (from other tools or clstr.news URLs).",
            "type": "string"
          },
          "timeline_before": {
            "description": "Cursor: cluster id (a UUID) from a previous page, to continue past it.",
            "type": "string"
          },
          "timeline_limit": {
            "description": "Timeline entries to return, newest first. Default 50, and 50 is also the maximum without an API key. A free key raises it to 500: https://clstr.news/developers",
            "maximum": 50,
            "minimum": 1,
            "type": "integer"
          }
        },
        "required": [
          "situation_id"
        ],
        "type": "object"
      },
      "name": "get_situation_timeline"
    },
    {
      "description": "List the situations developing now, ranked by relevance: a blend of significance, how many outlets are covering it, and how recently it moved. So a lower significance score can rank above a higher one, and that ordering is intentional; do not re-sort. A situation is an ongoing storyline that groups related news events over time and carries a maintained summary and a source count (how many outlets are behind it). Optionally filter by category, by country, and by time window (24h, 7d, or 30d), and switch the ordering to newest activity first with sort. Use this to answer 'what is going on in the world', 'what is happening in <category>' or 'what is happening in <country>' when there is no specific topic yet, then open any result with get_situation_timeline. When there are more, the result ends with a cursor to page further. Pass summary: \"full\" to get each situation's maintained summary in full, instead of a one-line preview, without a follow-up call per result; full summaries in a list are not enabled for every account, so read summary_mode in the result to see what you got, and use get_situation_timeline for one situation's summary in full. Results carry canonical clstr.news links.",
      "inputSchema": {
        "properties": {
          "category": {
            "description": "Optional category filter.",
            "enum": [
              "politics",
              "business",
              "technology",
              "health",
              "sports",
              "culture",
              "international",
              "crime"
            ],
            "type": "string"
          },
          "country": {
            "description": "Optional country filter: comma-separated ISO 3166-1 alpha-2 codes, for example \"US,GB\". Up to 10 at once. A situation matches if any of them is among the countries most directly involved in it.",
            "maxLength": 200,
            "type": "string"
          },
          "cursor": {
            "description": "From a previous result, to page further. Pass the same filters alongside it: a cursor resumes only under the filter set that produced it.",
            "type": "string"
          },
          "limit": {
            "description": "Max situations to return. Default 15.",
            "maximum": 25,
            "minimum": 1,
            "type": "integer"
          },
          "sort": {
            "description": "Ordering. 'relevance' (the default) blends significance, source count and recency; 'recent' is newest activity first.",
            "enum": [
              "relevance",
              "recent"
            ],
            "type": "string"
          },
          "summary": {
            "description": "How much summary text each row carries. 'preview' (the default) is a one-line preview; 'full' returns the maintained summary in full, so you do not need a follow-up call per result. On get_top_situations, 'full' is not enabled for every account: read `summary_mode` in the result to see which mode was actually served, and get_situation_timeline always returns one situation's summary in full. 'full' returns each situation's full summary, up to roughly 300 words per row, so keep limit small when you use it.",
            "enum": [
              "preview",
              "full"
            ],
            "type": "string"
          },
          "window": {
            "description": "Time window. Default '7d'.",
            "enum": [
              "24h",
              "7d",
              "30d"
            ],
            "type": "string"
          }
        },
        "required": [],
        "type": "object"
      },
      "name": "get_top_situations"
    },
    {
      "description": "Search the news by topic to find matching situations and events. A situation is an ongoing storyline (story arc) that groups related events over time; an event, called a cluster, is one happening grouped from the outlets covering it and deduplicated into a single item, so you get one event rather than 20 near-duplicate headlines. Results come back grouped under their situations, each with a one-line summary, a significance score (1 to 10, where 8 and above is exceptional), a source count (how many outlets are covering it), and a canonical clstr.news link. Use this to answer 'what is happening around X' for a topic, company, country, or event. Then open a result with get_situation_timeline for the full history, or get_cluster for one event's detail. Results are relevance ordered and bounded to the top matches: when there are more, the result ends with a cursor to pass back, and each page counts as one search against your cap. Pass summary: \"full\" to read each match's summary untruncated instead of one line. Results carry canonical clstr.news links. (Requires sign-in, or a free API key: https://clstr.news/developers)",
      "inputSchema": {
        "properties": {
          "cursor": {
            "description": "From a previous result, to page further. Each page counts as one search against your cap.",
            "type": "string"
          },
          "days": {
            "description": "How far back to search, in days. Default 7, maximum 30.",
            "maximum": 30,
            "minimum": 1,
            "type": "integer"
          },
          "limit": {
            "description": "Max events to return. Default 15. They are grouped under their situations in the result, so you may see fewer situation headings than this number.",
            "maximum": 25,
            "minimum": 1,
            "type": "integer"
          },
          "query": {
            "description": "Topic, entity, company, country, or event to search for.",
            "maxLength": 200,
            "type": "string"
          },
          "summary": {
            "description": "How much summary text each row carries. 'preview' (the default) is a one-line preview; 'full' returns the maintained summary in full, so you do not need a follow-up call per result. On get_top_situations, 'full' is not enabled for every account: read `summary_mode` in the result to see which mode was actually served, and get_situation_timeline always returns one situation's summary in full.",
            "enum": [
              "preview",
              "full"
            ],
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "type": "object"
      },
      "name": "search_situations"
    }
  ]
}

What the leaf hashes

{"body":"f7eb31630990d575f17c70f11ed5120a320325d07a224f88774798fae2de3308","id":1253321,"kind":"mcp.tools","method":"probe.mcp/1","observed_us":1793370224867371,"prev":994478,"subject":"651c6ad6-cbdb-476b-8c42-11e9b1511dd7","subject_kind":"endpoint"}

Proof

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

1. 0xf10614695a61600f59b62fafe9df7f0a9291807fcbb26e100cb81b9797be3817
2. 0xb4afbd23761bd125a2e41f2fbd0760c80b7da9670c80df74b1486be69e552ae8
3. 0xc0f2f008e7f906ac63e8627fbfafa5e9b1cdb7c6d5b785c8753b0d407022f00c
4. 0xcec948161f769b7054f586b59cc5304d07af0642a39be349f1fb0176717d8b6a
5. 0xdc20e87013fa66c707b4faab9afa9ffd9660b7d8978087ea5a8279c2be922cac
6. 0xf05813423b575b249e23b0edea4d648ec867d7d6205f2a681504a5041ba2bfef
7. 0xe52d561697e8a820b582c61d15849fa91dbfaf7e769ea2b0386ca45b2efd61ad
8. 0xbd2574ada1f44ea2bb9e174c973c8584a9a087308aeff6437e0be40b2b5e653c
9. 0xa85d2593fa3732d323d3bb22fb635012f03fd587c9038bc4bfd60ce42d0a715a
10. 0x4ac06f3cd01c5587334b6a76ba55f5ebc7de3b9affb8a46777b7adb925a140a6
11. 0xe8b2f34d78a80d68a94901a043ec0994789ee90d95f468bf5419cbb5fba90e8d
12. 0xc247113275f237f2f9e15b483fa3de5f93b830cd85dc9fe32752fddec37d4c7f
13. 0xc4d1aa4c86009997771d234f361d697ff280913322c529b9c4472470f727e868
14. 0x480837169e0b2dae12e25a5963879f1d41492816181ac128eeca59bf75b8d55d
15. 0xea7df1002501052c124b5aed2b1a5df3d59be54394c6a8539c86fad1df339a9e
16. 0xfbe61dc2d59668ac573e5eab865747e21d38bf2fe4c64762beef01f1018a4dea
17. 0x71e74c274b23c9047354edb6dcd2c654415e3986b8bd875dae992996ea12e22b
18. 0x0c43c73b62a5d49ee1444b5dc4195fc5b16b141d3f4458e2e9fbd5fd6ecb367d

Day root

0x0826c7ad6039e06a2360ca0a4a3a4fe7f2626c6dc19f71a37599386f78b39875

Chained

0x36b4c8a1063758f0b8765fa1bdf75fa92fb543cc183add3e261880ee2bd1f822

Published

On Arc Testnet, block 69923247: 0x8704744146c6967c8abc9e9a99de4db7283b29e840922ea83a69b6fe776e6861