Remote MCP · Endpoint
io.github.Waysway-app/waysway MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://api.waysway.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.Waysway-app/waysway
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 20 tools
- Uptime, last 30 days
- 72.2% from 18 checks
- Described by its publisher as
- Waysway AI travel MCP for hotels, live prices, restaurants, flights, and activities.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Handshake completed | 709 ms |
| 10 days ago | Handshake completed | 694 ms |
| 11 days ago | Handshake completed | 716 ms |
| 14 days ago | Handshake completed | 759 ms |
| 15 days ago | Handshake completed | 754 ms |
| 17 days ago | Handshake completed | 713 ms |
| 19 days ago | Handshake completed | 680 ms |
| 20 days ago | Handshake completed | 732 ms |
| 21 days ago | Handshake completed | 713 ms |
| 22 days ago | Handshake completed | 723 ms |
| 22 days ago | Handshake completed | 697 ms |
| 23 days ago | Handshake completed | 714 ms |
| 25 days ago | Handshake completed | 698 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 18.
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 io.github.Waysway-app/waysway and makes no claim about it beyond what these checks measured.