Wego
REMOTE · MCP.WEGO.COM
Search live flight and hotel prices on Wego. Get schedules, public holidays and booking links.
Available components
Last scanned (14 hours ago)
Scores higher than 57% 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 Security80
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4404 tokens (~440/item across 10 items; 10 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 Management13
- Stability observed for 4 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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.
- 20 Nov 26 +1
- Tool “flights_search” rewrote its description, which is the text the model reads security
- Tool “hotels_search” rewrote its description, which is the text the model reads security
- Schema quality: 553 → 440 ▲ functional
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “flights_search” rewrote its description, which is the text the model reads security
- 18 Nov 26 0
- Tool “flights_search” rewrote its description, which is the text the model reads security
- Tool “hotels_search” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 71
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://mcp.wego.com/public-app/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.wego.com | CN=YR1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | RSA 2048 | SHA256-RSA | 5720f22244a58ad27a605cdf896a502cd5f |
| SANs: mcp.wego.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.wego.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| wego.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.wego.com/public-app/v1/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.wego.com/public-app/v1/mcp | HTTPS enforced | 308 | https://mcp.wego.com/public-app/v1/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 →
flights_one_way_price Flight One-Way Price ~294
Shows cheapest one-way flight prices across a date range. Returns daily prices with price band thresholds for comparison. Use with origin/destination IATA codes from places_find_location. Defaults to next 6 months if no dates provided.
| Name | Type | Req | Description |
|---|---|---|---|
| currencyCode | string | yes | The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in… |
| destination | string | yes | Arrival city IATA code (e.g., BKK, PAR, TYO) |
| directOnly | boolean | – | Show direct flights only |
| endDate | – | – | End date (YYYY-MM-DD). Defaults to 6 months from start. |
| locale | string | – | Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar'). |
| origin | string | yes | Departure city IATA code (e.g., LON, NYC, SIN) |
| startDate | string | – | Start date (YYYY-MM-DD). Defaults to today. |
No output schema declared.
No examples provided.
flights_schedule Flight Schedule ~314
Gets the current published timetable of nonstop flights between two cities: airlines, flight numbers, departure and arrival airports and times, duration, and operating periods (dates, weekdays and aircraft). Connecting flights are not listed: use flights_search for those and for fares on a date. Accepts city or airport IATA codes from places_find_location; an airport code gives its city's timetable. Results are paged: when metadata.hasMore is true, call again with page + 1. Optionally filter by airline code.
| Name | Type | Req | Description |
|---|---|---|---|
| airline | string | – | Optional: Filter by airline code (2-letter IATA code, e.g., 'EK', 'SQ') |
| from | string | yes | Departure city or airport code (IATA, e.g., 'SIN' or 'LHR'). An airport code gives its city's timetable. |
| locale | string | – | Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar'). |
| page | integer | – | Page of flights, 1-based (default 1). Rarely needed: most routes fit on one page. |
| pageSize | integer | – | Flights per page (default and max 200). Use it to narrow a long answer. |
| to | string | yes | Arrival city or airport code (IATA, e.g., 'BKK' or 'LHR'). An airport code gives its city's timetable. |
No output schema declared.
No examples provided.
flights_search Search Flights ~1,018
Searches for flights between airports or cities. Not for flight status, price tracking, visa information, bookings, or reservation management. Polling flow: 1. Call with newSearch. It returns a searchId at once (status "created", pollAgainInSeconds: 5). 2. Wait pollAgainInSeconds, then call with searchId. Status is "incomplete" (cheaper fares still arriving) or "complete". 3. While status is "incomplete", wait pollAgainInSeconds and call again. Stop at "complete". After 3 reads, use the results you have. A search is complete about 30 seconds after it is created. After that, every read returns "complete" at once. Refinement: call with the searchId and new filters or sorting. They replace the previous filters and sorting entirely, so send again the ones to keep. Defaults: one date means one-way, a return date means round-trip. Omit filters when the user states no preference. Use a time range for an exact time ("after 10pm"). Use time blocks for a broad one: midnight 0-6h, morning 6-12h, afternoon 12-18h, night 18-24h. Paging: every searchId read returns metadata {page, pageSize, resultCount, totalCandidates, hasMore}. totalCandidates counts matching trips on all pages, resultCount this page. While hasMore is true, call with the same searchId, filters and sorting and page + 1. Featured trips appear on page 1 only. Labels (best_value, cheapest, cheapest_direct) are judged over all matching trips, not the page. Each trip leg has dayOffset: calendar days between the leg's local departure date and local arrival date (0 same day, 1 next day, -1 across the date line). Filter options: a page 1 read with searchId returns filterOptions with the airlines, alliances, bookingSites and stopoverAirports of this search. Later pages do not. The lists are partial while status is "incomplete" and final at "complete". Each entry is { code, name, price }, where price is the cheapest per-person price before filters. Each code is a valid value for the filter of the same name. Use the…
| Name | Type | Req | Description |
|---|---|---|---|
| currencyCode | string | yes | The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in… |
| filters | object | – | Flight filters to apply. When used with searchId (refinement), filters completely replace the previous filters. To preserve existing filters like airlines or departure times, include them again along… |
| locale | string | – | Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar'). |
| newSearch | object | – | Parameters required to create a new flight search when searchId is not provided. Include route (from/to), travel dates (fromDate/toDate in YYYY-MM-DD), and passenger counts. Use this to start a new W… |
| page | integer | – | Page of trips a searchId read returns, 1-based (default 1, max 100). |
| pageSize | integer | – | Trips per page on a searchId read (default 20, max 50). Out-of-range or non-integer values are rejected, never clamped. |
| searchId | string | – | Reuse the searchId from a previous search when refining, filtering, sorting, or selecting. |
| siteCode | string | – | The user's OWN country as an ISO 3166-1 alpha-2 code (e.g. 'SG', 'SA', 'IN'), when the conversation shows where the user is. It picks the Wego site that booking links open and the market prices come… |
| sorting | string | – | Sort order for results. Pass a single string value. Options: score_desc (recommended, default), price_asc (cheapest), duration_asc (fastest), leg1_departure_time_asc/desc (outbound departure), leg2_d… |
No output schema declared.
No examples provided.
flights_search_anywhere Search Flights Anywhere ~333
Discovers cheapest flight destinations from an origin city when the user has no specific destination in mind. Use for open-ended queries like 'where should I go?', 'cheapest flights from Dubai', 'surprise me', or 'best deals from Singapore'. Returns up to 15 cheapest destinations with prices, airlines, and travel dates. Do NOT use when user has a specific destination — use flights_search instead. Use IATA city codes from places_find_location.
| Name | Type | Req | Description |
|---|---|---|---|
| currencyCode | string | yes | The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in… |
| departureDate | string | – | Departure date (YYYY-MM-DD). Optional; API picks best dates if omitted. |
| locale | string | – | Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar'). |
| origin | string | yes | Departure city IATA code (e.g., DXB, SIN, LON) |
| returnDate | – | – | Return date (YYYY-MM-DD). Optional; ignored for oneway trips. |
| tripType | string | – | Trip type: 'roundtrip' (default) or 'oneway' |
No output schema declared.
No examples provided.
holidays_lookup Lookup Holidays ~141
Looks up public holidays for a country within a date range. Used for travel planning to find local holidays at the destination.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | ISO 3166-1 alpha-2 country code (e.g., 'SG', 'JP', 'US', 'TH') |
| end_date | string | yes | End date for the holiday search range in YYYY-MM-DD format. The range covers at most 366 days. |
| locale | string | – | Locale for localized holiday names (e.g., 'en', 'ar'). Defaults to 'en'. |
| start_date | string | yes | Start date for the holiday search range in YYYY-MM-DD format |
No output schema declared.
No examples provided.
hotels_get_photos Get Hotel Photos ~218
Gets photos for one or more hotels (up to 8), up to 3 per category: rooms, bathrooms, dining, amenities such as the pool and gym, public spaces such as the lobby, exterior, views and nearby attractions. Hotels with no categories get up to 12 photos with no category. Use this tool for room photos too, because hotels_get_rooms gives only one image per room type. Use categoryFocus to show some categories first. missingHotelIds lists the hotels that could not be loaded.
| Name | Type | Req | Description |
|---|---|---|---|
| categoryFocus | array | – | Photo categories to show first (does not filter). Pool and gym photos are in Amenities, lobby photos are in Public Spaces. Categories: Rooms, Bathrooms, Dining, Amenities, Public Spaces, Exterior, Vi… |
| hotelIds | array | yes | Array of hotel IDs to fetch photos for (1-8 hotels) |
| locale | string | – | Locale for the hotel name (e.g., 'en', 'ar'). Category names and photo descriptions are always English. |
No output schema declared.
No examples provided.
hotels_get_rooms Get Hotel Rooms ~258
Gets room rates for a specific hotel. Returns room types with pricing from multiple providers. Each rate's perNight price covers all rooms in the search together, for one night. Requires hotelId and searchId from a prior hotels_search call. If status is "incomplete", more rates are still loading: wait pollAgainInSeconds and call once more with the same arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| currencyCode | string | yes | The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in… |
| hotelId | integer | yes | Hotel ID from a previous hotels_search result |
| locale | string | – | Locale for results (default: 'en') |
| page | integer | – | Page number (default: 1) |
| perPage | integer | – | Room types per page, 1-10 (default: 10) |
| searchId | string | yes | Search ID from a previous hotels_search result |
No output schema declared.
No examples provided.
hotels_search Search Hotels ~936
Searches for hotels by city, location or hotel ID. Not for restaurants, activities, car rentals or non-travel queries. Call places_find_location first: types=["city"] for a cityCode, types=["poi"] for coordinates, types=["hotel"] for a hotelId. Each price is per night for all rooms in the search together. With 2 rooms, one price covers both rooms. Polling flow: 1. Call without searchId. It returns a searchId at once (status "created", pollAgainInSeconds: 5). 2. Wait pollAgainInSeconds, then call with searchId. Status is "incomplete" (better rates still arriving) or "complete" (all providers answered). 3. While status is "incomplete", wait pollAgainInSeconds and call again. Stop at "complete". After 3 reads, use the results you have. Once complete, every read (new filters, sorting or page) returns "complete" at once. Use one search type per new search: - citySearch: a city. For "near the airport" sort by "distance_from_nearest_airport_asc". For "downtown" sort by "distance_from_center_asc". - geoSearch: a named airport, landmark or POI, sorted by "distance_asc". Radius 10km for a landmark, 20km for an airport, or the radius the user gives. - hotelSearch: one hotel by ID. Refinement: call with the searchId and new filters, sorting or pagination. Filters replace the previous filters entirely, so send again the ones to keep. Filter options: a page 1 read with searchId returns filterOptions with the amenities, roomAmenities, brands, chains and propertyTypes of this search. Later pages do not. The lists are partial while status is "incomplete" and final at "complete". Each entry is { name, count }, where count is the approximate number of hotels in the whole search with that value, before filters. Amenity counts can be low. Each name is a valid value for the filter of the same name. Use these names in filters instead of guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| checkIn | string | – | Check-in date in YYYY-MM-DD. |
| checkOut | string | – | Check-out date in YYYY-MM-DD. |
| citySearch | object | – | Hotels in a city (e.g., 'hotels in Dubai' = {cityCode: 'DXB'}). |
| currencyCode | string | yes | The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in… |
| filters | object | – | Filters to apply to search results. |
| geoSearch | object | – | Hotels near a location (e.g., 'near Eiffel Tower' = {latitude: 48.8584, longitude: 2.2945}). Use places_find_location for coordinates. |
| hotelSearch | object | – | Single hotel by ID (e.g., {hotelId: 12345}). |
| locale | string | – | Locale code (e.g., 'en', 'ar'). Default: 'en'. |
| pagination | object | – | Pagination settings |
| rooms | array | – | Room config (e.g., [{adultsCount: 2, childrenCount: 1, childrenAges: [8]}]). REQUIRED when childrenCount > 0: ask for ages before searching. |
| searchId | string | – | Reuse the searchId from a previous search when refining filters or sorting. |
| siteCode | string | – | The user's OWN country as an ISO 3166-1 alpha-2 code (e.g. 'SG', 'SA', 'IN'), when the conversation shows where the user is. It picks the Wego site that booking links open and the market prices come… |
| sorting | string | – | Sort order (e.g., 'cheapest first' = 'price_asc', 'closest to center' = 'distance_from_center_asc'). Default: relevance. |
No output schema declared.
No examples provided.
places_find_location Find Location ~631
Search for cities, airports, districts, states, hotels, or points of interest by name. Returns location codes, IDs, and coordinates. Supports pagination (default: 10 results per page). PLACE TYPES: Filter by specific types using the 'types' parameter: - city: Major cities (returns cityCode like "DXB", "PAR") - airport: Airports (returns IATA codes like "JFK", "LHR") - district: Neighborhoods within cities (returns districtId) - state: States, provinces, regions - hotel: Individual hotels (returns hotelId) - poi: Points of interest, landmarks (returns coordinates) If 'types' is omitted, returns all matching place types. POI SEARCH WITH LOCATION BIAS: POI search uses Google Places API. You can optionally provide locationBias (approximate coordinates) to improve result relevance when geographic context is known. When to provide locationBias: - User mentions a city: "Eiffel Tower in Paris" (provide Paris coordinates) - Previous conversation context provides location - You recognize the landmark location When NOT to provide locationBias: - No geographic context available - Uncertain about location - Global/ambiguous landmarks EXAMPLES: Find city: { query: "Dubai" } returns cityCode: "DXB" Find district: { query: "Downtown Dubai", types: ["district"] } returns districtId Find airports: { query: "New York", types: ["airport"] } returns JFK, LGA, EWR Find hotel: { query: "Burj Al Arab", types: ["hotel"] } returns hotelId Find POI with bias: { query: "Eiffel Tower", types: ["poi"], locationBias: { latitude: 48.85, longitude: 2.35 } } Find POI without bias: { query: "Marina Bay Sands", types: ["poi"] } Pagination: { query: "hotel", pageSize: 10, page: 2 } returns results 11-20 AMBIGUITY HANDLING: When multiple locations match, response includes hasAmbiguity: true and disambiguationHint. Ask user to specify which location. NOTES: - locationBias is optional (text search works without it) - Approximate coordinates are fine (city-level accuracy) - Location bias improves…
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Locale code for localized results (falls back to user's locale from platform metadata) |
| locationBias | object | – | Optional coordinates to bias POI search results. Useful when searching for landmarks in a specific region. The LLM can provide approximate city/region coordinates based on context. |
| page | integer | – | Page number for pagination (default: 1) |
| pageSize | integer | – | Number of results per page (default: 10, max: 50) |
| query | string | yes | Search query for the location |
| types | array | – | Array of place types to filter results. If omitted, returns all types. |
No output schema declared.
No examples provided.
places_get_nearest_airport Get Nearest Airport ~76
Finds the nearest airport to given coordinates. Returns airport IATA code, name, and distance. Useful for determining departure airport when only coordinates are known.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude coordinate |
| locale | string | – | Locale for localized names (defaults to 'en') |
| longitude | number | yes | Longitude coordinate |
No output schema declared.
No examples provided.
How do I install the Wego MCP server?
Wego is a hosted endpoint at https://mcp.wego.com/public-app/v1/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 · mcp.wego.com
claude mcp add --transport http com-wego-mcp-mcp 'https://mcp.wego.com/public-app/v1/mcp'
What is the Wego MCP server?
Wego is an MCP server listed in the public MCP registry as com.wego.mcp/mcp. Search live flight and hotel prices on Wego. Get schedules, public holidays and booking links. This page covers its hosted endpoint (https://mcp.wego.com/public-app/v1/mcp).
Is the Wego MCP server safe to use?
Wego scores 72 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 Wego MCP server expose?
Wego exposes 10 tools: flights_one_way_price, flights_schedule, flights_search, flights_search_anywhere, places_get_nearest_airport, and 5 more. Their descriptions and schemas cost roughly 4,219 tokens of context every time the server is loaded.
Does the Wego MCP server require authentication?
No. We connected to Wego without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wego MCP server still maintained?
Wego 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 Wego MCP server?
VerifyMCP ran 13 checks on Wego, 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.