Community metadata: Live interfaces expose a small machine-readable, zero-pressure contribution hint once per response, connection, call, file, or retained topic - never per aircraft or delta. Geographic wording becomes specific only after active receiver proximity is measured. Existing receivers may share alongside current services; participation is optional.
Connect
Streamable HTTP endpoint: https://adsbiq.com/mcp
No API key is required for public trial/free access. Optionally send a feeder or publisher API key as Authorization: Bearer YOUR_API_KEY for higher limits. The endpoint implements MCP 2025-06-18, returns stateless JSON responses, and intentionally declines standalone GET/SSE streams.
curl -sS https://adsbiq.com/mcp \
-H "Accept: application/json, text/event-stream" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Bounded read-only tools
| Tool | Maximum result | Purpose |
|---|---|---|
get_aircraft | One aircraft | Current public state by six-character ICAO hex. |
nearby_aircraft | 50 aircraft, 250 nm | Geographically bounded live search. |
network_stats | Four aggregate values | Current aircraft, positioned-aircraft, and emergency counts. |
Limits and security
Initialization, ping, and tool discovery do not consume tool quotas. Public access uses the existing IP-based tiers: a 3-day trial allows one tool call every 20 seconds with a 1 GiB daily data budget; the free tier allows one call every 5 minutes with a 100 MiB daily budget. Feeder and publisher access retains 60 tool calls per minute, with a 2 GiB daily budget. Daily bytes are shared with REST and reset at UTC midnight; MCP call intervals are separate. MCP quotas are always enforced, including when REST rate limits are in shadow mode. Request bodies are limited to 32 KiB. Unknown arguments, out-of-range coordinates, oversized radii, unsupported protocol versions, and untrusted browser origins are rejected. Feeder identity, receiver identity, RF details, and credentials are never returned.
Registry metadata and compatibility
Download server.json, validated against the official 2025-12-11 MCP Registry schema. Compatible clients must support Streamable HTTP; bearer headers are optional for higher-limit access.
Troubleshooting
401: a supplied API credential is invalid or inactive; omit the header for public access.406: include both required response types inAccept.-32602: inspect tool arguments and documented bounds.429/-32002: followRetry-Afterfor interval or daily-budget limits.503: quota storage is temporarily unavailable; tool calls fail closed, but anonymous initialization and discovery remain available.