Gaduin
v0.3.0Read-only flight, train, airport and chokepoint status plus prediction markets on transport delays.
Endpoint health
online- Last checked
- 11/20/2026, 4:17:21 AM
- Latency
- 269 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.gaduin%2Fgaduin
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.gaduin/gaduin": {
"url": "https://gaduin.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Aircraft position
get_aircraft_position
The latest position on record for the aircraft with this ICAO 24-bit address, however old: latitude, longitude, barometric altitude, ground speed, course, on-ground state and callsign (both null unless reported in the last 15 minutes), when it was reported and its age in seconds. live is true only when it is at most 180 seconds old, two of GADUIN's 90-second reading intervals; an older position is the latest on record, not where the aircraft is now. Not found when no position of the aircraft was recorded in the last 90 days. Positions are what the aircraft's own transponder broadcast, picked up by ground receivers and relayed to GADUIN with a delay, so reported_at_utc, not the time of the request, is when the aircraft was there; where no receiver hears the aircraft (over oceans and remote land) there is no position for that stretch.
Schema valid · SHA-256 4d0be935d225…
View input schema
{ "type": "object", "properties": { "icao24": { "type": "string", "description": "The aircraft's ICAO 24-bit address as six hex digits, e.g. 4ca7b2 (get_flight_status reports it under aircraft)." } }, "required": [ "icao24" ] }Aircraft recorded track
get_aircraft_track
Every position recorded for an aircraft from from to to, both inclusive, oldest first; nothing is cut. The window may span at most 6 hours and must start within the last 90 days; a longer or older window is refused, so read a longer stretch window by window. GADUIN reads every aircraft's position once every 90 seconds and keeps a point only when the reported position time moved, so points are typically 90 seconds apart, with gaps where no receiver heard the aircraft; aircraft of flights GADUIN follows are read every 5 seconds for about 40 minutes either side of their scheduled arrival, so their points are denser there. Nothing is thinned. Positions are what the aircraft's own transponder broadcast, picked up by ground receivers and relayed to GADUIN with a delay, so reported_at_utc, not the time of the request, is when the aircraft was there; where no receiver hears the aircraft (over oceans and remote land) there is no position for that stretch.
Connections
streamable-http
https://gaduin.com/mcp