← Registry

eCommerce

wise-travel.com

An MCP server for WiseTravel that searches live international flight fares, resolves IATA airport codes, and generates booking and pre-filled payment links.

1 endpoint4 known toolsFirst detected September 29, 2026Last detected September 29, 2026

ENDPOINT 1

https://www.wise-travel.com/mcp

No auth detected

MCP server metadata

Name
wisetravel
Version
1.0.0
Capabilities
tools
Server instructions

WiseTravel searches live, bookable fares for scheduled international flights. Resolve place names to IATA codes with find_airports before calling search_flights — search_flights only accepts 3-letter codes. City codes (LON, NYC, TYO) cover every airport in that city. Prices are totals for the whole party, in USD, taxes included. Fares move during the day, so a quote is a snapshot: the booking link re-prices live when it opens. Booking and payment happen on wise-travel.com — this server cannot reserve, hold, pay for or cancel anything. Once a traveller has chosen a fare, prepare_booking turns it into a link that opens that itinerary already filled in at the review-and-pay step, leaving only payment. Every traveller field it takes is optional — send what has been provided; anything omitted is completed on that page. Each search result ends with a `search_ref` for exactly this purpose.

Known tools 4

search_flights

Search live, bookable fares for scheduled international flights on WiseTravel, for one route, date and traveller mix at a time.

Inferred read-only
find_airports

Look up the IATA codes WiseTravel searches accept, from a place name or a partial code — for example "tokyo", "heathrow" or "SF".

Inferred read-only
get_booking_link

Build the wise-travel.com link for a given route, date and traveller mix, without running a fare search.

Inferred read-only
prepare_booking

Take one itinerary from a search_flights result, attach the traveller details already gathered, and return a link that opens that exact itinerary on wise-travel.com at the review-and-pay step with everything filled in — so the traveller only has to check the details and pay.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.wisetravel]
url = "https://www.wise-travel.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "wisetravel": {
      "type": "http",
      "url": "https://www.wise-travel.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: wisetravel
Remote MCP URL: https://www.wise-travel.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "wisetravel": {
      "url": "https://www.wise-travel.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "wisetravel": {
      "type": "http",
      "url": "https://www.wise-travel.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "wisetravel",
  "transport": "streamable-http",
  "url": "https://www.wise-travel.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.