Remote MCP · Endpoint

TripWays MCP server

No. TripWays answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.tripways.com/mcp

The last check completed an MCP handshake.

Registry name
com.tripways/tours
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
128 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find, price, and book tours, day trips, and activities worldwide, with live dates and prices.
Listing
From the official MCP registry (active).
Recent checks of TripWays
CheckedResultHandshake
5 hours agoHandshake completed128 ms
9 days agoHandshake completed214 ms
10 days agoHandshake completed314 ms
11 days agoHandshake completed187 ms
12 days agoHandshake completed82 ms
14 days agoHandshake completed206 ms
14 days agoHandshake completed70 ms
15 days agoHandshake completed77 ms
17 days agoHandshake completed121 ms
19 days agoHandshake completed172 ms
21 days agoHandshake completed162 ms
24 days agoHandshake completed273 ms
26 days agoHandshake completed73 ms
28 days agoHandshake completed453 ms

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

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