io.github.cyanheads/faa-traffic-delays-mcp-server

Est-ce que io.github.cyanheads/faa-traffic-delays-mcp-server est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.cyanheads/faa-traffic-delays-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 6 outils

• faa_delays_get_advisory≈ 1512 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • date · string · requis
    UTC date the advisory was issued, YYYY-MM-DD: date from the same faa_delays_list_advisories row or advisory reference. MM/DD/YYYY, as advisory titles print it, and M/D/YYYY are also accepted.
  • advisory_number · integer · requis
    ATCSCC advisory number, 1–999: number from a faa_delays_list_advisories row, or advisory.number from an advisory reference on faa_delays_list_active_events, faa_delays_get_airport_status, or faa_delays_get_operations_plan. The printed forms "ADVZY 082" and "082" are also accepted.

  Exemple d'appel

  {"name": "faa_delays_get_advisory", "arguments": {"date": "texte", "advisory_number": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "url": "texte", "date": "texte", "text": "texte", "error": {}, "found": true, "shown": 1, "title": "texte", "notice": "texte", "sentAt": "texte", "subject": "texte", "guidance": "texte"}}

• faa_delays_get_airport_status≈ 3957 tokens

  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. 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • airports · array · requis
    1–100 submitted US airport codes, each a 3-character FAA location identifier (SEA, ORD, 0S9) or its ICAO code (KSEA, PHNL, TJSJ), case-insensitive; a comma-separated string is also accepted. Validates every code, deduplicates FAA/ICAO equivalents, and processes the first 25 distinct airports with the canonical remainder returned as omittedAirports. City and airport names are not accepted.

  Exemple d'appel

  {"name": "faa_delays_get_airport_status", "arguments": {"airports": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "notice": "texte", "airports": [], "fetchedAt": "texte", "processedCount": 1, "omittedAirports": []}}

• faa_delays_get_operations_plan≈ 1619 tokens

  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 current ATCSCC announcements. The advisory reference opens the full plan text with faa_delays_get_advisory, including active constraints and runway closures this summary omits.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "faa_delays_get_operations_plan", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "notice": "texte", "advisory": {}, "fetchedAt": "texte", "announcements": [], "enRoutePlanned": [], "terminalPlanned": []}}

• faa_delays_list_active_events≈ 2995 tokens

  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 (closures, ground stops, then GDPs and then AFPs each by average delay, arrival/departure delays by band maximum, closure NOTAMs, 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • event_types · array · optionnel
    Only these event types: ground_stop, ground_delay_program, airspace_flow_program, arrival_delay, departure_delay, airport_closure, closure_notam, deicing. Also accepts gs, gdp, afp, spelled-out names such as "departure delay", and a comma-separated string; case-insensitive. Omit for every type. countsByType always covers the whole feed.

  Exemple d'appel

  {"name": "faa_delays_list_active_events", "arguments": {"event_types": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "shown": 1, "events": [], "notice": "texte", "fetchedAt": "texte", "enRouteFeed": "ok", "totalActive": 1, "countsByType": {}, "appliedEventTypes": []}}

• faa_delays_list_advisories≈ 2084 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • date · string · optionnel
    UTC date to list, YYYY-MM-DD; MM/DD/YYYY and M/D/YYYY are also accepted. Omit for today (UTC). No later than tomorrow (UTC); past dates remain available.
  • limit · integer · optionnel
    Advisories per page, 1–200.
  • query · string · optionnel
    Literal case-insensitive substring of subject or any details line, such as FCA005; combined with categories and control_element before paging. Omit to match every title.
  • offset · integer · optionnel
    Matching advisories to skip, for paging: nextOffset from the previous page.
  • categories · array · optionnel
    Only advisories the FAA files under these categories: ground_stop, ground_delay_program, airspace_flow_program, ctop, route, other (flow constrained areas and operations plans file under other). Also accepts gs, gdp, afp, spelled-out names such as "ground stop", and a comma-separated string; case-insensitive. Omit for every advisory, including CDM compression advisories, which the FAA files under no category.
  • control_element · string · optionnel
    Only advisories whose control element is this facility or lists it as a part: an airport by FAA identifier (ORD) or ICAO code (KORD), an ARTCC (ZAU), a pair (ORD/ZAU or KORD/ZAU), or DCC for national advisories such as reroutes and the operations plan. Case-insensitive. Airports named only in a subject or details do not match.

  Exemple d'appel

  {"name": "faa_delays_list_advisories", "arguments": {"date": "texte", "limit": 1, "query": "texte", "offset": 1, "categories": [], "control_element": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "date": "texte", "error": {}, "shown": 1, "notice": "texte", "truncated": true, "advisories": [], "nextOffset": 1, "totalCount": 1, "appliedQuery": "texte", "appliedCategories": [], "appliedControlElement": "texte"}}

• faa_delays_list_reference≈ 1862 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • topic · string · requis · event_types | terms | artccs | pacing_airports | identifiers
    What to decode: event_types (event types and their key fields), terms (traffic-management abbreviations), artccs (ARTCC center codes and names), pacing_airports (the FAA pacing airports with time zones, read live), or identifiers (accepted airport-code, advisory, and time formats). Case-insensitive; spaces and hyphens read as underscores.

  Exemple d'appel

  {"name": "faa_delays_list_reference", "arguments": {"topic": "event_types"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "terms": [], "topic": "event_types", "artccs": [], "notice": "texte", "fetchedAt": "texte", "eventTypes": [], "identifiers": {}, "pacingAirports": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://faa-traffic-delays.caseyjhand.com/mcp