faa-traffic-delays-mcp-server
io.github.cyanheads/faa-traffic-delays-mcp-servercyanheadsstreamable-httpv0.3.1Scanned
Track FAA ground stops, delay programs, airport delays, the operations plan, and ATCSCC advisories.
6 tools: 6 only read.
- Reads private data · 1
- Reads text others write · 6
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- 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-traffic-delays-mcp-server can do
The faa-traffic-delays-mcp-server is published by the GitHub account cyanheads. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (faa_delays_list_advisories); 6 tools bring in text other people can write (faa_delays_get_airport_status, faa_delays_list_active_events, faa_delays_get_operations_plan and 3 more).
The fixed checks matched 1 finding (tool-shadowing). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 0.3.1.
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.
6 tools
Only reads 6Show 6 read-only tools
faa_delays_get_advisoryGet the full text of one ATCSCC advisory by its number and UTC date.Reads text others writeNo findings
Why it is in this group
- The name "faa_delays_get_advisory" says "get": a word for reading.
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 Get the full text of one ATCSCC advisory by its number and UTC date. faa_delays_list_advisories lists the advisories issued on a date with their numbers, and the advisory reference that faa_delays_list_active_events and faa_delays_get_airport_status return on program rows and faa_delays_get_operations_plan returns for the plan names one directly. Advisory text carries what the status feed omits: program rate by hour, delay assignment mode, scope, comments, and the operations plan's active constraints and runway closures. Advisory numbers restart at 1 each UTC day, and older advisories remain available.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
faa_delays_get_airport_statusGet the current FAA traffic management status for one or more US airports: a headline status, every active event (ground stop, Ground Delay Program with its delay profile, arrival …Reads text others writeNo findings
Why it is in this group
- The name "faa_delays_get_airport_status" says "get": a word for reading.
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 Get the current FAA traffic management status for one or more US airports: a headline status, every active event (ground stop, Ground Delay Program with its delay profile, arrival or departure delay, closure, deicing) with reason and times, and the runway configuration and airport arrival rate. Each row also carries plannedPrograms, the current operations plan's terminal ground-stop and delay-program items that name the airport, with the plan's times as written. Every row carries the airport's ARTCC, and its coordinates come from the feed when the airport is listed (absent when the feed omits them) and from the NASR directory otherwise; both place a departure airport against a program's includedFacilities and departureScopeNm. Airports are FAA 3-character identifiers (SEA, ORD, JFK) or their ICAO codes (KSEA, PHNL); a code that names no US airport is rejected. The FAA feed lists only airports with an active event, so a known airport absent from it returns status no_active_events, and runway configuration is available only for listed airports.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
faa_delays_get_operations_planGet the FAA Command Center's current operations plan: terminal programs (possible ground stops and delay programs by airport) and en-route initiatives (route closures, severe-weath…Reads text others writeNo findings
Why it is in this group
- The name "faa_delays_get_operations_plan" says "get": a word for reading.
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 Get the FAA Command Center's current operations plan: terminal programs (possible ground stops and delay programs by airport) and en-route initiatives (route closures, severe-weather avoidance plans) expected later in the day, each with its planned UTC time and stated likelihood, plus the plan advisory's send time and current ATCSCC announcements. The advisory reference opens the full plan text with faa_delays_get_advisory, including active constraints, runway closures, and the EVENT TIME line that dates planned items.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
faa_delays_list_active_eventsList every active FAA traffic management event across the National Airspace System in one call: ground stops, Ground Delay Programs, Airspace Flow Programs, arrival and departure d…Reads text others writeNo findings
Why it is in this group
- The name "faa_delays_list_active_events" says "list": a word for reading.
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 List every active FAA traffic management event across the National Airspace System in one call: ground stops, Ground Delay Programs, Airspace Flow Programs, arrival and departure delays, airport closures, closure NOTAMs, and deicing. Rows are sorted by severity (airport-wide closures in effect, including those filed as closure_notam, ground stops, then GDPs and then AFPs each by average delay, arrival/departure delays by band maximum, other closure NOTAMs and closures outside their daily window, deicing) and carry the reason, delay figures, times, and an advisory reference for faa_delays_get_advisory. Use faa_delays_get_airport_status for the full detail of one airport, including its GDP delay profile and runway configuration.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
faa_delays_list_advisoriesList the ATCSCC advisories issued on one UTC date, newest first, from the FAA advisories database's per-date index: ground stops and delay programs as issued, proposed, revised, an…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "faa_delays_list_advisories" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "database": it reads databases.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the ATCSCC advisories issued on one UTC date, newest first, from the FAA advisories database's per-date index: ground stops and delay programs as issued, proposed, revised, and canceled, required reroutes, flow constrained areas, operations plans, and CDM compression advisories, including those no longer active and those on past dates, which the NAS Status feed does not carry. Each row gives the advisory number, control element, subject, any further title lines (a reroute's name, constrained area, and valid period), and send time; its number and date open the full text with faa_delays_get_advisory. Narrow by categories, control_element (an airport, its ICAO code, an ARTCC, or DCC for national advisories), or query (literal case-insensitive subject/details text, such as an FCA name); filters combine before limit and offset paging.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
faa_delays_list_referenceDecode the vocabulary the other faa_delays tools return: event types and their fields, traffic-management terms (AAR, EDCT, FCA, GDP, SWAP), ARTCC center codes, the FAA pacing airp…Reads text others write1 finding
Why it is in this group
- The name "faa_delays_list_reference" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description names a tool "faa_delays" that this server does not list.
What this check looks forMatched text
description: "Decode the vocabulary the other faa_delays tools return: event types and their fields, t..."
Description, as the server wrote it Decode the vocabulary the other faa_delays tools return: event types and their fields, traffic-management terms (AAR, EDCT, FCA, GDP, SWAP), ARTCC center codes, the FAA pacing airports with time zones, and accepted identifier formats.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: 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 outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- 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:30 UTC, unchanged since Oct 22, 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
- 0
- 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
Findings
Matches of fixed checks, with the text they matched.
The description names a tool "faa_delays" that this server does not list.
What this check looks forMatched text
description: "Decode the vocabulary the other faa_delays tools return: event types and their fields, t..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:faa_delays_get_operations_planOnly readsdescription
- Changed:faa_delays_list_active_eventsOnly readsdescription
Tools3 changed.~3 changedView diff
- Changed:faa_delays_get_airport_statusOnly readsdescription
- Changed:faa_delays_list_active_eventsOnly readsdescription
- Changed:faa_delays_list_advisoriesOnly readsinputSchema
Install
Pinned to version 0.3.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http faa-traffic-delays https://faa-traffic-delays.caseyjhand.com/mcpclaude mcp add --transport http faa-traffic-delays https://faa-traffic-delays.caseyjhand.com/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": [
"mcp__faa-traffic-delays__faa_delays_get_airport_status",
"mcp__faa-traffic-delays__faa_delays_list_active_events",
"mcp__faa-traffic-delays__faa_delays_get_operations_plan",
"mcp__faa-traffic-delays__faa_delays_get_advisory",
"mcp__faa-traffic-delays__faa_delays_list_advisories",
"mcp__faa-traffic-delays__faa_delays_list_reference"
],
"ask": [],
"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-traffic-delays. Review it before you use it.
Capability tags behind 6 rules
- mcp__faa-traffic-delays__faa_delays_get_airport_status untrusted-input
- mcp__faa-traffic-delays__faa_delays_list_active_events untrusted-input
- mcp__faa-traffic-delays__faa_delays_get_operations_plan untrusted-input
- mcp__faa-traffic-delays__faa_delays_get_advisory untrusted-input
- mcp__faa-traffic-delays__faa_delays_list_advisories private-data, untrusted-input
- mcp__faa-traffic-delays__faa_delays_list_reference 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/io.github.cyanheads/faa-traffic-delays-mcp-server/verify?hash=6de3be8535f744bea962395210fc0f89dde98146b6bca97dcaf55907792dbd78" | jq -e '.changed == false'Pinned hash 6de3be8535f7, from Nov 21, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/faa-traffic-delays-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/faa-traffic-delays-mcp-server)Source: MCP Registry · repository. Synced Nov 21, 2026, 18:17 UTC.
faa-traffic-delays-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the faa-traffic-delays-mcp-server safe?
- No scan can promise that. What its definitions show: 6 tools, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.
Can the faa-traffic-delays-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-traffic-delays-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-traffic-delays-mcp-server have?
- 6 tools: 6 read. faa_delays_get_airport_status, faa_delays_list_active_events, faa_delays_get_operations_plan, faa_delays_get_advisory, faa_delays_list_advisories and faa_delays_list_reference.
Does the faa-traffic-delays-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the faa-traffic-delays-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-traffic-delays-mcp-server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.