Remote MCP · Endpoint

FlightSeatMap MCP server

No — it is up, but it requires credentials. FlightSeatMap answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://mcp.flightseatmap.com/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
com.flightseatmap/flightseatmap
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
10 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Seat maps, seat ratings, traveller reviews and seat alerts for 150+ airlines.
Listing
From the official MCP registry (active).
Recent checks of FlightSeatMap
CheckedResultHandshake
1 hour agoCredentials required—
2 days agoCredentials required—
4 days agoCredentials required—
5 days agoCredentials required—
7 days agoHandshake completed276 ms
8 days agoHandshake completed468 ms
9 days agoHandshake completed616 ms
12 days agoHandshake completed303 ms
13 days agoHandshake completed321 ms
15 days agoHandshake completed221 ms
16 days agoHandshake completed353 ms
17 days agoHandshake completed262 ms
18 days agoHandshake completed263 ms
19 days agoHandshake completed136 ms
20 days agoHandshake completed375 ms
21 days agoHandshake completed333 ms
22 days agoHandshake completed294 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 FlightSeatMap and makes no claim about it beyond what these checks measured.