{"id":"com.airsidelabs/aviation-tools","slug":"com-airsidelabs-aviation-tools","title":"Airside Labs Aviation Tools","description":"Aviation identity resolution and an AI use-case atlas, with provenance and temporal validity","version":"1.3.0","publisher":{"kind":"domain","id":"airsidelabs.com","label":"airsidelabs.com","url":"https://airsidelabs.com"},"website":"https://airsidelabs.com/tools/docs","repository":"","remotes":[{"type":"streamable-http","url":"https://mcp.airsidelabs.com/mcp","headers":[{"description":"Optional. An Airside Labs API key, as an alternative to signing in with OAuth. Three tools (use_case_landscape, get_use_case, submit_suggestion) need neither, subject to a per-address daily cap.","isSecret":true,"name":"X-API-Key"}]}],"packages":[],"published":"2026-10-01","updated":"2026-10-01","status":"online","auth":"","latency_ms":972,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"resolve_airport","title":"Resolve airport","description":"Which aerodrome does this airport code or name refer to on a given date?\n\nAccepts an IATA three-letter code, an ICAO four-letter code, an airport\nname fragment or a city name. Returns the aerodrome with its codes,\nlocation, elevation, IANA timezone and type (large, medium, small,\nheliport or closed).\n\nPass `as_of` whenever the question concerns a past date. Airport codes move\nbetween aerodromes: A","read_only":true},{"name":"resolve_airline","title":"Resolve airline","description":"Which airline does this designator, name or callsign refer to on a date?\n\nAccepts an IATA two-character designator, an ICAO three-letter designator,\nan airline name or a callsign. Returns the operator with both designators,\ncountry, operational status and, where an airline ceased, its successor.\n\n`as_of` matters more here than for any other tool. IATA two-character\ndesignators are heavily reused: ","read_only":true},{"name":"resolve_aircraft_type","title":"Resolve aircraft type","description":"Which aircraft type does this designator or marketing name refer to?\n\nAccepts an ICAO type designator (A21N) or a marketing name people actually\nsay (\"A321neo\", \"Dash 8-400\", \"777-300ER\", \"Q400\"). Returns the ICAO\ndesignator, manufacturer, model, engine count and type, aircraft class, and\nthe ICAO wake turbulence category.\n\nA name that identifies a family rather than a variant -- \"Dreamliner\",\n\"77","read_only":true},{"name":"resolve_registration","title":"Resolve registration","description":"Which airframe wore this registration on a given date?\n\nAccepts a tail number in any common form: VH-OQA, VHOQA, lowercase, padded\nwith whitespace. Returns the aircraft with its country of registry, ICAO\ntype designator, an embedded resolved aircraft type, operator, owner,\nserial number and Mode-S hex address.\n\nA registration is a slot rather than a permanent name: marks are\nsurrendered and reissu","read_only":true},{"name":"parse_flight_identifier","title":"Parse flight identifier","description":"Split a flight designator into carrier and number, and identify the carrier.\n\nAccepts the forms that arrive in real message traffic: TK1979, BAW276,\n\"U2 8341\", BA02490, BA2490A. Returns the parsed carrier with its resolved\nairline, the flight number, any operational suffix, which scheme was used\n(IATA or ICAO), and both normalised forms.\n\nTwo things this tool will not do. It will not tell you who ","read_only":true},{"name":"flight_airframes","title":"Flight airframes","description":"Which airframes have been heard operating this airline flight, how often and when --\nfrom Airside Labs' own ADS-B receiver?\n\nAccepts a flight in any common form: BA49, BAW49, \"BA 49\", VS105. Returns each airframe\nheard broadcasting that Flight ID within the receiver's footprint, with its Mode-S\naddress, registration and ICAO type (joined from the registrations dataset), how many\nreceiver poll cycl","read_only":true},{"name":"airframe_flights","title":"Airframe flights","description":"Which flights has this airframe been heard or filed operating, how often and when --\nthe inverse of flight_airframes, from Airside Labs' own ADS-B receiver and the FAA\nflight-plan feed?\n\nAccepts a registration in any common form (G-XWBA, N101DU, PH-BHA) or a Mode-S address\n(406a3d). A registration is resolved first, so `as_of` matters for a re-issued mark: the\nanswer names the airframe it resolved","read_only":true},{"name":"validate_identifiers","title":"Validate identifiers","description":"Do these aviation identifiers describe the same thing on this date?\n\nGive any combination of a registration (tail number), a Mode-S 24-bit\naddress, an ICAO type designator, an operator name, an airline designator\n(IATA or ICAO), a callsign and a flight designator, plus `as_of`. Each\npair that can be checked is checked, and every check comes back with a\nverdict -- `consistent`, `contradicted` or `u","read_only":true},{"name":"report_unmet_need","title":"Report unmet need","description":"Tell us what you came looking for and could not get from these tools.\n\nCall this when you needed something aviation-related that this toolset did\nnot give you. It is not an error channel and it is not a retry: it is how\nthe next version of these tools learns what is missing. A need reported\nhere is appended to this service's own feedback store, on the same server\nthat answered you, and reviewed la","read_only":false},{"name":"use_case_landscape","title":"Use-case landscape","description":"How many use cases are there, sliced one way? Counts you can quote.\n\n`group_by` is one of org_type (16 canonical organisation types: Airport,\nAirline, Air Navigation Service Provider, Ground Handling, Regulator /\nAuthority, Aerospace Manufacturing, MRO / Maintenance …), sector, role\n(500+ roles), ai_level, hazard_class, or cadence_class (counts data\nrequirements rather than use cases). Filters AND","read_only":true},{"name":"search_use_cases","title":"Search use cases","description":"Which aviation AI use cases match this text? Find candidates by keyword.\n\nFull-text search (BM25, stemmed) over 6,500 use cases spanning airports,\nairlines, ANSPs, ground handlers, regulators, manufacturers and more, each\nattached to a role and an organisation type. Returns summaries only --\nid, short text, role, organisation type, EASA screen -- capped at 25.\nUse get_use_case for the full record ","read_only":true},{"name":"get_use_case","title":"Get use case","description":"The full record for one use case, by id from a search or landscape result.\n\nReturns the use-case text; the role that owns it with its description; the\norganisation type (canonical and as the corpus names it); every data\nrequirement -- title, description, nominal update rate with a normalised\ncadence class (real_time … annual), and the kind of system it typically\ncomes from; the EASA screen (AI lev","read_only":true},{"name":"similar_use_cases","title":"Similar use cases","description":"What else in the catalogue is like this use case? Nearest neighbours by meaning.\n\nReturns up to 20 use cases closest in embedding space (bge-base cosine\nover the use-case text), as summaries with a `similarity`. Good for \"what\nelse is like the one we picked\", for finding the same idea stated for a\ndifferent role or organisation type, and for spotting near-duplicates\nbefore counting them as two.\n\nS","read_only":true},{"name":"data_requirements","title":"Data requirements","description":"What data does this use case, role or organisation type need, and how fresh?\n\nThree modes. With `use_case_id`: that use case's requirements verbatim --\ntitle, normalised title_family, description, nominal update rate,\nnormalised cadence class and the kind of source system. With `query`:\nREVERSE lineage -- full-text search over requirement titles and\ndescriptions (the inputs, not the use-case text)","read_only":true},{"name":"trace_data_lineage","title":"Trace data lineage","description":"Which standard operational messages would evidence this data need?\n\nThe lineage spine is use case -> data requirement -> requirement family ->\nstandard message type -> data elements. Four modes. With `use_case_id`:\nthat use case's requirements grouped by family, each family with the\nstandard messages that evidence it (relevance primary/supporting, cadence,\nelement count) -- plus `requirements_with","read_only":true},{"name":"trace_workflow","title":"Trace operational workflow","description":"What happens before and after this use case, and who hands off to whom?\n\nThe catalogue is otherwise flat -- role, use case, data requirement -- with\nno edges. This is the edges: named operational sequences with their steps in\norder, the role at each step, the `gate` that must hold before the next one\nmay start, and what passes between roles at each handoff (headset, radio,\nhand signal, system, vis","read_only":true},{"name":"easa_ai_framework","title":"EASA AI framework screen","description":"The EASA AI-level and hazard-class tables, page-cited, to read a screen against.\n\nReturns the AI levels (0, 1A, 1B, 2A, 2B, 3A, 3B: what the system does and\nhow much authority the end user keeps), the hazard classes (H1-H5: worst\ncredible effect and the assurance level it implies at acceptable and\nmoderate risk), the technique ceilings (which AI techniques the Concept\nPaper accepts up to which lev","read_only":true},{"name":"scenarios","title":"List real-day scenarios","description":"Which real operational episodes does the catalogue carry, to illustrate use cases with?\n\nA scenario is one real day reconstructed from data Airside Labs holds and\nmay publish: FAA SWIM flight plans, FAA NOTAMs, its own ADS-B receiver. Each\nis a UTC window at a place, a timeline whose every event names the raw\nrecord it came from, and a set of lenses -- one use case's cut of the day,\nwith the actua","read_only":true},{"name":"get_scenario","title":"Get a real-day scenario","description":"One real episode end to end: what happened, where and when (UTC), the actors,\nwhat it shows and what it must not be read as; the timeline, every event with its\nactor, source and the reference of the raw record it came from; and the lenses,\neach a use case's cut of the day with a small evidence table, an implication, and\nthe use cases it illustrates with a reason for each.\n\nUse it when a brief need","read_only":true},{"name":"airport_network_integration","title":"Airport network integration","description":"What level of network integration does this airport have with the EUROCONTROL Network\nManager, or with the FAA's TFDM programme, as of a date?\n\nAnswers with one value: `ani` (Advanced Network Integrated: A-CDM with the higher level of\nintegration), `acdm` (all DPI message types sent to the network, so a TOBT and TSAT stream\nexists), `adv_twr` (Advanced ATC TWR: E-DPI, C-DPI and A-DPI only, no TOBT","read_only":true},{"name":"airport_operator","title":"Airport operator","description":"Who operates this airport, which group would take the commercial meeting, and who owns\nit?\n\nReturns operator_name, operator_group (the parent that a sales or partnership conversation\nlands with, spelled consistently: Aena, MAG, Groupe ADP, Fraport, VINCI Airports, Adani and\nso on), ownership_class (public-national, public-regional, private-group,\nprivate-individual, concession-mixed or unknown), o","read_only":true},{"name":"airport_operations_status","title":"Airport operations status","description":"Is there a positive, sourced reason this airport is not open for ordinary commercial\nengagement: closed to civil traffic, in a sanctioned jurisdiction, or a general-aviation\nfield with no scheduled service?\n\nReturns `closed` (no civil passenger operations), `restricted` (the airport operates but\nsits under UK sanctions guidance for its jurisdiction, with the guidance page cited),\n`general-aviation","read_only":true},{"name":"airport_connectivity","title":"Airport connectivity","description":"How many nonstop destinations does this airport publish, and in which countries?\n\nReturns the count of nonstop destinations from the airport's published destination table,\nthe number resolved to a country, the destinations by country, and the counts to the United\nStates, the Gulf and the UAE, with the date of the read.\n\nThis is presence, not frequency: one weekly seasonal service and a daily trunk","read_only":true},{"name":"airport_size_band","title":"Airport size band","description":"Which ACI passenger size band is this airport in, on its latest published annual total?\n\nReturns the passengers figure, its year, and the band on ACI World's published ASQ size\ncategories: under 2M, 2 to 5M, 5 to 15M, 15 to 25M, 25 to 40M, over 40M passengers per year.\nThe figure comes from the airport's Wikipedia infobox (its latest published annual total),\nnot from ACI, so airports are not on a ","read_only":true},{"name":"airport_runways","title":"Airport runways","description":"What runways does this aerodrome publish in its state AIP, with what dimensions,\nsurface, bearings, thresholds and declared distances, and for which AIRAC cycle?\n\nReturns every runway the state's export lists for the aerodrome: designator, length\nand width, surface and PCN, the runway strip, and per direction the threshold\ncoordinates, true and magnetic bearing, the approach slope indicator (PAPI ","read_only":true},{"name":"route_capacity","title":"Route capacity","description":"How much scheduled capacity is flown nonstop from one airport to another, by whom and\non what, over the last N months of BTS T-100 data?\n\nReturns monthly departures performed, seats and passengers with the load factor, and the\nsame broken down by carrier and aircraft type with seats per departure and the sector\ndistance (BTS statute miles, and nautical miles converted). The pair is DIRECTIONAL:\nSE","read_only":true},{"name":"airport_fleet_mix","title":"Airport fleet mix","description":"What aircraft types fly from (or into) an airport, how often, with how many seats, and\nat what load factor, over the last N months of BTS T-100 data?\n\nReturns each type's departures performed and share of the airport's departures, seats,\npassengers, load factor, seats per departure, and how many carriers and destinations it\nserves, plus airport totals. `direction` is `departures` (default) or `arr","read_only":true},{"name":"submit_suggestion","title":"Submit suggestion","description":"Record a suggestion about this toolset or its use-case catalogue. No API\nkey is needed for this tool.\n\nThe suggestion is written as one record into this server's own local\nfeedback store and nothing else happens: no message, notification, email\nor request goes to any website, person or other system, now or later, and\nthe tool does not read the store back. Airside Labs reads the store when\npreparin","read_only":false},{"name":"feedback_status","title":"Feedback status","description":"What happened to a suggestion or unmet-need report filed here? No API key is needed.\n\nPass the `fingerprint` from a submit_suggestion or report_unmet_need receipt (12 hex\ncharacters). Returns `status`: `shipped` (a person acted on it and the change is live, with\nwhat shipped and when), `declined` (read and not taken up, with the reason), `acknowledged`\n(read, still open) or `open` (recorded, not y","read_only":true}],"server_info":{"name":"Airside Labs Aviation Tools","version":"1.3.0"},"category":"travel","tags":["security","agents","analytics"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-01","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/com-airsidelabs-aviation-tools/"}