Remote MCP · Endpoint

VoyageHacks MCP server

No. VoyageHacks answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://voyagehacks.com/mcp

The last check completed an MCP handshake.

Registry name
com.voyagehacks/travel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
85 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Multilingual travel guides, gear picks and booking links for AI travel agents.
Listing
From the official MCP registry (active).
Recent checks of VoyageHacks
CheckedResultHandshake
1 hour agoHandshake completed85 ms
2 days agoHandshake completed61 ms
4 days agoHandshake completed76 ms
5 days agoHandshake completed105 ms
7 days agoHandshake completed59 ms
8 days agoHandshake completed326 ms
9 days agoHandshake completed73 ms
12 days agoHandshake completed50 ms
13 days agoHandshake completed80 ms
15 days agoHandshake completed74 ms
16 days agoHandshake completed107 ms
18 days agoHandshake completed69 ms
19 days agoHandshake completed70 ms
20 days agoHandshake completed53 ms
20 days agoHandshake completed77 ms
21 days agoHandshake completed103 ms
22 days agoHandshake completed430 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 VoyageHacks and makes no claim about it beyond what these checks measured.