Remote MCP · Endpoint

TripHook MCP server

No. TripHook answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.triphook.me/api/public/mcp

The last check completed an MCP handshake.

Registry name
me.triphook/triphook
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
139 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Find group trips and day outs to join, events in a city, and where to go by weather and budget.
Listing
From the official MCP registry (active).
Recent checks of TripHook
CheckedResultHandshake
1 hour agoHandshake completed139 ms
1 day agoHandshake completed117 ms
4 days agoHandshake completed124 ms
6 days agoHandshake completed113 ms
9 days agoHandshake completed116 ms
11 days agoHandshake completed120 ms
13 days agoHandshake completed120 ms
15 days agoHandshake completed114 ms
17 days agoHandshake completed149 ms
19 days agoHandshake completed117 ms
21 days agoHandshake completed122 ms
22 days agoHandshake completed112 ms
23 days agoHandshake completed105 ms
25 days agoHandshake completed118 ms
27 days agoHandshake completed112 ms
29 days agoHandshake completed139 ms

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

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 TripHook and makes no claim about it beyond what these checks measured.