General Tools

airsidelabs.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint27 known toolsFirst detected September 11, 2026Last detected September 21, 2026

ENDPOINT 1

https://mcp.airsidelabs.com/mcp

No auth detected

MCP server metadata

Name: Airside Labs Aviation Tools
Version: 1.2.0

Capabilities

experimentalpromptsresourcestools

Server instructions

Aviation tools from Airside Labs. Identity: five tools resolve identifiers -- airports, airlines, aircraft types, registrations, flight designators -- to canonical entities with confidence, alternates, temporal validity and per-field provenance, and validate_identifiers checks a set of them against each other on a date. Context: ten use-case atlas tools answer what AI use cases exist for an organisation type or role, what data each needs and how fresh, which standard messages would carry it, where it sits in an operational sequence, how it screens against the EASA AI-level and hazard framework, and what else is like it -- start with use_case_landscape, search with operational nouns, fetch the few full records an argument needs. A full record may carry data stories: measured, dated findings from Airside Labs' own receiver and approved public feeds showing what that data does when touched; scenarios and get_scenario give whole real days with a traceable timeline and the lenses cut from them. Quote a story or a scenario with its source and window, never as live data or an industry statistic. use_case_landscape, get_use_case and submit_suggestion need no API key (a per-address daily cap applies). report_unmet_need is how to tell us what you could not get; submit_suggestion is the open suggestion box — corrections, missing use cases, data sources, feature or commercial feedback. Internally three more tools adjudicate airport charges against encoded contract clauses. Pass as_of for any historical identity question: codes are reused and an undated answer is silently wrong for past data. An unresolved, empty or unadjudicable result is a real answer, not an error.

Known tools 27

resolve_airport

Which aerodrome does this airport code or name refer to on a given date?

Inferred read-only

resolve_airline

Which airline does this designator, name or callsign refer to on a date?

Inferred read-only

resolve_aircraft_type

Which aircraft type does this designator or marketing name refer to?

Inferred read-only

resolve_registration

Which airframe wore this registration on a given date?

Inferred read-only

parse_flight_identifier

Split a flight designator into carrier and number, and identify the carrier.

Inferred read-only

flight_airframes

Which airframes have been heard operating this airline flight, how often and when -- from Airside Labs' own ADS-B receiver?

Inferred read-only

validate_identifiers

Do these aviation identifiers describe the same thing on this date?

Inferred read-only

report_unmet_need

Tell us what you came looking for and could not get from these tools.

Inferred read-only

use_case_landscape

How many use cases are there, sliced one way?

Inferred read-only

search_use_cases

Which aviation AI use cases match this text?

Inferred read-only

get_use_case

The full record for one use case, by id from a search or landscape result.

Inferred read-only

similar_use_cases

What else in the catalogue is like this use case?

Inferred read-only

data_requirements

What data does this use case, role or organisation type need, and how fresh?

Inferred read-only

trace_data_lineage

Which standard operational messages would evidence this data need?

Inferred read-only

trace_workflow

What happens before and after this use case, and who hands off to whom?

Inferred read-only

easa_ai_framework

The EASA AI-level and hazard-class tables, page-cited, to read a screen against.

Inferred read-only

scenarios

Which real operational episodes does the catalogue carry, to illustrate use cases with?

Inferred read-only

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

Inferred read-only

airport_network_integration

What level of network integration does this airport have with the EUROCONTROL Network Manager, or with the FAA's TFDM programme, as of a date?

Inferred read-only

airport_operator

Who operates this airport, which group would take the commercial meeting, and who owns it?

Inferred read-only

airport_operations_status

Is there a positive, sourced reason this airport is not open for ordinary commercial engagement: closed to civil traffic, in a sanctioned jurisdiction, or a general-aviation field with no scheduled service?

Inferred read-only

airport_connectivity

How many nonstop destinations does this airport publish, and in which countries?

Potential side effects

airport_size_band

Which ACI passenger size band is this airport in, on its latest published annual total?

Inferred read-only

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?

Inferred read-only

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?

Inferred read-only

submit_suggestion

Leave a suggestion for Airside Labs.

Inferred read-only

feedback_status

What happened to a suggestion or unmet-need report filed here?

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.airside-labs-aviation-tools]
url = "https://mcp.airsidelabs.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "airside-labs-aviation-tools": {
      "type": "http",
      "url": "https://mcp.airsidelabs.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: airside-labs-aviation-tools
Remote MCP URL: https://mcp.airsidelabs.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "airside-labs-aviation-tools": {
      "url": "https://mcp.airsidelabs.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "airside-labs-aviation-tools": {
      "type": "http",
      "url": "https://mcp.airsidelabs.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "airside-labs-aviation-tools",
  "transport": "streamable-http",
  "url": "https://mcp.airsidelabs.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.