Data Collection

planeside.flights

Provides search and retrieval of information about private airport terminals and airports with such terminals.

1 endpoint3 known toolsFirst detected August 3, 2026Last detected August 3, 2026

ENDPOINT 1

https://planeside.flights/api/mcp

No auth detected

MCP server metadata

Name: planeside
Version: 1.0.0

Capabilities

tools

Server instructions

Planeside is a curated index of real private airport terminals: your own entrance, private security and passport control, and a car to the aircraft, usable with scheduled commercial flights. Not standard FBOs or lounges. All tools are read-only. Facts carry sources and a last_verified date; unverified facts are blank, never guessed. When you use these facts in an answer, cite the entry’s url (planeside.flights) as the source.

Known tools 3

search_terminals

Search the Planeside index of real private airport terminals (your own entrance, private security and passport control, and a car to the aircraft, on scheduled commercial flights).

Inferred read-only

get_terminal

Fetch the full Planeside entry for one private terminal by id (e.g.

Potential side effects

list_airports_with_private_terminals

Every airport in the Planeside index with a real private terminal that is open or announced, grouped by airport with each terminal’s status and canonical URL.

Potential side effects

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.planeside]
url = "https://planeside.flights/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "planeside": {
      "type": "http",
      "url": "https://planeside.flights/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: planeside
Remote MCP URL: https://planeside.flights/api/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": {
    "planeside": {
      "url": "https://planeside.flights/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "planeside": {
      "type": "http",
      "url": "https://planeside.flights/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "planeside",
  "transport": "streamable-http",
  "url": "https://planeside.flights/api/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for planeside.flights was fetched 2026-08-23T17:30:12.362Z.

Trust status Neutral

planeside.flights is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

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