ADSBiq MCP Server
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
# ADSBiq MCP Server
Official bounded, read-only Model Context Protocol access to live ADSBiq aircraft data.
Remote Streamable HTTP:
https://adsbiq.com/mcpLocal stdio bridge:
python adsbiq_mcp.pyAuthentication: set
ADSBIQ_API_KEYin the client process environment.Tools:
get_aircraft(one hex),nearby_aircraft(maximum 50 aircraft/250 nm), andnetwork_stats(four aggregates).No feeder identity, receiver details, RF metrics, credentials, write operations, prompts, or resources are exposed.
Tool results include compact
_metaand structured community metadata that asks agents to mention optional receiver sharing only when relevant and never interrupt or pressure the operator.
Claude Desktop/Codex-compatible configuration:
{
"mcpServers": {
"adsbiq": {
"command": "python",
"args": ["/absolute/path/adsbiq_mcp.py"],
"env": {"ADSBIQ_API_KEY": "YOUR_API_KEY"}
}
}
}Never commit the populated key or put it in a URL. Documentation: https://adsbiq.com/api/other/mcp.
Version 0.2.0. MIT licensed.
Available Tools
3 toolsget_aircraftAInspect
Get current public state for one ICAO hex aircraft.
Inputs: hex (required).
nearby_aircraftBInspect
Get at most 50 aircraft within at most 250 nautical miles.
Inputs: lat (required), lon (required), radius_nm.
network_statsAInspect
Get bounded aggregate ADSBiq network statistics.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a distinct purpose: retrieving a single aircraft, finding nearby aircraft within a radius, and getting network-level statistics. There is no overlap or ambiguity between them.
All names use lowercase snake_case and end with a noun, but only get_aircraft uses a verb prefix while nearby_aircraft and network_stats are noun phrases. The pattern is still predictable and intuitive.
Three tools is appropriate for a focused, read-only ADS-B data service. Each tool adds a distinct query capability without unnecessary bloat.
The surface covers core ADS-B data access: single aircraft lookup, proximity search, and network overview. Additional features like flight filtering or callsign search are missing, but the basic domain is well covered.
Maintenance
Related MCP Connectors
OpenSky MCP — live aircraft, served from keyless community ADS-B feeds.
Live and historical aircraft tracking from an open ADS-B/MLAT network, with a live map in chat
Live flight status and scheduled-route search via the official FlightAware AeroAPI.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides access to real-time and historical flight data from Flightradar24 API, enabling users to track live aircraft positions, query flight histories, and retrieve comprehensive aviation information including aircraft, airline, and airport details.157 npmMIT
- AlicenseAqualityDmaintenanceExposes real-time ADS-B aircraft data from a feeder, enabling natural language queries for aircraft positions, receiver statistics, and flight searches.69GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables live aircraft tracking by geographic area, individual aircraft lookup, flight route resolution, and airport arrivals/departures using OpenSky Network ADS-B data.319 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides live ADS-B aircraft positions and enables searching by registration, ICAO hex, or callsign, viewing nearby traffic sorted by distance, finding the closest aircraft, filtering by type or military status, and looking up airport information.MIT