Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sorted Travel

REMOTE · SORTED.TRAVEL

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

Available components

−4 this week 74 Trust /100

Last scanned (15 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Recent critical change

Authorization (16 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security66
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 12 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

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 →

Changelog

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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 16 Nov 26 −7
    • Authorization: partial → fail ▼ critical
    • 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 security
  • 15 Nov 26 +1
    • 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 security
  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 9 Nov 26 +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.

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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://sorted.travel/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=sorted.travel CN=WE1,O=Google Trust Services,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA256 47b11e6cbd67cc5413d17dc2c4d247eb
SANs: sorted.travel, *.sorted.travel
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of sorted.travel. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
travel. DS published 589 8 Verified
sorted.travel. DS published 2371 13 Verified
sorted.travel. Verified address RRset verified with the apex keys
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=31536000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sorted.travel/mcp Verified 200
http (plaintext) http://sorted.travel/mcp HTTPS enforced 301 https://sorted.travel/mcp
MCP tools · 10 exposed · ~2,659 tokens

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 →

Tool Tokens
check_visa_requirements ~168

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).

NameTypeReqDescription
destination_countrystringyesVisa-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_countrystringyesVisa-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.

Structured output declared, but exposes no named fields.

No examples provided.

get_destination_info ~225

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.

NameTypeReqDescription
destination_handlestringyesSorted sitemap handle such as paris, hanoi, or tokyo.

Structured output declared, but exposes no named fields.

No examples provided.

get_destination_weather ~252

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.

NameTypeReqDescription
destination_handlestringyesSorted sitemap handle such as paris, hanoi, or tokyo.

Structured output declared, but exposes no named fields.

No examples provided.

get_profile_preferences ~112

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.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_recommended_destinations ~1,113

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.

NameTypeReqDescription
currencystring–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_flightsboolean–Set true only if the traveler asked for direct flights. Omit otherwise.
is_flight_time_filter_enabledboolean–Set true only when the traveler specified a max flight time. Omit otherwise.
is_one_layoverboolean–Set true only if the traveler asked to limit to at most one layover. Omit otherwise.
is_price_filter_enabledboolean–Set true only when the traveler specified a budget (with max_price). Omit otherwise.
is_safeboolean–Set true only if the traveler asked for safe destinations. Omit otherwise.
is_single_airlineboolean–Set true only if the traveler asked for a single airline or single ticket. Omit otherwise.
is_visa_freeboolean–Set true only if the traveler asked for visa-free or eVisa destinations. Omit otherwise.
is_weather_filter_enabledboolean–Set true only when the traveler asked for weather or temperature constraints. Omit otherwise.
is_weather_mixedboolean–Set only when the traveler asked about mixed or partly cloudy weather. Omit otherwise.
is_weather_rainboolean–Set true only when the traveler asked for rainy weather. Omit otherwise.
is_weather_sunboolean–Set only when the traveler asked about sunny weather. Omit otherwise.
max_flight_timeinteger–Max flight time in hours. Omit unless the traveler specified a flight time limit.
max_priceinteger–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_sizeinteger–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_codestring–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_maxinteger–Max temperature in Celsius. Omit unless the traveler specified a temperature range.
temperature_mininteger–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).

Structured output declared, but exposes no named fields.

No examples provided.

render_destination_info ~81

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.

NameTypeReqDescription
destinationobjectyesFull structuredContent from get_destination_info. Pass it through unchanged.
NameTypeReqDescription
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.
statusstringyesResult 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.

No examples provided.

render_destination_weather ~81

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.

NameTypeReqDescription
destinationobjectyesFull structuredContent from get_destination_weather. Pass it through unchanged.
NameTypeReqDescription
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.
statusstringyesResult status. Usually OK.
ui_view––Widget view. weather for forecast and climate.
weather_attribution––Attribution text for the forecast provider.

No examples provided.

render_recommended_destinations ~233

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.

NameTypeReqDescription
currencystring–Currency code from the recommendation result.
destinationsarrayyesDestination 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_codestring–Departure IATA from the recommendation result `from` field.
statusstring–Result status. Usually OK.
total_cnt––Total match count from the recommendation result.
NameTypeReqDescription
currencystring–Currency code for prices.
destinationsarrayyesDestination cards shown in the carousel.
discover_url––Discover page URL for the same search.
fromstring–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.
statusstringyesResult status. Usually OK.
total_cnt––Total match count from the recommendation result.

No examples provided.

resolve_destination ~198

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.

NameTypeReqDescription
page_sizeinteger–Maximum number of destination matches to return (1-7). Omit unless the traveler asked for a specific count.
querystringyesCity, country, region, or IATA airport code to resolve onto Sorted destinations.

Structured output declared, but exposes no named fields.

No examples provided.

update_profile_preferences ~196

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.

NameTypeReqDescription
field_namestringyesPreference field to change. Only traveler profile fields are allowed.
field_valuestringyesValue to set, add, or remove. For list fields this is one item, such as a destination handle or IATA code.
operationstringyesUPDATE replaces the field. ADD and REMOVE change lists.

Structured output declared, but exposes no named fields.

No examples provided.

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.

remote · sorted.travel

# add to Claude Code
claude mcp add --transport http travel-sorted-sorted-travel 'https://sorted.travel/mcp'
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.