Remote MCP · Endpoint

TripWays MCP server

No. TripWays answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
273 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed273 ms
2 days agoHandshake completed73 ms
4 days agoHandshake completed453 ms
6 days agoHandshake completed188 ms
8 days agoHandshake completed158 ms
10 days agoHandshake completed83 ms
12 days agoHandshake completed46 ms
13 days agoHandshake completed216 ms
14 days agoHandshake completed588 ms
16 days agoHandshake completed227 ms
18 days agoHandshake completed226 ms
20 days agoHandshake completed140 ms
21 days agoHandshake completed277 ms
23 days agoHandshake completed343 ms
24 days agoHandshake completed292 ms

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

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.