MCP server
Travel Risk API has a remote Model Context Protocol server, so AI assistants can use the same data as the API: country risk, government advisories, disaster and conflict alerts, airports, flights, airlines and in-flight Wi-Fi.
| Server URL | https://api.travelriskapi.com/mcp |
| Transport | Streamable HTTP |
| Sign-in | OAuth 2.1 with PKCE (recommended), or an API key in the X-API-Key header |
| Quota | Each tool call counts as one request on your plan |
Connect
Claude (claude.ai, Claude Desktop)
- Open Settings → Connectors → Add custom connector.
- Name it Travel Risk API and paste
https://api.travelriskapi.com/mcp. - Click Connect, sign in with your API key on travelriskapi.com and press Allow.
Claude Code
claude mcp add --transport http travel-risk https://api.travelriskapi.com/mcp
Run /mcp inside Claude Code and choose travel-risk to sign in.
Cursor
Add to ~/.cursor/mcp.json (or the project's .cursor/mcp.json), then click Connect in Settings → MCP:
{ "mcpServers": { "travel-risk": { "url": "https://api.travelriskapi.com/mcp" } } }
VS Code
Add to .vscode/mcp.json:
{ "servers": { "travel-risk": { "type": "http", "url": "https://api.travelriskapi.com/mcp" } } }
ChatGPT
In developer mode, create a connector with the server URL and choose OAuth.
Any client, with an API key
Clients that cannot do OAuth can send your key as a header:
{ "mcpServers": { "travel-risk": { "url": "https://api.travelriskapi.com/mcp",
"headers": { "X-API-Key": "trk_your_key" } } } }
No key yet? Get one free, no card needed.
Tools
| Tool | What it answers |
|---|---|
assess_trip |
A whole itinerary: risk, nearby alerts and flight status per segment, with flags |
country_risk |
Risk score 0–5 and advisory level 1–4 for a country, with the breakdown |
country_profile |
Country details, current advisory and active alerts |
travel_advisories |
Advisories from several governments, each normalised to levels 1–4 |
active_alerts |
Natural-disaster and severe-weather alerts, filterable by country and severity |
conflict_events |
Recent armed-conflict and political-violence events |
airport_conditions |
Delays, ground stops, security and immigration waits, weather and traffic |
airport_security_wait |
Security checkpoint waits by checkpoint |
border_wait |
Land border crossing waits |
airline_profile |
Airline identity, fleet, IOSA registration and safety facts |
aircraft |
Aircraft by registration, with in-flight Wi-Fi |
flight_status |
Live status, times and delays of a flight |
flight_wifi |
Expected Wi-Fi on a flight: Starlink, another system or none |
airline_wifi |
An airline's Wi-Fi by aircraft type |
ip_geolocation |
Approximate location of an IP address |
Countries use ISO 3166-1 alpha-3 codes (FRA), airports IATA or ICAO codes (JFK, KJFK), airlines IATA or ICAO codes (UA), flights IATA numbers (UA1). Every tool returns {"data": …, "fetched_at": …}.
Example prompts
- Is it safe to travel to Lima next week? Check advisories and active alerts for Peru.
- Which of these countries have a level 3 or 4 advisory: Mexico, Egypt, Thailand, Colombia?
- Does UA1 tomorrow have Starlink, and what are security waits at SFO right now?
Security and access
- Sign-in happens on travelriskapi.com. Your assistant never sees your API key: it receives a token that expires after one hour and is renewed automatically.
- A connected assistant can read data only. It cannot see or change billing.
- To disconnect, remove the connector in your assistant. Tokens stop working within an hour; renewal stops at once.
- Details: Privacy Policy and Terms.