Gaduin
REMOTE · GADUIN.COM
Read-only flight, train, airport and chokepoint status plus prediction markets on transport delays.
Available components
Last scanned (14 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7905 tokens (~282/item across 28 items; 28 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 28 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_chokepoint_status” rewrote its description, which is the text the model reads security
- Tool “get_flight_history” rewrote its description, which is the text the model reads security
- Tool “get_flight_status” rewrote its description, which is the text the model reads security
- Tool “get_market_price_history” rewrote its description, which is the text the model reads security
- Tool “get_station_board” rewrote its description, which is the text the model reads security
- Tool “list_disrupted_airports” rewrote its description, which is the text the model reads security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- Tool “search_flights” rewrote its description, which is the text the model reads security
- Schema quality: 213 → 282 ▼ functional
- Schema quality: good → excellent functional
- New tool “get_aircraft_position” functional
- New tool “get_aircraft_track” functional
- New tool “get_airport_arrivals” functional
- New tool “get_airport_departures” functional
- New tool “get_flight_position” functional
- New tool “get_flight_track” functional
- New tool “get_observed_flights” functional
- New tool “get_port_board” functional
- New tool “get_rail_punctuality” functional
- New tool “get_train_status” functional
- New tool “get_vessel_port_calls” functional
- New tool “list_aircraft_in_area” functional
- New tool “list_airport_movements” functional
- New tool “list_flight_disruptions” functional
- New tool “list_ports” functional
- New tool “search_stations” functional
- “get_chokepoint_status” added an optional parameter “days” cosmetic
- “get_flight_history” added an optional parameter “days” cosmetic
- “get_flight_status” added an optional parameter “date” cosmetic
- “get_station_board” added an optional parameter “date” cosmetic
- “get_station_board” added an optional parameter “window” cosmetic
- “search_flights” added an optional parameter “date” cosmetic
- “search_flights” added an optional parameter “scope” cosmetic
- “get_station_board” reworded the description of “limit” cosmetic
- “list_markets” reworded the description of “query” cosmetic
- 15 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_airline_stats” rewrote its description, which is the text the model reads security
- Tool “get_airport_status” rewrote its description, which is the text the model reads security
- Tool “get_chokepoint_status” rewrote its description, which is the text the model reads security
- Tool “get_flight_history” rewrote its description, which is the text the model reads security
- Tool “get_flight_status” rewrote its description, which is the text the model reads security
- Tool “get_station_board” rewrote its description, which is the text the model reads security
- Tool “list_chokepoints” rewrote its description, which is the text the model reads security
- Tool “list_disrupted_airports” rewrote its description, which is the text the model reads security
- Tool “search_flights” rewrote its description, which is the text the model reads security
- Schema quality: 132 → 213 ▼ functional
- Schema quality: excellent → good functional
- “get_flight_history” reworded the description of “number” cosmetic
- “get_flight_status” reworded the description of “number” cosmetic
- “list_markets” reworded the description of “query” cosmetic
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +2
- Tool “search_flights” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “check_airport” functional
- New prompt “check_chokepoint” functional
- New prompt “check_flight” functional
- New prompt “check_station” functional
- New prompt “disrupted_airports” functional
- New prompt “find_flights” functional
- Server version: 0.2.0 → 0.3.0 functional
- 12 Nov 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://gaduin.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gaduin.com | CN=YE1,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 685a34ae5d7632943434aab0fee86333967 |
| SANs: *.gaduin.com, gaduin.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of gaduin.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| gaduin.com. | DS published | 2371 | 13 | Verified |
| gaduin.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gaduin.com/mcp | Verified | 200 | |
| http (plaintext) | http://gaduin.com/mcp | HTTPS enforced | 301 | https://gaduin.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_aircraft_position Aircraft position ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| icao24 | string | yes | The aircraft's ICAO 24-bit address as six hex digits, e.g. 4ca7b2 (get_flight_status reports it under aircraft). |
No output schema declared.
No examples provided.
get_aircraft_track Aircraft recorded track ~333
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start of the window: an ISO-8601 time with a UTC offset, e.g. 2026-11-13T12:00:00Z; within the last 90 days. |
| icao24 | string | yes | The aircraft's ICAO 24-bit address as six hex digits, e.g. 4ca7b2 (get_flight_status reports it under aircraft). |
| to | string | yes | End of the window, after from and at most 6 hours later, in the same form. |
No output schema declared.
No examples provided.
get_airline_stats Airline on-time record ~145
An airline's last 30 days of the flights on record that it operates itself (coverage on_record: the flights on record, not its full schedule): arrivals graded against a published schedule, on-time and late counts, the on-time share, median and 90th-percentile arrival delay (all three only from 20 graded arrivals), landings left ungraded, cancellations, diversions, routes flown, up to five most and least delayed flights, the late rule, and a link to its airline page on gaduin.com.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Airline IATA code (e.g. BA) or ICAO code (e.g. BAW). |
No output schema declared.
No examples provided.
get_airport_arrivals Airport arrivals board ~319
One page of an airport's arrivals on record for one airport-local day, landed and cancelled flights included (coverage on_record: the flights GADUIN has a record of, not the airport's full schedule). Each physical flight appears once with its codeshares, ordered by scheduled arrival (unknown schedules last), with origin, scheduled departure, scheduled, estimated and recorded arrival in UTC, status and a link to its flight page. The recorded arrival is a landing as the airport shows it, never an estimate. Each flight belongs to exactly one date: the airport-local date of its scheduled arrival, whenever it actually landed (with no scheduled arrival, the date of its recorded landing), so days add up without double counting. While next_cursor is not null, call again with the same airport and cursor set to it to read the rest of the day.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | Airport IATA code (e.g. LHR) or ICAO code (e.g. EGLL). An IATA code works for airports with a page on gaduin.com; otherwise give the ICAO code. |
| cursor | string | – | next_cursor from the previous answer, to read the next page; give the same airport (and date, if given) with it. Omit for the first page. |
| date | string | – | Airport-local date YYYY-MM-DD, within the last 400 days. Defaults to the airport's today. |
| limit | integer | – | Max flights per page (1-500). Defaults to 100. |
No output schema declared.
No examples provided.
get_airport_departures Airport departures board ~372
One page of an airport's departures on record for one airport-local day, departed and cancelled flights included (coverage on_record: the flights GADUIN has a record of, not the airport's full schedule). Each physical flight appears once with its codeshares, ordered by scheduled departure (unknown schedules last), with destination, scheduled, estimated and recorded departure in UTC, status, delay in minutes, verdict (delayed means more than late_threshold_minutes plus the airport's taxi_allowance_minutes) and a link to its flight page. Each flight belongs to exactly one date: the airport-local date of its scheduled departure, whenever it actually left (with no scheduled time, the date of its recorded departure), so days add up without double counting; for the airport's current day only, a flight that left before local midnight ahead of a schedule after it is listed once that day has ended. While next_cursor is not null, call again with the same airport and cursor set to it to read the rest of the day. total counts the day's flights at each read, so a flight added between pages can change it.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | Airport IATA code (e.g. LHR) or ICAO code (e.g. EGLL). An IATA code works for airports with a page on gaduin.com; otherwise give the ICAO code. |
| cursor | string | – | next_cursor from the previous answer, to read the next page; give the same airport (and date, if given) with it. Omit for the first page. |
| date | string | – | Airport-local date YYYY-MM-DD, within the last 400 days. Defaults to the airport's today. |
| limit | integer | – | Max flights per page (1-500). Defaults to 100. |
No output schema declared.
No examples provided.
get_airport_status Airport status today ~502
How an airport is running today (airport-local day), with a link to its page on gaduin.com. departures: today's flights on record scheduled in the local day, each counted once, with coverage on_record (the counts cover the flights on record for this airport today, not its full schedule); of those due (scheduled at or before now) each is exactly one of on_time, delayed, cancelled, not_reported (no recorded departure yet) or not_graded (a recorded departure with a null allowance or more than 60 minutes before its schedule); decided = on_time + delayed + cancelled; cancelled_later counts cancellations scheduled after now, and diverted the due flights shown diverted (also counted in their outcome). Delayed means departing more than delay_threshold_minutes plus taxi_allowance_minutes after the scheduled time; the allowance is the airport's usual taxi time where its departure times are take-off times, 0 for gate times, and null when its departures are not graded yet. The on-time, delayed, cancelled and disrupted (delayed + cancelled) shares are over decided; they and the typical delay of the delayed flights (their lower median) are null, and verdict is unknown, below min_decided (20) decided flights or when departures are not graded. arrivals: coverage is airport_list with share_basis scheduled_day (the airport's own arrivals list), else on_record; with share_basis scheduled_day, arrivals scheduled today, landed and cancelled, with cancelled_share = cancelled / scheduled, null below min_scheduled (20); with share_basis not_comparable (US airports), flights landed in the local day and flights scheduled in it and cancelled, two different days, so scheduled and cancelled_share are null and arrivals never rate the airport; arrival delays are not measured. A side GADUIN did not read today is null. status: severe when the departures disrupted share is at least 0.50, disrupted from 0.25, else normal; when departures are not rated, severe or disrupted when the arrivals cancelled…
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | Airport IATA code (e.g. LHR) or ICAO code (e.g. EGLL). |
No output schema declared.
No examples provided.
get_chokepoint_status Chokepoint ship traffic ~241
Ship traffic through one maritime chokepoint as of its latest published count: status, the mean of the last 7 calendar days to latest_date against normal and how many of those days are published, the newest daily count, how many final weeks it has been under 85% of normal, since when and against which normal, the last 8 weeks with their share of normal (figures only once a week is final), the last 14 published daily counts, the rule behind the status, and a link to its page on gaduin.com; with days, also every published daily count of that window (history). Counts are published in batches several days in arrears (weekly; Panama monthly): latest_date is the newest day counted, not today.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Also return history: every published daily count in this many calendar days ending on latest_date, with the weeks holding them (1-1130, the depth of the record kept). Omit for the reading alone. |
| slug | string | yes | Chokepoint slug from list_chokepoints, e.g. suez or panama. |
No output schema declared.
No examples provided.
get_flight_history Flight on-time history ~183
How often a flight has been late over the last 30 days, or the last days days (up to 400, the record's reach). Returns n (arrivals graded against a published arrival schedule) with its on-time and late counts, ungraded_arrivals (landings with no published schedule to grade), cancelled and diverted counts, operations (n + cancelled + diverted, the base for shares), unconfirmed legs left out, the window (shorter when the record limit cut it), the late rule with its minute threshold, and a link to the flight page on gaduin.com.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | History window in days (1-400); defaults to 30. window reports the span actually covered. |
| number | string | yes | Flight number: airline IATA or ICAO code plus number, e.g. AA1. |
No output schema declared.
No examples provided.
get_flight_position Flight position now ~247
Where a flight is now: finds the aircraft broadcasting the flight number's callsign (the operating airline's ICAO code followed by the number) and returns its latest reported position: latitude, longitude, barometric altitude, ground speed, course, whether it reported being on the ground, its callsign, its ICAO 24-bit address, when it was reported and its age in seconds. The aircraft is named only when exactly one aircraft's latest report (received in the last 15 minutes) carries the callsign; otherwise position is null with a reason (callsign_unknown, not_broadcasting or ambiguous_callsign), never a guess. live is false for a position more than 180 seconds old. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | Flight number: airline IATA or ICAO code plus number, e.g. AA1. |
No output schema declared.
No examples provided.
get_flight_status Flight status ~584
Current status of a flight by number (e.g. AA1 or AAL1). Returns the canonical flight number and the leg its gaduin.com flight page answers with (today's leg in its own time zone, else the active leg nearest now, else the latest one; with date, that service date's leg), with its role (current: left and not landed, inside its arrival horizon; next: not yet left; latest: landed, cancelled, no arrival recorded, unconfirmed or past due with nothing recorded), its status (arrival_not_recorded once it left and no arrival was recorded by its scheduled arrival plus 6 hours, else its recorded departure plus 24 hours; timing is then null), whether sources disagree on its outcome, its timing, delay in minutes and on-time or delayed verdict under the late rule, its departure and arrival times in UTC and airport-local time with the time zone, the leg's own last update time (null when none), the aircraft type, registration and ICAO 24-bit address recorded for the operating flight's own leg (each null when not on record; always null on a codeshare listing), a link to the flight page and, when one is open, a link to the prediction market that page links (this leg's until it leaves, else the next upcoming leg's, with that leg's service date). on_record is true. It also returns observed: the flights read off positions reported by aircraft transponders under the flight number's broadcast callsign (matched_by callsign, with the callsigns tried; an airline whose callsigns do not follow its flight numbers shows nothing there) whose takeoff, else landing, starts within the leg's service date in its own time zone; each takeoff and landing is a bracket, not a gate time, and never fills or grades any time, delay or verdict above. observed is null when that day has not begun, lies beyond the 89 days observed flights are kept or no airline is known for the number; null with observed_unavailable true when it could not be read. A flight with no operation on record (with date, none on that servi…
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Service date YYYY-MM-DD (the departure's local date) to answer for that day's operation instead of the headlined one; from 400 days back to 3 days ahead. For a flight not on record, the UTC date its… |
| number | string | yes | Flight number: airline IATA or ICAO code plus number, e.g. AA1. |
No output schema declared.
No examples provided.
get_flight_track Flight flown track ~253
For each operation of a flight number on one service date, every position recorded for the aircraft flying it from its departure until its arrival was recorded, oldest first, each with latitude, longitude, barometric altitude, course and whether it is contested (the aircraft was flying for another operation at the same time as far as GADUIN can tell). GADUIN follows the aircraft of some operations only: the others have track null and reason not_tracked. An operation not yet departed, or departed with no position recorded yet, has an empty points list. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Service date YYYY-MM-DD, as get_flight_status reports it. Operations from the last 30 days and the next 3 are on record. |
| number | string | yes | Flight number: airline IATA or ICAO code plus number, e.g. AA1. |
No output schema declared.
No examples provided.
get_market Get a market ~80
One market by id or slug: its question, the rule it settles on, route, outcomes with current prices, volume, close time, status and, once settled, the outcome it settled on, with a link to its page.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Market UUID, or the slug from a gaduin.com/markets/<slug> link. |
No output schema declared.
No examples provided.
get_market_price_history Market price history ~122
How a market's prices moved: up to 180 timestamped points, oldest first, each with one price per outcome (in outcome order, 0 to 1). Shows how the market's view of an outcome changed over its life, including for closed and settled markets. The history reads a market's most recent 2,000 trades: when it has more, truncated is true and the series starts at starts_at, not at the market's open.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Market UUID, as list_markets and get_market return it. |
No output schema declared.
No examples provided.
get_observed_flights Observed flights by callsign ~305
The flights of one UTC date read off positions reported by aircraft transponders under the flight number's broadcast callsign: the airline's ICAO designator and the number (matched_by callsign, with the callsigns tried). An airline whose callsigns do not follow its flight numbers returns nothing, and neither does a codeshare number. Each flight is one aircraft's observed takeoff and landing with the airport; each is a bracket (earliest_utc to latest_utc, at most 10 minutes apart), not a gate time, and a side not observed is null with reason not_observed. A flight belongs to the date its takeoff bracket starts in, or its landing's when no takeoff was observed. No schedule, delay or on-time verdict is given; get_flight_status has the recorded times. Airports where no position on the ground is received yield no takeoff or landing. A movement is provisional until the UTC hour of the position that completed it has ended and 20 more minutes have passed (at most 80 minutes): until then a late position can still narrow its bracket, settle or clear its callsign, or withdraw it. complete says whether every movement of the date has settled.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | UTC date YYYY-MM-DD within the last 89 days. Defaults to today in UTC. |
| number | string | yes | Flight number: airline IATA or ICAO code plus number, e.g. AA1. |
No output schema declared.
No examples provided.
get_port_board Port arrivals and departures ~309
One port-local day of a port's own movement list: every vessel arrival and departure as the port lists it, with vessel name, IMO, MMSI and call sign as listed, status, and expected and recorded times in UTC. An arrival is placed by its recorded arrival (else the arrival the list expects), a departure by its recorded departure. What a recorded arrival means differs by port: instant_kind says whether it is the port entry or the berthing. A vessel absent from the day is not listed by the port; read_that_day false means the list was not read that day at all, so an absence says nothing. total counts every movement of the day: while next_cursor is not null, call again with the same locode and cursor set to it. A movement the port revises between pages can move across a page boundary: re-read from the first page for one consistent snapshot. Ports come from list_ports.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous answer, to read the next page; give the same locode with it. Omit for the first page. |
| date | string | – | Port-local day YYYY-MM-DD. Defaults to today at the port, or to the cursor's day. |
| limit | integer | – | Max movements per page (1-200). Defaults to 100. |
| locode | string | yes | UN/LOCODE of the port from list_ports, e.g. SEGOT; a dock code answers for its port. |
No output schema declared.
No examples provided.
get_rail_punctuality Rail punctuality ~249
Arrival punctuality of one operator, station or route (origin and destination station codes, one row per operator running it, counting only arrivals at its final destination), summed over the calendar days ending at the newest settled service date: calls (arrival calls with a recorded outcome, arrived or cancelled), on_time (less than 5 minutes late), within_15 (less than 15 minutes late, on_time included) and cancelled. Covers Great Britain's national rail network only: any other network is not found. A day counts only once all its arrivals are settled, so to_date trails today; days_counted says how many dates of the window are in the sums. Give exactly one of operator, station or route.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Calendar days in the window (1-90), ending at the newest settled date. Defaults to 28. |
| network | string | – | Rail network country code; only GB is recorded. |
| operator | string | – | Operator code, e.g. GW. |
| route | string | – | Origin and destination station codes, e.g. PAD-BRI. |
| station | string | – | Three-letter station code, e.g. PAD. |
No output schema declared.
No examples provided.
get_station_board Train station board ~311
Departures and arrivals at a railway station found by name or station code: the trains still to come by default, or every train of a station-local day with window day (the default when date is given). For each train, the other end of its journey, scheduled and recorded times in UTC, expected times and platforms where the railway publishes them, status, delay, operator and, when one is open, a link to its market; whether the board is live (expected times) and how fresh its source is; the coming hour's departures and cancellations, with the late count only on a live, fresh board (null otherwise); and a link to the station page on gaduin.com. Finds stations with a page on gaduin.com first, then any other station a stored train calls at (search_stations lists them).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Station-local date YYYY-MM-DD. Defaults to today at the station. |
| limit | integer | – | Max trains per direction (1-30). Defaults to 10; with window day, omit it to list the whole day. |
| network | string | – | The railway's country code to narrow the match, e.g. GB, US or CH. |
| station | string | yes | Station name or code, e.g. London Paddington, PAD or Zürich HB. |
| window | string | – | upcoming (trains from now on) or day (every train of the date). Defaults to day when date is given, else upcoming. |
No output schema declared.
No examples provided.
get_train_status Train run by number ~298
Every run of a train number on one service date with every calling point: scheduled, expected and recorded arrival and departure in UTC, platform where stated, cancellations, per-stop delay, and the railway's stated reason for a delay or cancellation in its own words. Expected times appear only on networks whose operator publishes live expected times, and only while the run is not stale (updated in the last 15 minutes); elsewhere a run is the timetable plus recorded times and cancellations. A number can run more than once a day or under several operators: runs are never merged, each is listed, and number_identity says how far the number names one run on its network. total counts every matching run; returned holds the first 10 by scheduled departure: narrow with network, operator or origin when total is larger. Runs are kept for about 45 days; timetables are held up to about 36 hours ahead.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Service date YYYY-MM-DD: the date the run starts on in its railway's time zone. |
| network | string | – | The railway's country code, e.g. GB, US or CH. |
| number | string | yes | Train number as published, e.g. 1A23, 171 or RJX 860. |
| operator | string | – | Operator code, e.g. VT or SBB. |
| origin | string | – | Origin station: its public code or its whole name. |
No output schema declared.
No examples provided.
get_vessel_port_calls Vessel port calls ~257
One vessel's calls, by IMO number, as the movement lists of the ports GADUIN reads recorded them, newest first: port, vessel name, MMSI and call sign as listed, status, expected and recorded arrival (instant_kind says whether it is the port entry or the berthing) and recorded departure in UTC, each call as the port's newest word on it that still names this IMO. Only the ports list_ports lists appear, so a voyage elsewhere is absent; no vessel positions are given. total counts every call in the window: while next_cursor is not null, call again with the same imo and days and cursor set to it.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous answer, to read the next page; give the same imo and days with it. Omit for the first page. |
| days | integer | – | Look-back in days (1-365): calls with any instant in this many days before now or later. Defaults to 30. |
| imo | string | yes | Seven-digit IMO ship number with a valid check digit, e.g. 9212163. |
| limit | integer | – | Max calls per page (1-100). Defaults to 50. |
No output schema declared.
No examples provided.
list_aircraft_in_area Aircraft in an area ~342
Every aircraft whose latest reported position lies inside a box (edges included) and is at most 180 seconds old (live), each as get_aircraft_position reports it, nearest the box's centre first (ties by icao24, so a limit always keeps the same ones). An aircraft whose latest position is older, or lies outside the box, is not listed. total counts them all; truncated is true when the limit cut the farthest from the centre. Sides are at most 10 degrees of latitude and of longitude; latitudes beyond 85.05112878 degrees north or south are outside the area index, so a box may not reach past them and an aircraft there is never listed. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | yes | The box as minLon,minLat,maxLon,maxLat in decimal degrees, e.g. -0.6,51.3,0.3,51.7: longitudes from -180 to 180, latitudes from -85.05112878 to 85.05112878, minLat below maxLat, each side at most 10… |
| limit | integer | – | Max aircraft to return, nearest the centre first (1-500). Defaults to 100. |
No output schema declared.
No examples provided.
list_airport_movements Observed airport landings and takeoffs ~459
The landings (type arrivals) or takeoffs (type departures) of airline flights at an airport in one airport-local day, read off positions reported by aircraft transponders, not from any airline or airport record. A movement belongs to the day its bracket starts in. Each movement is a bracket, not an instant: it happened between earliest_utc and latest_utc, the last position certainly in the air (at least 300 m above the airport) and the first on the ground for a landing, the reverse for a takeoff, at most 10 minutes apart; each comes with its callsign, the aircraft's ICAO 24-bit address and, when observed, the same flight's other movement (paired). These are not gate times, and no schedule, delay or on-time verdict is given. Only aircraft broadcasting an airline callsign are listed. An airport where no position on the ground is received yields nothing, and at one within a few km of another airport, movements that cannot be told apart from the other airport's are not listed. A movement is provisional until the UTC hour of the position that completed it has ended and 20 more minutes have passed (at most 80 minutes): until then a late position can still narrow its bracket, settle or clear its callsign, or withdraw it. complete says whether every movement of the day has settled. Pages are ordered by earliest_utc, then icao24; total counts every movement of the day: while next_cursor is not null, call again with the same airport, type and date and cursor set to it.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | Airport IATA code (e.g. LHR) or ICAO code (e.g. EGLL). |
| cursor | string | – | next_cursor from the previous answer, to read the next page; give the same airport, type and date with it. Omit for the first page. |
| date | string | – | Airport-local date YYYY-MM-DD within the last 89 days. Defaults to today at the airport. |
| limit | integer | – | Max movements per page (1-100). Defaults to 50. |
| type | string | yes | arrivals for landings, departures for takeoffs. |
No output schema declared.
No examples provided.
list_chokepoints Maritime chokepoints ~147
Every maritime chokepoint with a published daily ship count (Suez, Panama, Hormuz, Malacca and more), lowest share of normal first, then those unknown or not rated: slug, name, the unit counted, status (open, elevated, disrupted, closed, not_rated when too few ships a day to judge, or unknown), the mean of the last 7 calendar days to latest_date as a share of normal, normal and the newest day behind it, and a link to its page on gaduin.com. Counts are published in batches several days in arrears (weekly; Panama monthly): latest_date is the newest day counted, not today.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_disrupted_airports Most disrupted airports today ~144
Today's airports rated disrupted or severe that have a page on gaduin.com, in GADUIN's ranking: those rated on departures first by disrupted share of the departures on record, then those rated on arrival cancellations; each with the same reading as get_airport_status. total_disrupted counts every such airport; returned is how many of them, from the worst, this answer lists (at most limit). Departures are rated only from 20 decided flights, so an empty list means none is rated disrupted or severe, not that every airport runs normally.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max airports to return (1-50). Defaults to 10. |
No output schema declared.
No examples provided.
list_flight_disruptions Disrupted flights now ~235
Flights on record leaving, on its local today, an airport whose own departures board GADUIN reads, that are cancelled or late now (coverage on_record: not every flight). Late means departed, or published to depart, more than late_threshold_minutes plus the airport's taxi allowance after the schedule its board shows, and not yet landed; an airport with no measured allowance lists only cancellations. Each physical flight appears once under its operating flight number, with designators listing every number it is sold under, its airports, scheduled departure in UTC, status (cancelled or delayed), delay in minutes and a link to its flight page. Cancellations first, then the longest delay. total counts every such flight; the list holds at most the worst 1,000 (truncated says when total exceeds them) and returned is how many this answer holds (at most limit). partial means some covered airport could not be read, so its flights may be missing from the list and the total.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max flights to return, worst first (1-1000). Defaults to 100. |
No output schema declared.
No examples provided.
list_markets List prediction markets ~253
List prediction markets on real-world transport outcomes (flight delays, train punctuality, ship arrivals, weekly ship counts through maritime chokepoints, airport flight counts), filtered by status (OPEN by default; CLOSED, SETTLED or CANCELLED for past ones), category and a free-text query matched against the route, flight number, airline, airport codes and vehicle. Returns total (every market the filters match), returned (how many this page holds: the first limit of them, earliest close time first) and each returned market's id, link, category, question, route, outcomes with current prices, volume, close time and, once settled, the outcome it settled on.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter to one transport category. Omit to get all. |
| limit | integer | – | Max number of markets to return (1-100). Defaults to the server's page size. |
| query | string | – | Free text such as AA1, JFK, Paddington or Suez. Omit to match every market the other filters match. |
| status | string | – | Filter by market status: OPEN (trading), CLOSED (awaiting settlement), SETTLED or CANCELLED. Defaults to OPEN. |
No output schema declared.
No examples provided.
list_ports Ports with a movement list ~115
Every port whose own published list of vessel arrivals and departures GADUIN reads, by UN/LOCODE, with its name, country, coordinates, time zone, when its list was last read and found up to date, and whether that is current (within current_within_minutes). Only these ports have a board (get_port_board) or appear in vessel port calls (get_vessel_port_calls); a port missing here is one GADUIN does not read, not one without traffic. The list is never cut.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_flights Search flights by route ~498
Today's departures on record from an airport (airport-local day; date picks another local day), optionally only those to one destination (an airport code, or a city matched as whole words) or flown by one airline: finds flights without knowing their number. coverage is on_record: the counts cover the flights on record for this airport today, not its full schedule. Counts over the matching flights: departed_today (a departure is recorded and the flight is not cancelled), past_due_not_reported (not cancelled, no recorded departure, scheduled at or before now_utc), still_to_depart (not cancelled, no recorded departure, scheduled after now_utc) and cancelled_today. flights lists the still-to-depart ones, never a cancelled one (scope day lists every matching flight of the day instead, departed and cancelled ones included; total counts the flights the scope lists, returned how many this answer holds): number, operating flight for codeshares, destination, scheduled, estimated and actual departure in UTC, status, delay in minutes from the scheduled time, verdict (delayed means more than late_threshold_minutes plus the airport's taxi_allowance_minutes; a recorded departure is not_graded with a null allowance or more than 60 minutes before its schedule), a link to its flight page and, when one is open, to its market. Without an airline filter, codeshare listings of one flight count once. The result links the gaduin.com page of the route when the destination is one airport with flights on record today, else the departure airport's page.
| Name | Type | Req | Description |
|---|---|---|---|
| airline | string | – | Airline IATA or ICAO code (e.g. BA or BAW). |
| date | string | – | Departure airport-local date YYYY-MM-DD, within the last 400 days or ahead. Defaults to the airport's today. |
| from | string | yes | Departure airport. Airport IATA code (e.g. LHR) or ICAO code (e.g. EGLL). |
| limit | integer | – | Max flights to return (1-50). Defaults to 20. |
| scope | string | – | upcoming (default) lists the still-to-depart flights; day lists every matching flight scheduled to depart that local day (with no schedule, departed on it), departed and cancelled ones included. |
| to | string | – | Destination airport IATA or ICAO code, or city name (e.g. JFK, KJFK or New York). |
No output schema declared.
No examples provided.
search_stations Search railway stations ~226
Finds railway stations by name or public code among every station a stored train calls at, on every network GADUIN reads, whether or not it has a page on gaduin.com: name, public code (null where the railway has only an internal identifier: then pass the name with network to get_station_board), network, country, coordinates, time zone and how it matched. Matches rank by public code (or the railway's own station number), whole name, start of name, then any part of it; accents and case are ignored. total counts every match; returned is how many this answer holds, the first limit of them. coverage_days: the catalogue holds every station a train scheduled from that many days ago onward calls at.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max stations to return (1-50). Defaults to 20. |
| network | string | – | The railway's country code to narrow the match, e.g. GB, US or CH. |
| q | string | yes | Station name, part of it, or its code, e.g. Zurich. |
No output schema declared.
No examples provided.
How do I install the Gaduin MCP server?
Gaduin is a hosted endpoint at https://gaduin.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gaduin.com
claude mcp add --transport http com-gaduin-gaduin 'https://gaduin.com/mcp'
What is the Gaduin MCP server?
Gaduin is an MCP server listed in the public MCP registry as com.gaduin/gaduin. Read-only flight, train, airport and chokepoint status plus prediction markets on transport delays. This page covers its hosted endpoint (https://gaduin.com/mcp).
Is the Gaduin MCP server safe to use?
Gaduin scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Gaduin MCP server expose?
Gaduin exposes 28 tools: list_markets, get_market, get_market_price_history, get_flight_status, get_flight_history, and 23 more. Their descriptions and schemas cost roughly 7,770 tokens of context every time the server is loaded.
Does the Gaduin MCP server require authentication?
No. We connected to Gaduin without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Gaduin MCP server still maintained?
Gaduin is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Gaduin MCP server?
VerifyMCP ran 13 checks on Gaduin, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.