Remote MCP · Endpoint

Fly Frugal Travel Data MCP server

No. Fly Frugal Travel Data answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://flyfrugal.fyi/mcp

The last check completed an MCP handshake.

Registry name
fyi.flyfrugal/travel-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
682 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only public itinerary previews, observed round-trip fares, and flight savings verified today.
Listing
From the official MCP registry (active).
Recent checks of Fly Frugal Travel Data
CheckedResultHandshake
1 hour agoHandshake completed682 ms
1 day agoHandshake completed61 ms
4 days agoHandshake completed631 ms
6 days agoHandshake completed56 ms
9 days agoHandshake completed399 ms
11 days agoHandshake completed381 ms
13 days agoHandshake completed719 ms
15 days agoHandshake completed509 ms
17 days agoHandshake completed763 ms
19 days agoHandshake completed1.02 s
21 days agoHandshake completed378 ms
22 days agoHandshake completed760 ms
23 days agoHandshake completed659 ms

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

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