trip2g
REMOTE · TRIP2G.COM
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.
Available components
Last scanned (20 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4689 tokens (~390/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Nov 26 0
- The server no longer declares the “logging” capability functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “federated_search” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: 276 → 390 ▼ functional
- New tool “federated_asset” functional
- “federated_search” added an optional parameter “expected_answer” cosmetic
- “federated_search” added an optional parameter “rephrased_query” cosmetic
- “federated_search” added an optional parameter “short_query” cosmetic
- “search” added an optional parameter “expected_answer” cosmetic
- “search” added an optional parameter “rephrased_query” cosmetic
- “search” added an optional parameter “short_query” cosmetic
- “federated_search” reworded the description of “query” cosmetic
- “search” reworded the description of “query” cosmetic
- 30 Sept 26 0
- “expand” added an optional parameter “first” cosmetic
- “expand” added an optional parameter “last” cosmetic
- “federated_expand” added an optional parameter “first” cosmetic
- “federated_expand” added an optional parameter “last” cosmetic
4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://trip2g.com/_system/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trip2g.com | CN=YR2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | RSA 4096 | SHA256-RSA | 55aa55a75673d66da9354f2efa62600461f |
| SANs: trip2g.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trip2g.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| trip2g.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trip2g.com/_system/mcp | Verified | 200 | |
| http (plaintext) | http://trip2g.com/_system/mcp | HTTPS enforced | 301 | https://trip2g.com/_system/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
expand ~501
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.
| Name | Type | Req | Description |
|---|---|---|---|
| first | number | – | 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 | – | String note href, copied verbatim from a search result's href field |
| last | number | – | 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… |
| note_id | number | – | 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 | – | 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 | – | 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 | – | Breadcrumb path to the node to expand, e.g. ["Chapter 1"]. Omit or [] for the top level. |
No output schema declared.
No examples provided.
federated_asset ~198
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 '/'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
federated_expand ~381
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.
| Name | Type | Req | Description |
|---|---|---|---|
| first | number | – | List only this many of the oldest subsections, as expand does. |
| href | string | – | 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 deepe… |
| last | number | – | 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 | – | Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Prefer path |
| path | string | – | String remote note path, copied verbatim from a federated_search result's note_path field |
| pid | number | – | Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Prefer path |
| toc_path | array | – | Breadcrumb path to the node to expand. Omit or [] for the top level. |
No output schema declared.
No examples provided.
federated_instructions ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kb_id | string | yes | Target knowledge base id; nested bases use '/' (e.g. "philosophers/nietzsche" routes through the 'philosophers' peer, recursively) |
No output schema declared.
No examples provided.
federated_note_html ~494
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.
| Name | Type | Req | Description |
|---|---|---|---|
| href | string | – | 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 deepe… |
| match_id | string | – | 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 | – | 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 | – | String remote note path, copied verbatim from a federated_search result's note_path field |
| pid | number | – | 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 | – | 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. W… |
No output schema declared.
No examples provided.
federated_search ~552
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail_limit | number | – | 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 | – | 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 d… |
| kb_id | string | – | 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 deepe… |
| kb_ids | array | – | Target knowledge base ids; each accepts the same nested 'peer/base' form as kb_id |
| limit | number | – | 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 | – | 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 | – | 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 punctu… |
No output schema declared.
No examples provided.
federated_similar ~232
Find remote notes similar to a known note reference inside a connected knowledge base. Preferred: path (a federated_search result's note_path field).
| Name | Type | Req | Description |
|---|---|---|---|
| href | string | – | 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 deepe… |
| limit | number | – | Max number of results |
| note_id | string | – | Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Prefer path |
| path | string | – | String remote note path, copied verbatim from a federated_search result's note_path field |
| pid | number | – | Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Prefer path |
No output schema declared.
No examples provided.
instructions ~18
Full tool reference for the trip2g documentation base
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
note_html ~488
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context_words | number | – | Optional future hint for expanding focused reads |
| href | string | – | String note href or absolute URL, copied verbatim from a search result's href field |
| match_id | string | – | 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 | – | 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 | – | 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 | – | 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 | – | 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… |
No output schema declared.
No examples provided.
search ~465
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail_limit | number | – | 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 | – | 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 d… |
| limit | number | – | 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 | – | 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 | – | 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 punctu… |
No output schema declared.
No examples provided.
similar ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| href | string | – | String note href, copied verbatim from a search result's href field |
| limit | number | – | Max number of results (default 10) |
| note_id | number | – | 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 | – | 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 | – | 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 |
No output schema declared.
No examples provided.
wiki ~12
Wiki Knowledge Base Instructions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the trip2g MCP server?
trip2g is a hosted endpoint at https://trip2g.com/_system/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · trip2g.com
claude mcp add --transport http trip2g-trip2g 'https://trip2g.com/_system/mcp'
What is the trip2g MCP server?
trip2g is an MCP server listed in the public MCP registry as io.github.trip2g/trip2g. Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers. This page covers its hosted endpoint (https://trip2g.com/_system/mcp).
Is the trip2g MCP server safe to use?
trip2g scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the trip2g MCP server expose?
trip2g exposes 12 tools: expand, federated_asset, federated_expand, federated_instructions, federated_note_html, and 7 more. Their descriptions and schemas cost roughly 3,678 tokens of context every time the server is loaded.
Does the trip2g MCP server require authentication?
No. We connected to trip2g without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the trip2g MCP server still maintained?
trip2g is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the trip2g MCP server?
VerifyMCP ran 12 checks on trip2g, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about trip2g: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.