trip2g
REMOTE · TRIP2G.COM · SCANNED AUG 3
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.
Available components
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 →
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 10 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 Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3664 tokens (~366/item across 10 items; 10 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · trip2g.com
claude mcp add --transport http trip2g-trip2g https://trip2g.com/_system/mcp
[mcp_servers.trip2g-trip2g] url = "https://trip2g.com/_system/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trip2g-trip2g": {
"type": "remote",
"url": "https://trip2g.com/_system/mcp",
"enabled": true
}
}
} openclaw mcp add trip2g-trip2g --url https://trip2g.com/_system/mcp --transport streamable-http
mcp_servers:
trip2g-trip2g:
url: "https://trip2g.com/_system/mcp" {
"mcpServers": {
"trip2g-trip2g": {
"type": "http",
"url": "https://trip2g.com/_system/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 55
First indexed and scored.
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 3 Aug 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=YR1,O=Let's Encrypt,C=US | 15 Jun 2026 | 13 Sept 2026 | RSA 4096 | SHA256-RSA | 6c25d0d119f95012228c1815fe3dcf03b9a |
| SANs: trip2g.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 |
DNSSEC insecure
Validation of trip2g.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| trip2g.com. | absent | 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 |
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.
expand ~323
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. Drill down with expand, then read a leaf with note_html(path=..., toc_path=[...]) — no need to load the whole note or its full flat TOC.
| Name | Type | Req | Description |
|---|---|---|---|
| href | string | — | String note href, copied verbatim from a search result's href field |
| 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_expand ~285
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.
| 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… |
| 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 ~433
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 |
No output schema declared.
No examples provided.
federated_search ~334
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.
| 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) |
| 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 | Search query |
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 ~468
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. |
No output schema declared.
No examples provided.
search ~223
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.
| 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) |
| limit | number | — | Max number of results to return (default 6) |
| query | string | yes | Search query |
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.