Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
trip2g is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http trip2g-mcp https://trip2g.com/_system/mcp
# 2 — ask your agent for something these tools do
# expand, federated_asset, federated_expand and 9 more
trip2g costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http trip2g-mcp https://trip2g.com/_system/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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_childr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| first | number | no | 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. |
| href | string | no | String note href, copied verbatim from a search result's href field |
| last | number | no | 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 i |
| note_id | number | no | 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 |
| path | string | no | 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 |
| pid | number | no | 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 | array | no | Breadcrumb path to the node to expand, e.g. ["Chapter 1"]. Omit or [] for the top level. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kb_id | string | yes | Directly connected knowledge base id, as in federated_note_html |
| name | string | yes | One name from that note's assets, copied verbatim, e.g. "files/attach.zip" |
| note_path | string | yes | The remote note's path, exactly as passed to federated_note_html |
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 federa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| first | number | no | List only this many of the oldest subsections, as expand does. |
| href | string | no | String remote note href, copied verbatim from a federated_search result's href field |
| kb_id | string | yes | 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 |
| last | number | no | 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. |
| note_id | string | no | Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Prefer path |
| path | string | no | String remote note path, copied verbatim from a federated_search result's note_path field |
| pid | number | no | Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Prefer path |
| toc_path | array | no | Breadcrumb path to the node to expand. Omit or [] for the top level. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kb_id | string | yes | Target knowledge base id; nested bases use '/' (e.g. "philosophers/nietzsche" routes through the 'philosophers' peer, recursively) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| href | string | no | String remote note href or absolute URL, copied verbatim from a federated_search result's href field |
| kb_id | string | yes | 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 |
| match_id | string | no | 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 |
| note_id | string | no | 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 |
| path | string | no | String remote note path, copied verbatim from a federated_search result's note_path field |
| pid | number | no | 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 |
| toc_path | array | no | 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. Wi |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_limit | number | no | 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 | string | no | 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 de |
| kb_id | string | no | 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 |
| kb_ids | array | no | Target knowledge base ids; each accepts the same nested 'peer/base' form as kb_id |
| limit | number | no | Max number of results to return (default 6) |
| query | string | yes | The user's question exactly as they asked it. Do not rewrite it. |
| rephrased_query | string | no | 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. |
| short_query | string | no | 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 punctua |
Find remote notes similar to a known note reference inside a connected knowledge base. Preferred: path (a federated_search result's note_path field).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| href | string | no | String remote note href, copied verbatim from a federated_search result's href field |
| kb_id | string | yes | 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 |
| limit | number | no | Max number of results |
| note_id | string | no | Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Prefer path |
| path | string | no | String remote note path, copied verbatim from a federated_search result's note_path field |
| pid | number | no | Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Prefer path |
Full tool reference for the trip2g documentation base
No parameter schema on file.
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 p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| context_words | number | no | Optional future hint for expanding focused reads |
| href | string | no | String note href or absolute URL, copied verbatim from a search result's href field |
| match_id | string | no | 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 |
| note_id | number | no | 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 |
| path | string | no | 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 |
| pid | number | no | 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 |
| toc_path | array | no | 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 |
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=
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_limit | number | no | 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 | string | no | 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 de |
| limit | number | no | Max number of results to return (default 6) |
| query | string | yes | The user's question exactly as they asked it. Do not rewrite it. |
| rephrased_query | string | no | 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. |
| short_query | string | no | 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 punctua |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| href | string | no | String note href, copied verbatim from a search result's href field |
| limit | number | no | Max number of results (default 10) |
| note_id | number | no | 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 |
| path | string | no | 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 |
| pid | number | no | 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 |
Wiki Knowledge Base Instructions
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install trip2g or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| expand | no tags | |
| federated_asset | untrusted-inputexternal-sink | untrusted-input: keyword "fetch"; external-sink: keyword "curl" |
| federated_expand | no tags | |
| federated_instructions | untrusted-input | untrusted-input: keyword "fetch" |
| federated_note_html | no tags | |
| federated_search | no tags | |
| federated_similar | no tags | |
| instructions | no tags | |
| note_html | no tags | |
| search | no tags | |
| similar | no tags | |
| wiki | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish trip2g can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.