# Sorted Travel (remote · sorted.travel)

Travel ranking, place facts, weather, visa, and profile tools for Sorted Travel.

- Trust score: 74/100 (medium)
- Change this week: −4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Recent critical change**: Authorization (2026-11-16). See the changelog below before you install this server.

## Components

- remote · `sorted.travel`: 74/100 (this document), [markdown](https://verifymcp.io/servers/travel-sorted-sorted-travel/sorted.md), [page](https://verifymcp.io/servers/travel-sorted-sorted-travel/sorted)

## Channel facts

- Endpoint: `https://sorted.travel/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_profile_preferences).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3301 tokens (~275/item across 12 items; 10 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Sorted Travel MCP server?

Sorted Travel is a hosted endpoint at https://sorted.travel/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.

### Claude

```bash
claude mcp add --transport http travel-sorted-sorted-travel 'https://sorted.travel/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "travel-sorted-sorted-travel": {
      "url": "https://sorted.travel/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "travel-sorted-sorted-travel": {
      "type": "http",
      "url": "https://sorted.travel/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.travel-sorted-sorted-travel]
url = "https://sorted.travel/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "travel-sorted-sorted-travel": {
      "type": "remote",
      "url": "https://sorted.travel/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add travel-sorted-sorted-travel --url 'https://sorted.travel/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  travel-sorted-sorted-travel:
    url: "https://sorted.travel/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "travel-sorted-sorted-travel": {
      "Transport": "http",
      "Url": "https://sorted.travel/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add travel-sorted-sorted-travel -t streamable-http -u 'https://sorted.travel/mcp'
```

### Other

```json
{
  "mcpServers": {
    "travel-sorted-sorted-travel": {
      "type": "http",
      "url": "https://sorted.travel/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 72, −7)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_destination_info” rewrote its description, which is the text the model reads
- [security] Tool “get_destination_weather” rewrote its description, which is the text the model reads
- [security] Tool “get_recommended_destinations” rewrote its description, which is the text the model reads
- [security] Tool “render_destination_info” rewrote its description, which is the text the model reads
- [security] Tool “render_destination_weather” rewrote its description, which is the text the model reads
- [security] Tool “render_recommended_destinations” rewrote its description, which is the text the model reads
- [security] Tool “update_profile_preferences” is now declared destructive

### 2026-11-15 (score 79, +1)

- [security] Tool “get_destination_info” rewrote its description, which is the text the model reads
- [security] Tool “get_profile_preferences” rewrote its description, which is the text the model reads

### 2026-11-13 (score 78, +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.

### 2026-11-11 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 76, +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.

### 2026-11-08 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (10)

### `resolve_destination` (~198 tokens)

Resolve a city, country, region, or airport onto Sorted destinations.

Use this when the traveler names a place and you do not already have a
sitemap handle (paris, hanoi) or IATA code. Returns handle, name,
country, airport_code, and place_url for a few live matches. After
resolve: for generic info / what a place is like, call
get_destination_info (not weather). Call get_destination_weather only
when they asked for weather, forecast, climate, or when to visit. For
where-to-go ranking, call get_recommended_destinations with
airport_code. One place per call. Do not invent a handle.

Input parameters:

- `page_size` (integer): Maximum number of destination matches to return (1-7). Omit unless the traveler asked for a specific count.
- `query` (string, required): City, country, region, or IATA airport code to resolve onto Sorted destinations.

### `get_recommended_destinations` (~1113 tokens)

Recommend destinations from a departure airport.

Use this whenever the traveler asks where to go. Only set filter
arguments they explicitly asked for (month, airport, budget, weather,
visa, tags). Omit all other filters so Sorted keeps its defaults. Never
set a filter to false just because they did not mention it. When they
name a continent or region, always set destination_tags (Africa →
africa, Asia → asia, Europe → europe, Americas → americas, Middle East
→ middle-east, Caribbean → caribbean, Australia/Oceania →
australia-oceania). Do not enable direct flights unless they asked.
Passport names must match the visa table (USA, United Kingdom); aliases
such as United States are accepted and normalized. source_location_code
must be a supported origin, a city alias (PAR, LON, NYC), or ANYWHERE.
ANYWHERE is fine for weather, region, or vibe asks that are not flight-
or price-sensitive; it skips flight prices and direct-route filters. Use
a supported airport (not ANYWHERE) for direct, cheap/budget, flight
time, or layover asks. Do not use a destination airport_code from
resolve_destination unless it is in the supported list. Never invent a
destination list. Do not use this for live flight tickets. Returns JSON
only (no UI). Paired render tool: render_recommended_destinations —
pass this tool's destinations and related fields there; hosts show the
carousel only from that render step, not from this data result alone.

Input parameters:

- `currency` (string): Upper-case currency code for prices. Omit unless the traveler specified a currency.
- `destination_tags`: Destination interest handles the traveler asked for. Required for continents/regions: africa, asia, europe, americas, middle-east, caribbean, australia-oceania. Also features such as beach, hiking, r…
- `is_direct_flights` (boolean): Set true only if the traveler asked for direct flights. Omit otherwise.
- `is_flight_time_filter_enabled` (boolean): Set true only when the traveler specified a max flight time. Omit otherwise.
- `is_one_layover` (boolean): Set true only if the traveler asked to limit to at most one layover. Omit otherwise.
- `is_price_filter_enabled` (boolean): Set true only when the traveler specified a budget (with max_price). Omit otherwise.
- `is_safe` (boolean): Set true only if the traveler asked for safe destinations. Omit otherwise.
- `is_single_airline` (boolean): Set true only if the traveler asked for a single airline or single ticket. Omit otherwise.
- `is_visa_free` (boolean): Set true only if the traveler asked for visa-free or eVisa destinations. Omit otherwise.
- `is_weather_filter_enabled` (boolean): Set true only when the traveler asked for weather or temperature constraints. Omit otherwise.
- `is_weather_mixed` (boolean): Set only when the traveler asked about mixed or partly cloudy weather. Omit otherwise.
- `is_weather_rain` (boolean): Set true only when the traveler asked for rainy weather. Omit otherwise.
- `is_weather_sun` (boolean): Set only when the traveler asked about sunny weather. Omit otherwise.
- `max_flight_time` (integer): Max flight time in hours. Omit unless the traveler specified a flight time limit.
- `max_price` (integer): Max price the traveler is willing to pay. Omit unless they specified a budget.
- `months`: Month when the traveler will travel. Omit unless specified.
- `page_size` (integer): Number of results to return. Omit unless the traveler asked for a specific count.
- `passports`: Passport countries for visa filtering. Use visa-table names such as USA and United Kingdom.
- `selected_airlines`: Airline codes to filter by. Omit unless the traveler named airlines.
- `sort_by`: Result order. Omit unless the traveler asked to sort a specific way.
- `source_location_code` (string): Departure IATA from Sorted's supported origins only: AMS, BCN, BER, BOS, CDG, DUB, FRA, JFK, LHR, SFO, SYD, YYZ. City codes and aliases PAR→CDG, LON→LHR, NYC→JFK (and sibling airports such as ORY, LG…
- `temperature_max` (integer): Max temperature in Celsius. Omit unless the traveler specified a temperature range.
- `temperature_min` (integer): Min temperature in Celsius. Omit unless the traveler specified a temperature range.
- `user_tags`: Interest handles from saved traveler preferences, not explicit requests.
- `user_visas`: Visas the traveler said they hold. Use exact uppercase values (UK, SCHENGEN, NEW_ZEALAND).

### `render_recommended_destinations` (~233 tokens)

Render the destination recommendations carousel.

Paired data tool: get_recommended_destinations. Input is that tool's
destinations list (full list for a new search, or a filtered subset for
follow-ups such as cheapest or visa-free) plus related fields from the
same result. Hosts show the carousel from this render tool; the data
tool alone does not. Do not invent destination cards.

Input parameters:

- `currency` (string): Currency code from the recommendation result.
- `destinations` (array, required): Destination cards from get_recommended_destinations. Pass the full list, or a filtered subset for follow-ups such as cheapest or visa-free.
- `discover_url`: Discover URL from the recommendation result.
- `message`: Optional status message for empty or error states.
- `months`: Months from the recommendation result.
- `selected_month_indexes`: Selected month indexes from the recommendation result.
- `source_location_code` (string): Departure IATA from the recommendation result `from` field.
- `status` (string): Result status. Usually OK.
- `total_cnt`: Total match count from the recommendation result.

Output parameters:

- `currency` (string): Currency code for prices.
- `destinations` (array): Destination cards shown in the carousel.
- `discover_url`: Discover page URL for the same search.
- `from` (string): Departure IATA airport code.
- `message`: Optional status message for empty or error states.
- `months`: Travel months from the recommendation result.
- `selected_month_indexes`: Selected month indexes from the recommendation result.
- `status` (string): Result status. Usually OK.
- `total_cnt`: Total match count from the recommendation result.

### `get_destination_info` (~225 tokens)

Get on-the-ground facts for one destination handle.

Default tool for generic destination info ("info on Dubai", "tell me
about Lisbon", "what is Tokyo like"). Returns brief, safety, currency,
phone code, eSIM notes, and taxi apps. Use a sitemap handle such as
hanoi, paris, or tokyo. If you only have a city, country, or airport
name, call resolve_destination first. Do not use get_destination_weather
for those generic info asks. Use get_destination_weather only when the
traveler explicitly asks for current weather, a 7-day forecast, monthly
climate, or when to visit. Send the traveler to place_url
for the full page. Do not use this for bookings. Returns JSON only
(no UI). Paired render tool: render_destination_info — pass this tool's
structuredContent there; hosts show the place card only from that
render step, not from this data result alone.

Input parameters:

- `destination_handle` (string, required): Sorted sitemap handle such as paris, hanoi, or tokyo.

### `render_destination_info` (~81 tokens)

Render the destination facts card.

Paired data tool: get_destination_info. Input is that tool's
structuredContent, passed through unchanged. Hosts show the place card
from this render tool; the data tool alone does not. Do not invent
destination facts.

Input parameters:

- `destination` (object, required): Full structuredContent from get_destination_info. Pass it through unchanged.

Output parameters:

- `best_time_summary`: Short best-time-to-visit overview shown on the place card.
- `brief`: On-the-ground destination brief from get_destination_info. Usually an object with brief_text and update_date; a plain string is also accepted.
- `country`: Country name.
- `handle`: Sorted sitemap handle such as paris or tokyo.
- `image_url`: Destination photo URL for the place card hero image.
- `message`: Optional status message for empty or error states.
- `name`: Destination display name.
- `place_url`: Full destination page URL on sorted.travel.
- `status` (string): Result status. Usually OK.
- `sunrise`: Today's local sunrise as HH:MM.
- `sunset`: Today's local sunset as HH:MM.
- `ui_view`: Widget view. place for destination facts.

### `get_destination_weather` (~252 tokens)

Get current weather, forecast, climate, and when-to-visit notes for one place.

Use when the traveler explicitly asks for current weather, a 7-day
forecast, monthly climate averages, or when to visit a named destination.
Do not use this for generic destination info ("info on Dubai", "tell me
about Lisbon", "what is Tokyo like") — use get_destination_info instead.
This tool already includes seasonal when-to-visit months; do not look for
a separate when-to-visit tool. Use a sitemap handle such as hanoi, paris,
or tokyo. If you only have a city, country, or airport name, call
resolve_destination first. The 7-day forecast is from Foreca; credit
Foreca if you paraphrase it. Send the traveler to place_url for the full
page. Do not use this for bookings. Returns JSON only (no UI). Paired
render tool: render_destination_weather — pass this tool's
structuredContent there; hosts show the weather card only from that
render step, not from this data result alone.

Input parameters:

- `destination_handle` (string, required): Sorted sitemap handle such as paris, hanoi, or tokyo.

### `render_destination_weather` (~81 tokens)

Render the destination weather card.

Paired data tool: get_destination_weather. Input is that tool's
structuredContent, passed through unchanged. Hosts show the weather
card from this render tool; the data tool alone does not. Do not invent
weather data.

Input parameters:

- `destination` (object, required): Full structuredContent from get_destination_weather. Pass it through unchanged.

Output parameters:

- `handle`: Sorted sitemap handle such as paris or tokyo.
- `image_url`: Destination photo URL for the weather card hero image.
- `message`: Optional status message for empty or error states.
- `name`: Destination display name.
- `place_url`: Full destination page URL on sorted.travel.
- `source`: Weather data source. Usually Foreca.
- `status` (string): Result status. Usually OK.
- `ui_view`: Widget view. weather for forecast and climate.
- `weather_attribution`: Attribution text for the forecast provider.

### `check_visa_requirements` (~168 tokens)

Check visa hassle for a passport country and destination country.

Use visa-table country names (Ireland, not Irish; USA, not United
States). Common aliases are accepted and normalized. This is planning
context, not official immigration advice. Cite only place_url or
source_url from this result (sorted.travel only — never invent domains).

Input parameters:

- `destination_country` (string, required): Visa-table destination country name. Use USA, not United States.
- `destination_handle`: Optional Sorted destination handle to attach a place_url link in the response.
- `passport_country` (string, required): Visa-table passport country name. Use USA, not United States.
- `user_visas`: Visas the traveler holds. Use exact uppercase codes such as UK, SCHENGEN, or NEW_ZEALAND.

### `get_profile_preferences` (~112 tokens)

Read the signed-in traveler's saved profile preferences.

Requires an OAuth 2.0 access token with the profile.read scope. Returns
passports, home airport, currency, units, destination and activity
interests, preferred airlines, and bookmark or ignore lists. Does not
return chat history or account-deletion controls.

Intentionally omitted from OpenAI/ChatGPT tools/list while
should_list_profile_preference_tools is false. Ora and other hosts still
see the tool; implementation and OAuth gating stay.

### `update_profile_preferences` (~196 tokens)

Update one saved traveler profile preference for the signed-in user.

Requires an OAuth 2.0 access token with the profile.write scope. Allowed
fields: currency, units, sourceAirportCode, passports, visas,
passportHolder, airlines, destinationInterests, activityInterests,
lists.bookmarked, and lists.ignored. This cannot delete the account,
unlink messengers, or change email.

Intentionally omitted from OpenAI/ChatGPT tools/list while
should_list_profile_preference_tools is false. Ora and other hosts still
see the tool; implementation and OAuth gating stay.

Input parameters:

- `field_name` (string, required): Preference field to change. Only traveler profile fields are allowed.
- `field_value` (string, required): Value to set, add, or remove. For list fields this is one item, such as a destination handle or IATA code.
- `operation` (string, required): UPDATE replaces the field. ADD and REMOVE change lists.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/travel-sorted-sorted-travel/sorted#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 79
- 2026-11-14: 78
- 2026-11-13: 78
- 2026-11-12: 77
- 2026-11-11: 77
- 2026-11-10: 76
- 2026-11-09: 76
- 2026-11-08: 75
- 2026-11-07: 75

## Common questions

### What is the Sorted Travel MCP server?

Sorted Travel is an MCP server listed in the public MCP registry as travel.sorted/sorted-travel. Travel ranking, place facts, weather, visa, and profile tools for Sorted Travel. This page covers its hosted endpoint (https://sorted.travel/mcp).

### Is the Sorted Travel MCP server safe to use?

Sorted Travel scores 74 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 Sorted Travel MCP server expose?

Sorted Travel exposes 10 tools: resolve_destination, get_recommended_destinations, render_recommended_destinations, get_destination_info, render_destination_info, and 5 more. Their descriptions and schemas cost roughly 2,659 tokens of context every time the server is loaded.

### Does the Sorted Travel MCP server require authentication?

No. We connected to Sorted Travel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sorted Travel MCP server still maintained?

Sorted Travel 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 Sorted Travel MCP server?

VerifyMCP ran 14 checks on Sorted Travel, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.

## Links

- Remote endpoint: https://sorted.travel/mcp
- Repository: https://github.com/a-l-e-x-k/sorted-travel-sdk
- Website: https://sorted.travel/developers
- Changelog RSS feed: https://verifymcp.io/servers/travel-sorted-sorted-travel/sorted.xml
- Changelog JSON feed: https://verifymcp.io/servers/travel-sorted-sorted-travel/sorted/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/travel-sorted-sorted-travel/sorted.json
- HTML version of this page: https://verifymcp.io/servers/travel-sorted-sorted-travel/sorted
