Remote MCP · Endpoint

a2bflight fares MCP server

No. a2bflight fares answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.a2bflight.com/mcp

The last check completed an MCP handshake.

Registry name
com.a2bflight/fares
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
261 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Flight fares seen on thousands of routes, each dated, and where a group can meet. Not live. No key.
Listing
From the official MCP registry (active).
Recent checks of a2bflight fares
CheckedResultHandshake
1 hour agoHandshake completed261 ms
2 days agoHandshake completed266 ms
5 days agoHandshake completed246 ms
7 days agoHandshake completed258 ms
9 days agoHandshake completed264 ms
11 days agoHandshake completed283 ms
13 days agoHandshake completed280 ms
15 days agoHandshake completed305 ms
17 days agoHandshake completed267 ms
19 days agoHandshake completed396 ms
20 days agoHandshake completed263 ms
21 days agoHandshake completed261 ms
22 days agoHandshake completed261 ms
25 days agoHandshake completed262 ms

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

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 a2bflight fares and makes no claim about it beyond what these checks measured.