Remote MCP · Endpoint

FAA Airport Status MCP server

No. FAA Airport Status answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://faa-x402.quietworklabs.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.quietworklabs.faa-x402/faa-airport-status
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
126 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
FAA airport delays/ground stops + TFR corridor GeoJSON by bbox (x402 USDC on Base).
Listing
From the official MCP registry (active).
Recent checks of FAA Airport Status
CheckedResultHandshake
3 hours agoHandshake completed126 ms
9 days agoHandshake completed181 ms
10 days agoHandshake completed155 ms
11 days agoHandshake completed153 ms
12 days agoHandshake completed214 ms
14 days agoHandshake completed167 ms
14 days agoHandshake completed210 ms
15 days agoHandshake completed152 ms
17 days agoHandshake completed271 ms
19 days agoHandshake completed40 ms
21 days agoHandshake completed146 ms
24 days agoHandshake completed128 ms
26 days agoHandshake completed217 ms
28 days agoHandshake completed125 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 FAA Airport Status and makes no claim about it beyond what these checks measured.