Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Authorization not required, issuer https://auth.airsidelabs.com
Authorization not required, issuer https://auth.airsidelabs.com
Authorization not required, issuer https://auth.airsidelabs.com
Authorization not required, issuer https://auth.airsidelabs.com
Changed the definition of "airframe_flights", "flight_airframes", "report_unmet_need" and 1 more
⟨131 unchanged words⟩ carried in the window. Why this matters:it is the most-asked question the resolution tools could not answer --movement history for a tail. A fleet-watching, lessor or MRO agent thathas resolved aregistration wants to know what it has beendoing, anddoing; thisisanswer comes from what theonlyreceiverplaceheardthatand
Changed the definition of "airport_fleet_mix" and "route_capacity"
⟨112 unchanged words⟩ not from a schedule or a fleet list. Airports may be given as an IATA code, an ICAO code or a name. T-100 is filed under three-character codes that follow IATA, so an ICAO code or a name is resolved to the airport's IATA code first and the answer says so in its first note; `query` echoes the code that was looked up. Reading the answer: `status` is resolved, no_service orno_service.unresolved. `unresolved` means nothing was looked up (no airport matches, or it has no IATA code) and is never a statement about service. `totals` and `monthly` are sums of BTS-reported departures ⟨107 unchanged words⟩
Authorization not required, issuer https://auth.airsidelabs.com
Added "airframe_flights" and "airport_runways" (27 tools before, 29 now)
Airframe flights — Which flights has this airframe been heard or filed operating, how often and when -- the inverse of flight_airframes, from Airside Labs' own ADS-B receiver and the FAA flight-plan feed? Accepts a registration in any common form (G-XWBA, N101DU, PH-BHA) or a Mode-S address (406a3d). A registration is resolved first, so `as_of` matters for a re-issued mark: the answer names the airframe it resolved to and the Mode-S address(es) it looked up. Returns each Flight ID the airframe was heard broadcasting within the receiver's footprint, or was filed under in FAA flight plans, with sightings (receiv…
Airport runways — What runways does this aerodrome publish in its state AIP, with what dimensions, surface, bearings, thresholds and declared distances, and for which AIRAC cycle? Returns every runway the state's export lists for the aerodrome: designator, length and width, surface and PCN, the runway strip, and per direction the threshold coordinates, true and magnetic bearing, the approach slope indicator (PAPI or VASIS type, slope and MEHT) and the four declared distances TORA, TODA, ASDA and LDA. Every length is `{"m": ...}`; where the publisher states feet it is `{"m": ..., "published": {"value": ..., "u…
Authorization not required, issuer https://auth.airsidelabs.com
Authorization not required, issuer https://auth.airsidelabs.com
Added "airport_fleet_mix", "flight_airframes", "get_scenario" and 2 more; changed the definition of "data_requirements", "easa_ai_framework", "get_use_case" and 5 more (22 tools before, 27 now)
⟨423 unchanged words⟩ feeds) attached to the use cases itillustrates.illustrates, and `scenario` is one real day reconstructed from those feeds with a traceable timeline. The EASA level and hazard on a use ⟨39 unchanged words⟩
⟨266 unchanged words⟩ feeds) attached to the use cases itillustrates.illustrates, and `scenario` is one real day reconstructed from those feeds with a traceable timeline.
Authorization not required, issuer https://auth.airsidelabs.com
Authorization not required, issuer https://auth.airsidelabs.com
Changed the definition of "data_requirements", "easa_ai_framework", "get_use_case" and 5 more
⟨393 unchanged words⟩ knowledge and `knowledge:workflow` is authored operational sequencestructure.structure, and `data_story` is a measured, dated finding from data Airside Labs holds (its own ADS-B receiver, FAA flight-plan and BTS traffic feeds) attached to the use cases it illustrates. The EASA level and hazard on a use case are a title-level screen with a confidence, not a certificationfinding, andfinding; a workflow is not an operatingprocedure.procedure; a data story is not live and not a statistic about the industry -- read its `applies_when` before quoting it.
Authorization not required, issuer https://auth.airsidelabs.com
Certificate recorded, valid to 2026-11-25
Authorization not required, issuer https://auth.airsidelabs.com
First tool surface recorded: 22 tools (server version 1.1.0)
Showing the latest 18 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed
⟨134 unchanged words⟩ inside. A seat-finding or fleet-watching agent needs thetail, andtail; thisis theansweronlycomesplacefromitwhatcomesthefrom observationreceiverratherobserved,thannot from a schedule. Coverage is the station's footprint: ⟨96 unchanged words⟩
⟨50 unchanged words⟩ what is missing. A need reported here isreadappended to this service's own feedback store, on the same server that answered you, and reviewed later byaAirsideperson.Labs; nothing is sent to any other system. Use it when: - a tool returned ⟨234 unchanged words⟩
{"destructiveHint":false,"idempotentHint":false,"openWorldHint":falsetrue,"readOnlyHint":false,"title":"Report unmet need"}
LeaveRecord a suggestionforaboutAirsidethisLabs.toolset or its use-case catalogue. No APIkey is needed for this tool.ThisThe suggestion isthewrittensuggestionasboxoneforrecordtheintoaviationthisuse-caseserver'scatalogueown local feedback store andthe toolsnothingthatelseservehappens:it.noIfmessage,younotification,areemail oranrequestAIgoesagenttothatanyreadwebsite,apersonuse-caseorpageotheron airsidelabs.comsystem,—now orcalledlater,aand the toolheredoes—notandreadnoticedthesomething,storethisback.isAirside Labs reads the store when preparing thechannelnext version of the catalogue and the tools. Use it for: a correction to apublishedcatalogue use case, an aviation AI use case ⟨26 unchanged words⟩ would make the full toolset worth a subscriptionto your operator). `suggestion` is the important field: say ⟨32 unchanged words⟩ by get_use_case) or the `page_slug` of theairsidelabs.comcatalogue page ityoucameread.from. `contact` isoptional:anaddressfree-textorfieldURLstoredifwithyourtheoperatorrecordwantsandausedreplyfor—nothing else; leave it outotherwise,unlessandthedouser asked for it. Do not submitpersonal data, conversation history or customeridentifiers; text islength-capped and thelog is readstoredbyrecordaispersontreated asuntrusted content.Nothing answers this in real time:Filing arecordedsuggestionis reviewed by a human later, and filing onedoes not change any answer you have already receivedreceived.and produces no reply. Returns a receipt saying whetheritthewasrecordrecorded.was stored.
{"destructiveHint":false,"idempotentHint":false,"openWorldHint":falsetrue,"readOnlyHint":false,"title":"Submit suggestion"}
⟨151 unchanged words⟩ yield yourself: fares are not held here. Airports may be given as an IATA code, an ICAO code or a name. T-100 is filed under three-character codes that follow IATA, so an ICAO code or a name is resolved to the airport's IATA code first and the answer says so in its first note; `query` echoes the code that was looked up. Reading the answer: `status` is resolved, no_service orno_service.unresolved. `unresolved` means nothing was looked up (no airport matches, or it has no IATA code) and is never a statement about service. `totals` and `monthly` are sums of BTS-reported departures ⟨107 unchanged words⟩
⟨435 unchanged words⟩ feeds) attached to the use cases itillustrates.illustrates, and `scenario` is one real day reconstructed from those feeds with a traceable timeline. The EASA level and hazard on a use ⟨39 unchanged words⟩
⟨339 unchanged words⟩ feeds) attached to the use cases itillustrates.illustrates, and `scenario` is one real day reconstructed from those feeds with a traceable timeline. The EASA level and hazard on a use ⟨39 unchanged words⟩
⟨250 unchanged words⟩ feeds) attached to the use cases itillustrates.illustrates, and `scenario` is one real day reconstructed from those feeds with a traceable timeline. The EASA level and hazard on a use ⟨39 unchanged words⟩
⟨372 unchanged words⟩ feeds) attached to the use cases itillustrates.illustrates, and `scenario` is one real day reconstructed from those feeds with a traceable timeline. The EASA level and hazard on a use ⟨39 unchanged words⟩
⟨479 unchanged words⟩ feeds) attached to the use cases itillustrates.illustrates, and `scenario` is one real day reconstructed from those feeds with a traceable timeline. The EASA level and hazard on a use ⟨39 unchanged words⟩
⟨259 unchanged words⟩ feeds) attached to the use cases itillustrates.illustrates, and `scenario` is one real day reconstructed from those feeds with a traceable timeline. The EASA level and hazard on a use ⟨39 unchanged words⟩
Airport fleet mix — What aircraft types fly from (or into) an airport, how often, with how many seats, and at what load factor, over the last N months of BTS T-100 data? Returns each type's departures performed and share of the airport's departures, seats, passengers, load factor, seats per departure, and how many carriers and destinations it serves, plus airport totals. `direction` is `departures` (default) or `arrivals`. `months` defaults to the last 12 of the window; pass null for the whole window. Scheduled passenger service only. This is the fleet-mix question a planner asks before sizing a route or a gat…
Flight airframes — Which airframes have been heard operating this airline flight, how often and when -- from Airside Labs' own ADS-B receiver? Accepts a flight in any common form: BA49, BAW49, "BA 49", VS105. Returns each airframe heard broadcasting that Flight ID within the receiver's footprint, with its Mode-S address, registration and ICAO type (joined from the registrations dataset), how many receiver poll cycles it was in view for, over how many distinct days, and first and last heard. `most_seen` and `most_recent` name the likeliest next tail; `types_seen` lists every type that has flown it, and where th…
Get a real-day scenario — One real episode end to end: what happened, where and when (UTC), the actors, what it shows and what it must not be read as; the timeline, every event with its actor, source and the reference of the raw record it came from; and the lenses, each a use case's cut of the day with a small evidence table, an implication, and the use cases it illustrates with a reason for each. Use it when a brief needs the whole story rather than one finding: a worked example with a paper trail, an edge-case write-up for a data science team, a workshop narrative. For one use case's view, take the lens from get_us…
Route capacity — How much scheduled capacity is flown nonstop from one airport to another, by whom and on what, over the last N months of BTS T-100 data? Returns monthly departures performed, seats and passengers with the load factor, and the same broken down by carrier and aircraft type with seats per departure and the sector distance (BTS statute miles, and nautical miles converted). The pair is DIRECTIONAL: SEA to LHR is not LHR to SEA; ask both if you need the round trip. `months` defaults to the last 12 of the window; pass null for the whole window. `scheduled_only` (default true) restricts to scheduled…
List real-day scenarios — Which real operational episodes does the catalogue carry, to illustrate use cases with? A scenario is one real day reconstructed from data Airside Labs holds and may publish: FAA SWIM flight plans, FAA NOTAMs, its own ADS-B receiver. Each is a UTC window at a place, a timeline whose every event names the raw record it came from, and a set of lenses -- one use case's cut of the day, with the actual rows, an implication, and the use cases it is attached to. This lists them with their window, place, event and lens counts and how many use cases they touch. Fetch one with get_scenario; the lenses…
⟨236 unchanged words⟩ knowledge and `knowledge:workflow` is authored operational sequencestructure.structure, and `data_story` is a measured, dated finding from data Airside Labs holds (its own ADS-B receiver, FAA flight-plan and BTS traffic feeds) attached to the use cases it illustrates. The EASA level and hazard on a use case are a title-level screen with a confidence, not a certificationfinding, andfinding; a workflow is not an operatingprocedure.procedure; a data story is not live and not a statistic about the industry -- read its `applies_when` before quoting it.
⟨75 unchanged words⟩ framework rows it points at, page-cited; keywords; up to three `data_stories`; and the fivenearest use cases by text similarity. A data story is what this use case's data does when you actually touch it: a measured finding from Airside Labs' own receiver, the FAA flight-plan feed, BTS traffic data or the served entity registry -- a fill rate, a reused identifier, an ambiguous timestamp, the reach of one sensor. Each carries `claim` (the finding, with its scope in the sentence), `implication` (what to do about it), `identifiers` (exact ids to test with), `evidence` (a small table), `sources` with editions and windows, `caveats` and `not_to_be_read_as`. Put the claim in the requirements section, the identifiers in the test plan, and cite the source and window. A use case with no data stories is undecorated, not unillustratable. Use this for the few worked examples an ⟨109 unchanged words⟩ rows by their cp_ref if you quote them. Do NOT generalise a data story past its `applies_when`: one receiver, three US airports and one data edition are a witness, not a survey. Every response carries `provenance`: `corpus` is Airside ⟨39 unchanged words⟩ knowledge and `knowledge:workflow` is authored operational sequencestructure.structure, and `data_story` is a measured, dated finding from data Airside Labs holds (its own ADS-B receiver, FAA flight-plan and BTS traffic feeds) attached to the use cases it illustrates. The EASA level and hazard on a use case are a title-level screen with a confidence, not a certificationfinding, andfinding; a workflow is not an operatingprocedure.procedure; a data story is not live and not a statistic about the industry -- read its `applies_when` before quoting it.
⟨154 unchanged words⟩ 3B) and `hazard_class` (H1-H5) imply it. Each result carries `data_stories`, the number of measured findings attached to that use case (see get_use_case); prefer a decorated record when two read alike, because it comes with evidence you can put in front of a reviewer. Do NOT use this to establish whether an ⟨103 unchanged words⟩ knowledge and `knowledge:workflow` is authored operational sequencestructure.structure, and `data_story` is a measured, dated finding from data Airside Labs holds (its own ADS-B receiver, FAA flight-plan and BTS traffic feeds) attached to the use cases it illustrates. The EASA level and hazard on a use case are a title-level screen with a confidence, not a certificationfinding, andfinding; a workflow is not an operatingprocedure.procedure; a data story is not live and not a statistic about the industry -- read its `applies_when` before quoting it.
⟨220 unchanged words⟩ knowledge and `knowledge:workflow` is authored operational sequencestructure.structure, and `data_story` is a measured, dated finding from data Airside Labs holds (its own ADS-B receiver, FAA flight-plan and BTS traffic feeds) attached to the use cases it illustrates. The EASA level and hazard on a use case are a title-level screen with a confidence, not a certificationfinding, andfinding; a workflow is not an operatingprocedure.procedure; a data story is not live and not a statistic about the industry -- read its `applies_when` before quoting it.
⟨97 unchanged words⟩ time, count, weight, identifier, status),andthe families itserves.serves, and `data_stories` -- what Airside Labs measured about that message type in real feeds (fill rates, identifier traps), each with its window and source. With no arguments: the catalogue of ~23 message ⟨204 unchanged words⟩ knowledge and `knowledge:workflow` is authored operational sequencestructure.structure, and `data_story` is a measured, dated finding from data Airside Labs holds (its own ADS-B receiver, FAA flight-plan and BTS traffic feeds) attached to the use cases it illustrates. The EASA level and hazard on a use case are a title-level screen with a confidence, not a certificationfinding, andfinding; a workflow is not an operatingprocedure.procedure; a data story is not live and not a statistic about the industry -- read its `applies_when` before quoting it.
⟨449 unchanged words⟩ knowledge and `knowledge:workflow` is authored operational sequencestructure.structure, and `data_story` is a measured, dated finding from data Airside Labs holds (its own ADS-B receiver, FAA flight-plan and BTS traffic feeds) attached to the use cases it illustrates. The EASA level and hazard on a use case are a title-level screen with a confidence, not a certificationfinding, andfinding; a workflow is not an operatingprocedure.procedure; a data story is not live and not a statistic about the industry -- read its `applies_when` before quoting it.
⟨229 unchanged words⟩ knowledge and `knowledge:workflow` is authored operational sequencestructure.structure, and `data_story` is a measured, dated finding from data Airside Labs holds (its own ADS-B receiver, FAA flight-plan and BTS traffic feeds) attached to the use cases it illustrates. The EASA level and hazard on a use case are a title-level screen with a confidence, not a certificationfinding, andfinding; a workflow is not an operatingprocedure.procedure; a data story is not live and not a statistic about the industry -- read its `applies_when` before quoting it.