FAA Airport Status MCP server
dev.workers.quietworklabs.faa-x402/faa-airport-statusfaa-x402.quietworklabs.workers.devstreamable-httpv1.2.0Scanned
FAA airport delays/ground stops + TFR corridor GeoJSON by bbox (x402 USDC on Base).
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the FAA Airport Status MCP server can do
The FAA Airport Status MCP server is published by faa-x402.quietworklabs.workers.dev, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: airport_status, us_airport_disruptions and tfr_corridor), but cannot delete data. None of its tools only reads.
3 tools bring in text other people can write (airport_status, us_airport_disruptions and tfr_corridor).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 3Claude Code: ask
airport_statusCurrent 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/de…Reads text others write1 finding
Why it is in this group
- The name "airport_status" says "status": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "airport_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "airport_status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
tfr_corridorActive and upcoming US Temporary Flight Restrictions whose area intersects a bounding box, as a GeoJSON FeatureCollection: polygon per restricted area with altitude band (feet + AG…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
us_airport_disruptionsEvery current FAA disruption in US airspace (ground stops, ground delay programs, delays, closures) ranked by severity.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://faa-x402.quietworklabs.workers.dev/mcp: tools/list returned 3 tools to an anonymous client, including airport_status (write), us_airport_disruptions (write), tfr_corridor (write)
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 2 to 3
Findings
Matches of fixed checks, with the text they matched.
- Warnairport_status
The server marks "airport_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "airport_status" says "status": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Tools1 added.+1 addedView diff
- Added:tfr_corridorChanges things
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http faa-airport-status https://faa-x402.quietworklabs.workers.dev/mcpclaude mcp add --transport http faa-airport-status https://faa-x402.quietworklabs.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__faa-airport-status__airport_status",
"mcp__faa-airport-status__us_airport_disruptions",
"mcp__faa-airport-status__tfr_corridor"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as faa-airport-status. Review it before you use it.
Capability tags behind 3 rules
- mcp__faa-airport-status__airport_status untrusted-input
- mcp__faa-airport-status__us_airport_disruptions untrusted-input
- mcp__faa-airport-status__tfr_corridor untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.quietworklabs.faa-x402/faa-airport-status/verify?hash=e5dae6bc07cda4d89f511a648b65bc78032a7b4197f0036120c5aba095d81e43" | jq -e '.changed == false'Pinned hash e5dae6bc07cd, from Nov 9, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.quietworklabs.faa-x402/faa-airport-status/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.quietworklabs.faa-x402/faa-airport-status)Source: MCP Registry. Synced Oct 25, 2026, 00:17 UTC.
FAA Airport Status MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the FAA Airport Status MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the FAA Airport Status MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the FAA Airport Status MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the FAA Airport Status MCP server have?
- 3 tools: 3 write. airport_status, us_airport_disruptions and tfr_corridor.
Does the FAA Airport Status MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the FAA Airport Status MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the FAA Airport Status MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 25, 2026. Every change is on this page and in its Atom feed.