Trip720
REMOTE · TRIP720.TRAVEL
Plans a whole trip from a total budget, every price labelled live, estimate or official.
Available components
Last scanned (5 hours ago)
Scores higher than 45% of remote servers
Unreachable for 1 day in a row. Last reached 4 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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Nov 26 64
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 5 Nov 2026 · Probed https://trip720.travel/api/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trip720.travel. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| travel. | present | 60277 | 8 | Verified |
| trip720.travel. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trip720.travel/api/mcp | Unreachable | ||
| http (plaintext) | http://trip720.travel/api/mcp | HTTPS enforced |
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 →
best_time_to_visit Best time to visit a country, from Trip720 ~83
When to go to a country, month by month: the best months overall, each covered place's most pleasant months, and the busy holiday weeks to plan around. From climate data (NASA POWER) and Trip720's research. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | A country name or two-letter code, e.g. 'Japan' or 'JP'. |
No output schema declared.
No examples provided.
check_entry_requirements Visa and entry rules, from Trip720 ~93
Whether travellers need a visa or an electronic authorisation for a holiday, for each passport and each destination country: the rule's name, the minimum processing days and its source (official government pages where available). Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | yes | Two-letter destination countries, e.g. ['JP', 'VN']. |
| passports | array | yes | Two-letter passport countries, e.g. ['AU']. |
No output schema declared.
No examples provided.
destination_facts What a place really costs, from Trip720 ~179
Trip720's checked facts for one destination, for travellers from Australia or the UK: what a day costs a person for food and getting around (street food, balanced, mostly restaurants), local transport and taxi prices, tourist tax, the most pleasant months, the visa for that home country, the sights not to miss with tips, and the total of a sample priced trip. Each figure comes from Trip720's research with its sources, in AUD or GBP. Read only; no booking or search is made. Places not covered say so and list the covered places in that country.
| Name | Type | Req | Description |
|---|---|---|---|
| homeCountry | string | – | Where the traveller lives: AU (Australia) or GB (the UK). AU when not given. |
| place | string | yes | A town, island or country, e.g. 'Kyoto', 'Bali', 'Japan'. |
No output schema declared.
No examples provided.
get_day_plan Day-by-day plan of a Trip720 option ~72
The day-by-day plan of one option of a trip already planned on Trip720 (the recommended option unless optionId is given): times, places and prices for each day. Read only; times marked typical are not from a timetable.
| Name | Type | Req | Description |
|---|---|---|---|
| optionId | string | – | – |
| tripId | string | yes | – |
No output schema declared.
No examples provided.
get_trip Read a Trip720 trip ~57
Reads a trip already planned on Trip720, by its trip id: its status and, when ready, its options with every labelled price and booking link. Read only; trips are kept 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| tripId | string | yes | – |
No output schema declared.
No examples provided.
plan_trip Plan a whole trip with Trip720 ~353
For a request to plan a trip with a budget. Plans a whole trip, home to home, against the traveller's total budget: flights, stays, transfers, activities, visas and daily costs. Returns up to six options, each with a Safe Trip Total (the whole trip with a contingency), the route, and every price labelled live (checked with the provider), estimate (Trip720's own, protection margin included) or official (a government fee), with a link to the option on trip720.travel where it is booked. Side effect: the trip is saved on Trip720 (kept 30 days) so it can be opened and booked; nothing is booked or paid. Limits: at most 6 travellers, 60 nights and 5 named places; flight fares are estimates in this quick build. A trip still being built comes back with status 'building' and its trip id.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | object | yes | – |
| departDate | string | yes | Departure date, YYYY-MM-DD. |
| destination | – | yes | 'surprise' to let Trip720 choose, or up to 5 places. |
| dining | string | – | – |
| interests | array | – | Finer interests in words, e.g. 'street art', 'hiking'. |
| origin | object | yes | – |
| pace | string | – | PACKED: see as much as possible; RELAXED: take it slowly; SETTLED: one place. |
| returnDate | string | yes | Return date, YYYY-MM-DD, at most 60 nights later. |
| travellers | object | yes | At most 6 travellers in all. |
| tripFocus | array | – | Themes such as 'Culture & heritage', 'Food & wine'. |
No output schema declared.
No examples provided.
swap_trip_item Swap one item of a Trip720 trip ~122
Replaces one line of an option with one of the numbered choices from trip_alternatives, and re-prices the whole trip as the website does. Returns the updated option and its Safe Trip Total before and after. Side effect: the trip saved on Trip720 changes; the previous choice can be chosen again the same way. Nothing is booked or paid.
| Name | Type | Req | Description |
|---|---|---|---|
| choice | integer | yes | The number of the choice from trip_alternatives. |
| lineId | string | yes | – |
| optionId | string | yes | – |
| tripId | string | yes | – |
No output schema declared.
No examples provided.
trip_alternatives Other choices for one item of a Trip720 trip ~124
For one line of an option in a trip already planned on Trip720 (a stay, a flight, a transfer, an activity), the other choices the providers offer, numbered, each with its price and what it does to the whole trip's Safe Trip Total and budget. Line ids and option ids come from plan_trip or get_trip. Read only; searches the providers again.
| Name | Type | Req | Description |
|---|---|---|---|
| lineId | string | yes | The line's id, e.g. 'N-STAY-1'. |
| optionId | string | yes | – |
| tripId | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Trip720 MCP server?
Trip720 is a hosted endpoint at https://trip720.travel/api/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 · trip720.travel
claude mcp add --transport http travel-trip720-trip720 'https://trip720.travel/api/mcp'
What is the Trip720 MCP server?
Trip720 is an MCP server listed in the public MCP registry as travel.trip720/trip720. Plans a whole trip from a total budget, every price labelled live, estimate or official. This page covers its hosted endpoint (https://trip720.travel/api/mcp).
Is the Trip720 MCP server safe to use?
Trip720 scores 64 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 Trip720 MCP server expose?
Trip720 exposes 8 tools: plan_trip, get_trip, get_day_plan, trip_alternatives, swap_trip_item, and 3 more. Their descriptions and schemas cost roughly 1,083 tokens of context every time the server is loaded.
Does the Trip720 MCP server require authentication?
Its publisher declares no required credentials for Trip720. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Trip720 MCP server still maintained?
Trip720 is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.