FAA Airport Status

dev.workers.quietworklabs.faa-x402Published by faa-x402.quietworklabs.workers.devOfficial publisherv1.2.0Updated Oct 25, 2026

FAA airport delays/ground stops + TFR corridor GeoJSON by bbox (x402 USDC on Base).

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Remote MCP server giving an assistant live FAA airport disruption data: per-airport status, ranked US disruptions, and TFR areas as GeoJSON.

What you can do
Look up current FAA status for one US airport by IATA or ICAO code, including severity and active events such as ground stops, ground delay programs, delays and closures. List every current FAA disruption in US airspace ranked by severity. Retrieve active and upcoming Temporary Flight Restrictions intersecting a bounding box as a GeoJSON FeatureCollection with altitude bands, effective times, NOTAM ids and facilities.
When to use it
Useful when you need a quick read on US airport delays, ground stops or closures, or want to check which Temporary Flight Restrictions overlap a given area. Data is cached up to 60 seconds and is not intended for operational flight planning.
Requirements
A remote streamable HTTP endpoint; no local package, account, API key or header is declared. Calls are paid per use in USDC on Base via x402, with the first 5 calls per day per client free, so a wallet or x402-capable client is needed for further calls.
Before you install
Each call beyond the free daily allowance costs USDC on Base, so repeated queries spend money. The server is explicitly not for operational flight planning; treat results as informational and cached up to 60 seconds.

Installation

In SourceWeft

  1. Open FAA Airport Status in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.quietworklabs.faa-x402%2Ffaa-airport-status/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "faa-airport-status": {
      "type": "http",
      "url": "https://faa-x402.quietworklabs.workers.dev/mcp"
    }
  }
}

Tools

3

airport_status

FAA status for one US airport

Current FAA status for one US airport: normal, advisory or disrupted, max severity (0-5) and each active event (ground stop, ground delay program with average/max delay, arrival/departure delays, closure). Price: $0.002 USDC per call via x402 (Base); the first 5 calls per day per client are free.

Parameterscoderequired

us_airport_disruptions

All current US airport disruptions

Every current FAA disruption in US airspace (ground stops, ground delay programs, delays, closures) ranked by severity. Price: $0.003 USDC per call via x402 (Base); the first 5 calls per day per client are free.

ParametersminSeverity

tfr_corridor

US TFRs intersecting a geographic box (GeoJSON)

Active and upcoming US Temporary Flight Restrictions whose area intersects a bounding box, as a GeoJSON FeatureCollection: polygon per restricted area with altitude band (feet + AGL/MSL), effective time and valid_until, NOTAM id, type and facility. Fuses the FAA TFR list with each NOTAM's boundary geometry. For drone/flight-ops corridor pre-flight checks. Not for operational flight planning. Price: $0.005 USDC per call via x402 (Base); the first 5 calls per day per client are free.

Parametersbboxrequiredalt_ftbuffer_nmactive_only

Version history

2
  1. v1.2.0LatestOct 25, 2026
  2. v1.1.0Oct 18, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.