Border waits and airport delays are current conditions; visa wait times are an official estimate that carries its own last-updated date, which is why that field comes back with every result. Quote the date alongside the number when the answer feeds a plan. The lane detail on border crossings is the part travellers actually act on — SENTRI and NEXUS times differ enough from standard lanes to change a routing decision.
A hosted server over three US federal travel feeds: State Department visa appointment wait times at consular posts worldwide, CBP border wait times at land crossings, and FAA airport delays and ground stops.
- `travel_get_visa_wait_times` takes a `country`, `city` and `visaCategory`, and returns the estimated wait in calendar days plus the date it was last updated
- `travel_get_border_wait_times` takes a `border` ("Canadian" or "Mexican") and a `port`, and returns crossing type, lane type — standard, SENTRI, NEXUS or FAST — and the current delay in minutes
- `travel_get_airport_delays` takes an IATA `airport` code and returns delay type, reason, average duration and estimated end time
- Every parameter is optional, so a broad question — all posts in a country, all delayed airports — is a valid query
Nothing to install and no API key. Add it as a URL-type entry pointing at `https://immigration-travel-mcp.apify.actor/mcp`; it works with Claude Desktop, Cursor, Windsurf and any MCP-compatible client. Published as immigration-travel-mcp version 0.1.0. Calls are billed at $0.01 per tool call.