Remote MCP · Endpoint

trip2g MCP server

No. trip2g answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://trip2g.com/_system/mcp

The last check completed an MCP handshake.

Registry name
io.github.trip2g/trip2g
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
355 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.
Listing
From the official MCP registry (active).
Recent checks of trip2g
CheckedResultHandshake
2 hours agoHandshake completed355 ms
2 days agoHandshake completed275 ms
4 days agoHandshake completed286 ms
5 days agoHandshake completed293 ms
7 days agoHandshake completed275 ms
8 days agoHandshake completed335 ms
9 days agoHandshake completed289 ms
12 days agoHandshake completed284 ms
13 days agoHandshake completed280 ms
15 days agoHandshake completed306 ms
17 days agoHandshake completed283 ms
18 days agoHandshake completed290 ms
19 days agoHandshake completed280 ms
20 days agoHandshake completed294 ms
20 days agoHandshake completed353 ms
21 days agoHandshake completed280 ms
23 days agoHandshake completed279 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with trip2g and makes no claim about it beyond what these checks measured.