Remote MCP · Endpoint

Aviasurf MCP server

No. Aviasurf answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.aviasurf.com/mcp

The last check completed an MCP handshake.

Registry name
com.aviasurf/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
349 ms
Tools exposed
9 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Search and compare flight prices, calendars, airports, routes, and destinations with Aviasurf.
Listing
From the official MCP registry (active).
Recent checks of Aviasurf
CheckedResultHandshake
7 hours agoHandshake completed349 ms
3 days agoHandshake completed323 ms
12 days agoHandshake completed343 ms
13 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed361 ms
15 days agoHandshake completed327 ms
17 days agoHandshake completed313 ms
18 days agoHandshake completed314 ms
18 days agoHandshake completed338 ms
20 days agoHandshake completed535 ms
22 days agoHandshake completed329 ms
25 days agoHandshake completed344 ms
27 days agoHandshake completed317 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 22 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 Aviasurf and makes no claim about it beyond what these checks measured.