Remote MCP · Endpoint

HasData Google Flights Deals MCP server

No. HasData Google Flights Deals answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.hasdata.com/mcp?apis=google_travel_flights_deals

The last check completed an MCP handshake.

Registry name
com.hasdata/google-flights-deals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
A plain-language trip description becomes dated flight deals with prices and booking links.
Listing
From the official MCP registry (active).
Recent checks of HasData Google Flights Deals
CheckedResultHandshake
1 hour agoHandshake completed122 ms
4 days agoHandshake completed221 ms
14 days agoHandshake completed127 ms
15 days agoHandshake completed132 ms
15 days agoHandshake completed598 ms
17 days agoHandshake completed125 ms
18 days agoHandshake completed160 ms
19 days agoHandshake completed125 ms
20 days agoHandshake completed128 ms
21 days agoHandshake completed120 ms
23 days agoHandshake completed121 ms
25 days agoHandshake completed117 ms
28 days agoHandshake completed127 ms

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

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