{
  "notice": "bxzxxr MCP archive: a record of what public MCP servers declared when we listed them (we never call their tools). It is data, not a rating: nothing here says a server is safe, secure, verified or trustworthy, and a server can change after we looked. Secrets we detected are redacted; redacted tool lists are withheld and only their hash is shown.",
  "infrastructure": {
    "host": "trip2g.com",
    "site": "trip2g.com",
    "addresses": [
      {
        "address": "178.128.251.52",
        "endpoints": 1,
        "shared_infrastructure": false,
        "network": {
          "asn": 14061,
          "name": "DIGITALOCEAN-ASN - DigitalOcean, LLC",
          "prefix": "178.128.240.0/20",
          "country": "US"
        }
      }
    ],
    "addresses_recorded": true,
    "address_history": [
      {
        "addresses": [
          "178.128.251.52"
        ],
        "first_seen": "2026-11-21T17:24:01.617Z",
        "last_seen": "2026-11-22T21:20:04.303Z",
        "checks": 2
      }
    ],
    "hosting": [],
    "software": [],
    "server_info": {
      "name": "trip2g-mcp",
      "version": "1.0.0",
      "protocol_version": "2025-06-18"
    },
    "headers": {
      "server": "fasthttp"
    },
    "auth": null
  },
  "related": {
    "same_address": {
      "total": 0,
      "sample": []
    },
    "same_site": {
      "total": 0,
      "sample": []
    },
    "same_tool_list": {
      "total": 0,
      "sample": []
    },
    "same_publisher": {
      "publisher": "io.github.trip2g",
      "total": 0,
      "sample": []
    },
    "same_repository": {
      "repository_url": "https://github.com/trip2g/trip2g",
      "total": 0,
      "sample": []
    },
    "note": "Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators."
  },
  "endpoint": {
    "id": "40406",
    "server_name": "io.github.trip2g/trip2g",
    "url": "https://trip2g.com/_system/mcp",
    "host": "trip2g.com",
    "transport": "streamable-http",
    "last_checked_at": "2026-11-22T21:20:04.303Z",
    "last_state": "listed",
    "last_detail": null,
    "consecutive_failures": 0,
    "current_sha": "1f880fcf06ae671979fa25d42d8898cf29a5c4f156c58342d8cf63340b8ff7ae",
    "first_listed_at": "2026-11-21T17:24:01.617Z",
    "created_at": "2026-11-21T12:15:03.940Z",
    "resolved_addresses": [
      "178.128.251.52"
    ]
  },
  "server": {
    "name": "io.github.trip2g/trip2g",
    "title": "trip2g",
    "description": "Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.",
    "version": "1.0.0",
    "registry_status": "active",
    "repository_url": "https://github.com/trip2g/trip2g",
    "website_url": "https://trip2g.com",
    "published_at": "2026-07-19T06:25:01.899Z",
    "updated_at": "2026-07-19T06:25:01.899Z",
    "first_seen": "2026-11-21T12:15:02.847Z"
  },
  "other_endpoints": [],
  "intel": {
    "capabilities": [],
    "evm_addresses": [],
    "chains": [],
    "tokens": [],
    "computed_at": "2026-11-22T15:52:06.498Z"
  },
  "operator": {
    "key": "trip2g.com",
    "name": "trip2g.com",
    "platform": false
  },
  "needs_sign_in": false,
  "reachability": {
    "window_days": 30,
    "checks": 2,
    "answered": 2,
    "answered_percent": 100,
    "avg_listing_latency_ms": 790,
    "first_check_in_window": "2026-11-21T17:24:01.617Z",
    "consecutive_failures_now": 0,
    "days": [
      {
        "day": "2026-11-21",
        "checks": 1,
        "answered": 1,
        "last_state": "listed"
      },
      {
        "day": "2026-11-22",
        "checks": 1,
        "answered": 1,
        "last_state": "listed"
      }
    ]
  },
  "tool_list": {
    "sha256": "1f880fcf06ae671979fa25d42d8898cf29a5c4f156c58342d8cf63340b8ff7ae",
    "tools": 12,
    "resources": 0,
    "prompts": 0,
    "first_seen": "2026-11-21T17:24:02.388Z",
    "tool_names": [
      "expand",
      "federated_asset",
      "federated_expand",
      "federated_instructions",
      "federated_note_html",
      "federated_search",
      "federated_similar",
      "instructions",
      "note_html",
      "search",
      "similar",
      "wiki"
    ],
    "declared": {
      "tools": [
        {
          "name": "expand",
          "description": "Walk a note's table of contents level by level (progressive disclosure). Canonical call: expand(path=<result.note_path>, toc_path=[...]) — copy path verbatim from a search result's note_path field. Returns the direct children of a TOC node: omit toc_path (or pass []) for the top-level sections, or pass a toc_path to list that section's subsections. Each child has title, level, path, and has_children. A section with subsections lists them; a section without subsections is returned in full (what note_html gives for that toc_path, plus section_html in the payload), so no second call is needed to read a leaf. This cannot be turned off, and a client that wants only structure never triggers it: has_children on each listed child says where descending would turn into reading.",
          "inputSchema": {
            "type": "object",
            "properties": {
              "pid": {
                "type": "number",
                "description": "Non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id. Prefer path"
              },
              "href": {
                "type": "string",
                "description": "String note href, copied verbatim from a search result's href field"
              },
              "last": {
                "type": "number",
                "description": "List only this many of the newest subsections instead of all of them. A note that gains a dated section a day has hundreds of them after a year, and reading the whole listing to reach the latest few is the cost this avoids. The summary, total_children and omitted say what was left out, so a bounded listing never reads as a complete one. Bounds that meet or overlap return everything rather than repeating a run."
              },
              "path": {
                "type": "string",
                "description": "String note path, e.g. \"concepts/maska-i-glubina.md\" — copy verbatim from a search result's note_path field. The default, preferred way to reference a note"
              },
              "first": {
                "type": "number",
                "description": "List only this many of the oldest subsections. Pair it with last to get how a subject started and where it stands now, leaving out the middle; the summary marks the gap where it falls."
              },
              "note_id": {
                "type": "number",
                "description": "Same as pid: non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id. Prefer path"
              },
              "toc_path": {
                "type": "array",
                "items": {
                  "type": "string"
                },
                "description": "Breadcrumb path to the node to expand, e.g. [\"Chapter 1\"]. Omit or [] for the top level."
              }
            }
          }
        },
        {
          "name": "federated_asset",
          "description": "Get one attachment of a remote note — a file, not text. Canonical loop: federated_note_html(kb_id, path) -> for each name in its assets: federated_asset(kb_id, note_path=<that path>, name=<name>). Returns the asset's size and sha256 and a short-lived download URL on this server that streams the file from the remote base; fetch it with curl (the URL needs no other credential) and check the sha256. The file itself never comes back in the tool result. Only a directly connected base: kb_id without '/'.",
          "inputSchema": {
            "type": "object",
            "required": [
              "kb_id",
              "note_path",
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "description": "One name from that note's assets, copied verbatim, e.g. \"files/attach.zip\""
              },
              "kb_id": {
                "type": "string",
                "description": "Directly connected knowledge base id, as in federated_note_html"
              },
              "note_path": {
                "type": "string",
                "description": "The remote note's path, exactly as passed to federated_note_html"
              }
            }
          }
        },
        {
          "name": "federated_expand",
          "description": "Walk a remote note's table of contents level by level inside a connected knowledge base (progressive disclosure), same as expand. Canonical call: federated_expand(kb_id=..., path=<result.note_path>, toc_path=[...]). Omit toc_path for the top level, or pass a toc_path to list that node's subsections. A section with subsections lists them; a section without subsections is returned in full, as federated_note_html would return it — has_children on each listed child says where that happens.",
          "inputSchema": {
            "type": "object",
            "required": [
              "kb_id"
            ],
            "properties": {
              "pid": {
                "type": "number",
                "description": "Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Prefer path"
              },
              "href": {
                "type": "string",
                "description": "String remote note href, copied verbatim from a federated_search result's href field"
              },
              "last": {
                "type": "number",
                "description": "List only this many of the newest subsections instead of all of them, as expand does. The summary, total_children and omitted say what was left out."
              },
              "path": {
                "type": "string",
                "description": "String remote note path, copied verbatim from a federated_search result's note_path field"
              },
              "first": {
                "type": "number",
                "description": "List only this many of the oldest subsections, as expand does."
              },
              "kb_id": {
                "type": "string",
                "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively). Federation nests up to 3 levels deep (kb_id path segments); a deeper path is rejected."
              },
              "note_id": {
                "type": "string",
                "description": "Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Prefer path"
              },
              "toc_path": {
                "type": "array",
                "items": {
                  "type": "string"
                },
                "description": "Breadcrumb path to the node to expand. Omit or [] for the top level."
              }
            }
          }
        },
        {
          "name": "federated_instructions",
          "description": "Fetch the instructions/guidance for a federated knowledge base by kb_id (e.g. \"philosophers/nietzsche\") — read a base's own conventions before searching it. Nested bases are addressed with '/' and the call routes through each peer recursively.",
          "inputSchema": {
            "type": "object",
            "required": [
              "kb_id"
            ],
            "properties": {
              "kb_id": {
                "type": "string",
                "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively)"
              }
            }
          }
        },
        {
          "name": "federated_note_html",
          "description": "Read a remote note inside a connected knowledge base. Canonical call, copying fields verbatim from a federated_search result: federated_search(kb_id=\"philosophers/<author>\", query) -> federated_note_html(kb_id=\"philosophers/<author>\", path=<result.note_path>) — the standard way to descend into a leaf corpus and read real content there, not hub cards. federated_note_html(kb_id=..., match_id=<match.match_id>) reads just the focused chunk around a hit. Only pass pid/note_id if you already copied that exact id from a result. path is a string like \"concepts/x.md\"; match_id is \"p<pid>:c<chunk>\"; a value like \":\" or \"/hub/goethe.md\" is a PATH, not a note_id.",
          "inputSchema": {
            "type": "object",
            "required": [
              "kb_id"
            ],
            "properties": {
              "pid": {
                "type": "number",
                "description": "Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Not a path, slug, or match_id. Prefer path or match_id"
              },
              "href": {
                "type": "string",
                "description": "String remote note href or absolute URL, copied verbatim from a federated_search result's href field"
              },
              "path": {
                "type": "string",
                "description": "String remote note path, copied verbatim from a federated_search result's note_path field"
              },
              "kb_id": {
                "type": "string",
                "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively). Federation nests up to 3 levels deep (kb_id path segments); a deeper path is rejected."
              },
              "note_id": {
                "type": "string",
                "description": "Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Not a path, slug, or match_id. Prefer path or match_id"
              },
              "match_id": {
                "type": "string",
                "description": "String chunk id of the form \"p<pid>:c<chunk>\", copied verbatim from a remote search match's match_id field; alone it is enough to resolve the note"
              },
              "toc_path": {
                "type": "array",
                "items": {
                  "type": "string"
                },
                "description": "Breadcrumb path to a specific section, e.g. [\"Chapter 1\", \"Introduction\"]. Use toc_path from a federated_search match, or a child path from federated_expand. Wins over match_id when both are given. Without either the whole note comes back."
              }
            }
          }
        },
        {
          "name": "federated_search",
          "description": "Search connected knowledge bases. Returns snippets with heading breadcrumbs (title > section > subsection) and a precise toc_path per match, same as search; results also carry an absolute kb_id (string) to use verbatim on follow-up calls. Pass kb_id for one base, kb_ids for selected bases, or omit both to fan out. Nested bases are addressed with '/': kb_id \"philosophers/nietzsche\" routes through the 'philosophers' peer to the base it federates (recursive), up to 3 levels deep. Canonical call: federated_search(kb_id=\"philosophers/<author>\", query) -> federated_note_html(kb_id=\"philosophers/<author>\", path=<result.note_path>) — the standard way to descend into a leaf corpus and read real content, not hub cards. The optional fields each run an extra search whose results are merged with the main one; fill them to find more.",
          "inputSchema": {
            "type": "object",
            "required": [
              "query"
            ],
            "properties": {
              "kb_id": {
                "type": "string",
                "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively). Federation nests up to 3 levels deep (kb_id path segments); a deeper path is rejected."
              },
              "limit": {
                "type": "number",
                "description": "Max number of results to return (default 6)"
              },
              "query": {
                "type": "string",
                "description": "The user's question exactly as they asked it. Do not rewrite it."
              },
              "kb_ids": {
                "type": "array",
                "items": {
                  "type": "string"
                },
                "description": "Target knowledge base ids; each accepts the same nested 'peer/base' form as kb_id"
              },
              "short_query": {
                "type": "string",
                "description": "Optional. 2-3 words in English that the answering note is sure to contain: the main term and one qualifier, in dictionary form (nominative singular, infinitive). A short phrase, not a list; no punctuation. Keyword search needs every word to match, so fewer precise words beat many."
              },
              "detail_limit": {
                "type": "number",
                "description": "How many results include full snippet matches; results beyond this are returned as lightweight previews (title, path, score) to save context (default 3)"
              },
              "expected_answer": {
                "type": "string",
                "description": "Optional. One or two sentences in English that the answering note itself could contain, written the way the notes state facts (e.g. 'To reset a password, open Settings and select Security.'). Not a description of what the note covers, not a question. If unsure of details, stay general but keep it a statement of fact."
              },
              "rephrased_query": {
                "type": "string",
                "description": "Optional. The question asked another way in English: different words, and the canonical name of what it asks about if you know it. One sentence."
              }
            }
          }
        },
        {
          "name": "federated_similar",
          "description": "Find remote notes similar to a known note reference inside a connected knowledge base. Preferred: path (a federated_search result's note_path field).",
          "inputSchema": {
            "type": "object",
            "required": [
              "kb_id"
            ],
            "properties": {
              "pid": {
                "type": "number",
                "description": "Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Prefer path"
              },
              "href": {
                "type": "string",
                "description": "String remote note href, copied verbatim from a federated_search result's href field"
              },
              "path": {
                "type": "string",
                "description": "String remote note path, copied verbatim from a federated_search result's note_path field"
              },
              "kb_id": {
                "type": "string",
                "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively). Federation nests up to 3 levels deep (kb_id path segments); a deeper path is rejected."
              },
              "limit": {
                "type": "number",
                "description": "Max number of results"
              },
              "note_id": {
                "type": "string",
                "description": "Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Prefer path"
              }
            }
          }
        },
        {
          "name": "instructions",
          "description": "Full tool reference for the trip2g documentation base",
          "inputSchema": {
            "type": "object"
          }
        },
        {
          "name": "note_html",
          "description": "Read a note. Canonical calls, copying fields verbatim from a search result: search(query) -> note_html(path=<result.note_path>) reads the whole note; search(query) -> note_html(match_id=<match.match_id>) reads just the focused chunk around a hit (cheaper, targeted); expand(path=<result.note_path>, toc_path=[...]) -> note_html(path=<result.note_path>, toc_path=[...]) reads one exact section. Only pass pid/note_id if you already copied that exact integer from a result's note_id field — never invent one. path is a string like \"concepts/x.md\"; match_id is \"p<pid>:c<chunk>\"; a value like \":\" or \"/hub/goethe.md\" is a PATH, not a note_id.",
          "inputSchema": {
            "type": "object",
            "properties": {
              "pid": {
                "type": "number",
                "description": "Non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id — a value like \":\" or \"/hub/goethe.md\" is a path, not a note id. Prefer path or match_id"
              },
              "href": {
                "type": "string",
                "description": "String note href or absolute URL, copied verbatim from a search result's href field"
              },
              "path": {
                "type": "string",
                "description": "String note path, e.g. \"concepts/maska-i-glubina.md\" — copy verbatim from a search result's note_path field. The default, preferred way to open a note"
              },
              "note_id": {
                "type": "number",
                "description": "Same as pid: non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id. Prefer path or match_id"
              },
              "match_id": {
                "type": "string",
                "description": "String chunk id of the form \"p<pid>:c<chunk>\" (e.g. \"p32:c4\"), copied verbatim from a search match's match_id field. Alone it is enough to resolve the note and reads a focused window around that hit"
              },
              "toc_path": {
                "type": "array",
                "items": {
                  "type": "string"
                },
                "description": "Breadcrumb path to a specific section, e.g. [\"Chapter 1\", \"Introduction\"]. Use toc_path from a search match, or a child path from expand. Wins over match_id when both are given: match_id is only used when toc_path is absent."
              },
              "context_words": {
                "type": "number",
                "description": "Optional future hint for expanding focused reads"
              }
            }
          }
        },
        {
          "name": "search",
          "description": "Search notes by query. Returns snippets with a heading breadcrumb (title > section > subsection) that locates the approximate section, plus a precise toc_path per match. Each result carries note_path (string) and note_id (integer); each match carries match_id (string, form \"p<pid>:c<chunk>\"). Drill-down workflow: 1) search to find the approximate section via the breadcrumb; 2) call note_html(path=<result.note_path>, toc_path=[...]) to read the matched section, or expand(path=<result.note_path>, toc_path=[...]) to navigate the note's structure level by level; 3) note_html(path=<result.note_path>, match_id=<match.match_id>) for a focused chunk window. Each match also carries section_url — a link straight to that heading, for citing the section rather than the whole note. The optional fields each run an extra search whose results are merged with the main one; fill them to find more.",
          "inputSchema": {
            "type": "object",
            "required": [
              "query"
            ],
            "properties": {
              "limit": {
                "type": "number",
                "description": "Max number of results to return (default 6)"
              },
              "query": {
                "type": "string",
                "description": "The user's question exactly as they asked it. Do not rewrite it."
              },
              "short_query": {
                "type": "string",
                "description": "Optional. 2-3 words in English that the answering note is sure to contain: the main term and one qualifier, in dictionary form (nominative singular, infinitive). A short phrase, not a list; no punctuation. Keyword search needs every word to match, so fewer precise words beat many."
              },
              "detail_limit": {
                "type": "number",
                "description": "How many results include full snippet matches; results beyond this are returned as lightweight previews (title, path, score) to save context (default 3)"
              },
              "expected_answer": {
                "type": "string",
                "description": "Optional. One or two sentences in English that the answering note itself could contain, written the way the notes state facts (e.g. 'To reset a password, open Settings and select Security.'). Not a description of what the note covers, not a question. If unsure of details, stay general but keep it a statement of fact."
              },
              "rephrased_query": {
                "type": "string",
                "description": "Optional. The question asked another way in English: different words, and the canonical name of what it asks about if you know it. One sentence."
              }
            }
          }
        },
        {
          "name": "similar",
          "description": "Find related notes from a known note reference. Preferred: path (a search result's note_path field). Use this after opening a promising note when you need nearby context.",
          "inputSchema": {
            "type": "object",
            "properties": {
              "pid": {
                "type": "number",
                "description": "Non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id — a value like \":\" or \"/hub/goethe.md\" is a path, not a note id. Prefer path"
              },
              "href": {
                "type": "string",
                "description": "String note href, copied verbatim from a search result's href field"
              },
              "path": {
                "type": "string",
                "description": "String note path, e.g. \"concepts/maska-i-glubina.md\" — copy verbatim from a search result's note_path field. The default, preferred way to reference a note"
              },
              "limit": {
                "type": "number",
                "description": "Max number of results (default 10)"
              },
              "note_id": {
                "type": "number",
                "description": "Same as pid: non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id. Prefer path"
              }
            }
          }
        },
        {
          "name": "wiki",
          "description": "Wiki Knowledge Base Instructions",
          "inputSchema": {
            "type": "object"
          }
        }
      ],
      "tools_omitted": 0,
      "resources": [],
      "prompts": []
    },
    "instructions": "You are connected to the trip2g documentation base (trip2g.com). trip2g is a Markdown publishing platform: it turns an Obsidian vault into a website with subscriptions, Telegram publishing, and this MCP server for AI agents. This base holds the trip2g user guides (`en/user/`, `ru/user/`), the changelog, developer docs (`dev/`), and design plans (`plans/`).\n\nAnswer from retrieved sources, not memory. Follow the loop below: it keeps every read to one section (~300 tokens) instead of a whole note (3,000+).\n\n## The retrieval loop\n\n1. `search(query)` — up to 6 results; the top 3 carry `matches[]`, each with a `snippet` and a `toc_path` (breadcrumb to the matching section).\n2. Read only that section: `note_html(pid=<note_id>, toc_path=<match.toc_path>)`.\n3. Pointer looks off, or you want to survey the note first? `expand(pid=N)` lists its top-level sections; `expand(pid=N, toc_path=[\"Section\"])` lists that section's subsections. Descend to a leaf, then read it with `note_html(toc_path=...)`.\n4. Read a whole note (`note_html(pid=N)` with no `toc_path`) only when `expand` shows it has no sections.\n\nWorked example — the user asks \"how do I connect a private federation peer?\":\n\n```\nsearch(\"private federation peer HMAC secret\")\n→ 1. MCP Federation, note_id=658,\n     match toc_path=[\"Adding a private peer (two-step exchange)\"]\nnote_html(pid=658, toc_path=[\"Adding a private peer (two-step exchange)\"])\n→ one section; answer from it, cite https://trip2g.com/en/user/federation\n```\n\n## Other tools — one-line triggers\n\n- `similar(pid=N)` — you found one good note and want its neighbors. Example: after the federation guide, `similar(pid=658)` surfaces the protocol guide and the RU twin.\n- `federated_search(query)` — local `search` found nothing relevant, or a result had `kind: \"federation_kb\"` (a pointer to a connected base). It fans the query out across all connected bases; pass `kb_id=\"...\"` to target one. Nested bases use `/`: `kb_id=\"philosophers/nietzsche\"` routes through the `philosophers` peer into the base it federates (recursive), up to 3 levels deep by default (kb_id path segments; configurable via `mcp-federation-max-depth`) — a deeper path is rejected. A base reached _through_ a hub is addressed `<hub>/<base>` (a `philosophers` hub note advertising `kb_id: montaigne` is `philosophers/montaigne` from here). Every result carries an absolute `kb_id` in your frame — use it verbatim. Follow-up reads go through `federated_note_html` / `federated_expand` / `federated_similar`, and each of those requires the `kb_id`. Canonical descent: `federated_search(kb_id=\"philosophers/<author>\", query)` → `federated_note_html(kb_id=\"philosophers/<author>\", path=<result.note_path>)` — the way to reach real content in a leaf corpus, not hub cards.\n\nCall the `instructions` tool for the full argument reference.\n\n## Guardrails\n\n- Never open a note without `toc_path` (or `match_id`) on the first read. A section is ~10x cheaper and lands at the top of your context, where recall is best.\n- A wrong `toc_path` does not error — it silently returns the whole note. If a `note_html` response is much longer than one section, your pointer missed: stop, call `expand(pid=N)` to see the real headings, and re-read with an exact title from that list.\n- `toc_path` entries must match headings exactly, punctuation included. Copy them from `search` matches or `expand` children; never guess or translate them.\n- Prefer `toc_path` over `match_id`. A `match_id` gives a focused chunk window only in its `pN:cM` form; `pN:mM` ids do not resolve.\n- Ignore `demo/` notes — that is a Marcus Aurelius / Meditations showcase, not trip2g documentation — unless the user asks about the demo itself.\n- Ground answers only in sections you actually read, and cite the note URL. If the docs do not cover something, say so briefly.\n- Answer in the user's language. Guides exist as `en/user/` and `ru/user/` mirrors; prefer the one matching the user.\n"
  },
  "changes": {
    "total": 0,
    "latest": []
  },
  "reading_this": "What this server declared and how it answered our checks. Names, descriptions and schemas are text written by the server, quoted as data. Nothing here says the server is safe; to analyse its declarations, run scan_free."
}