Tineo
REMOTE · API.TINEO.AI
Plan trips, search flights and hotels, and keep every booking in one shared itinerary.
Available components
Last scanned (14 hours ago)
Scores higher than 86% 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 Security100
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 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 20466 tokens (~157/item across 130 items; 110 tools + 20 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
- Structured output schemas are declared (21% of tools); any adoption earns full credit.Pass
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 10 of 11 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ground_transfer_booking_links" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 112 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
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 →
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
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.
- 18 Nov 26 +1
- Resource “Routes” now points somewhere else: ui://widget/route-options-2026-11-16.4.html → ui://widget/route-options-2026-11-17.1.html security
- Tool “cruise_get” rewrote its description, which is the text the model reads security
- New resource “Journal Entry” functional
- New tool “journal_entry_create” functional
- 17 Nov 26 0
- Resource “Import Preview” now points somewhere else: ui://widget/import-preview-2026-10-30.1.html → ui://widget/import-preview-2026-11-16.1.html security
- Resource “Routes” now points somewhere else: ui://widget/route-options-2026-10-28.1.html → ui://widget/route-options-2026-11-16.4.html security
- Resource “Segment Details” now points somewhere else: ui://widget/segment-detail-2026-10-30.1.html → ui://widget/segment-detail-2026-11-16.1.html security
- 16 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.
- 15 Nov 26 0
- Resource “Airbnb stays” now points somewhere else: ui://widget/airbnb-cards-2026-11-14.2.html → ui://widget/airbnb-cards-2026-11-15.1.html security
- Resource “Discover” now points somewhere else: ui://widget/discovery-cards-2026-11-06.1.html → ui://widget/discovery-cards-2026-11-15.1.html security
- Resource “Flights” now points somewhere else: ui://widget/flight-cards-2026-11-04.2.html → ui://widget/flight-cards-2026-11-15.1.html security
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 82
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://api.tineo.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tineo.ai | CN=WE1,O=Google Trust Services,C=US | 12 Nov 2026 | 10 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | ad0b8af66dbfe53e0eb632c5551092af |
| SANs: tineo.ai, *.tineo.ai | ||||||
| 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 api.tineo.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| tineo.ai. | DS published | 2371 | 13 | Verified |
| api.tineo.ai. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.tineo.ai/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.tineo.ai/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://challenges.cloudflare.com https://basemaps.cartocdn.com https://*.basemaps.cartocdn.com https://raw.githubusercontent.com; worker-src 'self' blob:; frame-src 'self' https://challenges.cloudflare.com; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://api.tineo.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.tineo.ai |
| Authorisation server | https://api.tineo.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.tineo.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.tineo.ai/mcp | HTTPS enforced | 301 | https://api.tineo.ai/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 →
known_participants Known Trip Participants ~49
Search people the authenticated user previously added to trips. Use before traveler_add, then obtain explicit invitation consent and confirm the email address.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Names to match against prior trip participants. |
No output schema declared.
No examples provided.
library_list_clear_completed Clear Completed Library List Items ~154
Permanently delete every completed item from an owned Library List. Tell the user how many items will be removed; call with confirmed=true only after they confirm. Use the listId and expectedVersion from the latest library_list_get. On library_version_mismatch, read the list again and reconsider the change; never retry blindly. Library Lists only, not trip checklists.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | True only after the user explicitly confirms this exact change. Without it the tool changes nothing and returns the change for review. |
| expectedVersion | string | yes | Opaque version from the latest library_list_get or Library List tool result. |
| listId | string | yes | Library List ID from library_lists_search or library_list_get. |
No output schema declared.
No examples provided.
library_list_delete Delete Library List ~151
Delete an entire owned Library List and all of its items. Name the list to the user first; call with confirmed=true only after they confirm. Use the listId and expectedVersion from the latest library_list_get. On library_version_mismatch, read the list again and reconsider the change; never retry blindly. Library Lists only, not trip checklists.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | True only after the user explicitly confirms this exact change. Without it the tool changes nothing and returns the change for review. |
| expectedVersion | string | yes | Opaque version from the latest library_list_get or Library List tool result. |
| listId | string | yes | Library List ID from library_lists_search or library_list_get. |
No output schema declared.
No examples provided.
library_list_get Read Library List ~68
Read one owned Tineo Library List, including every stable item UUID and its version. Read before editing; preserve fields the user did not ask to change. Never use trip segment IDs or guess list/item IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| itemType | string | – | – |
| listId | string | yes | – |
No output schema declared.
No examples provided.
library_list_item_add Add Library List Item ~160
Add one item to an owned Library List. Generate one new itemId UUID for the item and reuse it on retries, so a retried call never adds a duplicate. Use the listId and expectedVersion from the latest library_list_get. On library_version_mismatch, read the list again and reconsider the change; never retry blindly. Library Lists only, not trip checklists.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedVersion | string | yes | Opaque version from the latest library_list_get or Library List tool result. |
| itemId | string | yes | New caller-generated UUID for the item; reuse the same value when retrying. |
| listId | string | yes | Library List ID from library_lists_search or library_list_get. |
| text | string | yes | The item's text. |
No output schema declared.
No examples provided.
library_list_item_delete Delete Library List Item ~166
Permanently delete one item from an owned Library List. Show the user the exact item first; call with confirmed=true only after they confirm. Use the listId and expectedVersion from the latest library_list_get. On library_version_mismatch, read the list again and reconsider the change; never retry blindly. Library Lists only, not trip checklists.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | True only after the user explicitly confirms this exact change. Without it the tool changes nothing and returns the change for review. |
| expectedVersion | string | yes | Opaque version from the latest library_list_get or Library List tool result. |
| itemId | string | yes | Existing item ID from library_list_get. |
| listId | string | yes | Library List ID from library_lists_search or library_list_get. |
No output schema declared.
No examples provided.
library_list_item_update Update Library List Item ~212
Change one existing item in an owned Library List (text, completed, color, notes, priority, dueDate), for example to check it off. Changes only the fields named in updateFields. Use the listId and expectedVersion from the latest library_list_get. On library_version_mismatch, read the list again and reconsider the change; never retry blindly. Library Lists only, not trip checklists.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedVersion | string | yes | Opaque version from the latest library_list_get or Library List tool result. |
| itemId | string | yes | Existing item ID from library_list_get. |
| listId | string | yes | Library List ID from library_lists_search or library_list_get. |
| updateFields | array | yes | The fields the user asked to change. Only these keys of updates are applied. To clear a nullable field, name it here and set it to an empty string, only when the user asks to clear it. |
| updates | object | yes | New values for the fields named in updateFields. |
No output schema declared.
No examples provided.
library_list_items_add Add Library List Items ~168
Add several items to an owned Library List in one call, in order (for example a whole packing or to-do list). Give each item its own new itemId UUID and reuse the same values on retries, so a retried call never adds duplicates. Up to 100 items per call; split longer lists. Use the listId and expectedVersion from the latest library_list_get. On library_version_mismatch, read the list again and reconsider the change; never retry blindly. Library Lists only, not trip checklists.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedVersion | string | yes | Opaque version from the latest library_list_get or Library List tool result. |
| items | array | yes | The new items in order. |
| listId | string | yes | Library List ID from library_lists_search or library_list_get. |
No output schema declared.
No examples provided.
library_list_items_reorder Reorder Library List Items ~188
Reorder the items of an owned Library List. orderedItemIds must contain every current item ID exactly once, in the new order. Show the user the proposed order first; call with confirmed=true only after they confirm. Use the listId and expectedVersion from the latest library_list_get. On library_version_mismatch, read the list again and reconsider the change; never retry blindly. Library Lists only, not trip checklists.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | True only after the user explicitly confirms this exact change. Without it the tool changes nothing and returns the change for review. |
| expectedVersion | string | yes | Opaque version from the latest library_list_get or Library List tool result. |
| listId | string | yes | Library List ID from library_lists_search or library_list_get. |
| orderedItemIds | array | yes | Every current item ID exactly once, in the new order. |
No output schema declared.
No examples provided.
library_list_update Update Library List ~190
Change one owned Library List's own details (title, emoji, color, description). Changes only the fields named in updateFields; never touches the list's items. Use the listId and expectedVersion from the latest library_list_get. On library_version_mismatch, read the list again and reconsider the change; never retry blindly. Library Lists only, not trip checklists.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedVersion | string | yes | Opaque version from the latest library_list_get or Library List tool result. |
| listId | string | yes | Library List ID from library_lists_search or library_list_get. |
| updateFields | array | yes | The fields the user asked to change. Only these keys of updates are applied. To clear a nullable field, name it here and set it to an empty string, only when the user asks to clear it. |
| updates | object | yes | New values for the fields named in updateFields. |
No output schema declared.
No examples provided.
library_lists_search Find Library Lists ~113
Find the signed-in user's Tineo Library Lists by title or description. Return candidate IDs; when several titles match, ask the user to select one. These are freestanding Library Lists, separate from trip packing/checklists. Only lists are supported; do not invent journal, place or file edits.
| Name | Type | Req | Description |
|---|---|---|---|
| itemType | string | – | – |
| limit | integer | – | Maximum candidates, 1..50. Omitted or zero uses 20. |
| offset | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
mentions_search Find Trips to Mention ~43
Typeahead search over the user's Tineo trips for composer @-mentions. Returns resource links to trips.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search text; may be empty. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No examples provided.
packing_list_regenerate Regenerate Packing List ~231
Regenerate a trip's existing packing checklist: replaces the generated items the user has not touched, and keeps every item the user checked, added or edited. Use only after the user asks to redo or refresh the list. With people, only those people's lists are regenerated (a person without a list gets a new one); a trip with no list yet gets a new one. Provide the trip_id from trips_list. Tineo builds the list on its servers with its AI model provider, sending the trip's title, dates, destinations, itinerary items, weather forecast, any context_notes, and each person's age band and notes (never their name).
| Name | Type | Req | Description |
|---|---|---|---|
| context_notes | string | – | Optional packing-relevant details the user asked to include, such as planned activities or special gear. Pass only what the user wants reflected in the list. Never include health conditions, medical… |
| people | array | – | Optional. One personalized list per person (max 6), titled with the person's name. |
| trip_id | string | yes | Tineo trip ID (from trips_list). |
No output schema declared.
No examples provided.
place_details View place details ~116
Look up a selected place ID for its name, address, map URL, coordinates, photos, and timezone when missing from places_search. Google rich business details are disabled: do not use this tool to answer opening-hours, open-now, price, website, phone, or rating questions. Missing fields mean unavailable, not closed or absent. Previously cached optional details may be stale.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional BCP 47 language code for place data |
| place_id | string | yes | The provider place ID returned by places_search |
No output schema declared.
No examples provided.
places_search Search places ~188
Search for real-world places by text. Use this when the user needs to find a hotel, restaurant, venue, airport, station, port, parking location, or other place before adding or editing a trip segment.
| Name | Type | Req | Description |
|---|---|---|---|
| included_type | string | – | Optional place type bias, such as lodging, restaurant, airport, train_station, parking, tourist_attraction, or point_of_interest |
| language | string | – | Optional BCP 47 language code for place data |
| location_bias | object | – | Optional latitude/longitude used to bias search results |
| max_results | integer | – | Maximum results to return, from 1 to 20. Defaults to 10. |
| query | string | yes | The place search text, such as a hotel name, restaurant, airport, venue, station, or full address |
| radius_meters | number | – | Optional radius in meters around location_bias |
No output schema declared.
No examples provided.
search Search Tineo ~47
Use this when the user wants to search their trips, itinerary segments, or travel documents by keyword. Returns citation-ready IDs, titles, and canonical URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query |
No output schema declared.
No examples provided.
search_airport_lounges Search Airport Lounges ~144
Requires Tineo Ultra access. Search Tineo's populated first-party airport-lounge catalog by IATA and optional terminal/gate. Returns terminal, concourse, stored gate reference, location, access, amenity, rating, and day-pass fields with categorical gate relevance (not walking distance).
| Name | Type | Req | Description |
|---|---|---|---|
| gate | string | – | Optional gate, such as A17. |
| iata_code | string | yes | Required 3-letter IATA airport code, such as ATL. |
| max_results | integer | – | Maximum lounges returned. Default 10. |
| terminal | string | – | Optional terminal or concourse, such as Terminal 5 or Concourse A. |
| Name | Type | Req | Description |
|---|---|---|---|
| airportIata | string | yes | – |
| airportTimeZone | string|null | – | – |
| gate | string|null | – | – |
| localDate | string|null | – | – |
| lounges | array | yes | – |
| note | string|null | – | – |
| schemaVersion | integer | yes | – |
| terminal | string|null | – | – |
| timeFormat | string | – | The signed-in user's saved time format. Absent or auto uses the host locale. |
| totalMatches | integer | yes | – |
| type | string | yes | – |
No examples provided.
search_attractions Search Attractions & Sights ~130
Search for popular tourist attractions, sights, landmarks, and things to do in a destination using TripAdvisor and Google Places. Returns attraction cards with ratings, descriptions, addresses, and ticket/experience links. Use when the user asks about top sights, landmarks, or attractions in a city.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of attractions to return (max 10). |
| location | string | – | Optional city/area location filter. |
| query | string | yes | Destination name, landmark, or attraction search term (e.g. 'Rome', 'Eiffel Tower', 'museums in London'). |
No output schema declared.
No examples provided.
search_flight_prices Search Flight Prices ~837
Never send more than 3 search_flight_prices calls in one turn: calls beyond 3 are rejected without searching. Search for flight itineraries with prices between two airports on a date using Google Flights. Returns available itineraries with prices, durations, airlines, layovers, and ranked route-search actions. Ages 12-17 are mapped as adults where a provider requires it; ages 0-1 are infants whose lap-versus-seat placement and provider policy must be confirmed before booking. Each account runs one search at a time; the second and third wait their turn and still return results. When the user names several airports, destinations, dates or trip lengths, search the 1 to 3 most likely combinations first (or one outbound_end_date range of up to 7 days), show the results, then ask before searching more. A queued or slow search returns lookupStatus pending with retry_after_seconds; it keeps its place and finishes on its own, so repeat the identical call after that wait to get its result. When the user rules out airlines or connection airports/countries, pass include_airlines/exclude_airlines/avoid_connection_airports/avoid_connection_countries so excluded routes are removed. Fares carry no baggage allowance: never claim a fare includes bags.
| Name | Type | Req | Description |
|---|---|---|---|
| adult_count | integer | – | Number of adult travelers (default 1). |
| arrival_airport | string | yes | Arrival airport IATA code, such as CDG. |
| avoid_connection_airports | array | – | Optional. Remove itineraries that connect at these airports (3-letter IATA codes). Single-date searches only. |
| avoid_connection_countries | array | – | Optional. Remove itineraries that connect in these countries (prefer ISO 3166 alpha-2 codes such as US, TR, RU; translate names to English). Single-date searches only. |
| cabin_class | string | – | Cabin class preference: 'economy', 'premium_economy', 'business', or 'first'. Default is 'economy'. |
| child_ages | array | – | Age of each traveler under 18. Ages 12-17 are provider-mapped as adults where required; ages 2-11 are children and 0-1 are infants. Confirm lap-versus-seat placement with the user/provider for ages 0… |
| currency | string | – | Optional ISO-style three-letter currency code. Omit to use the user's preferred currency, then the currency of the trip given by trip_id, then USD. |
| departure_airport | string | yes | Departure airport IATA code, such as JFK. |
| exclude_airlines | array | – | Optional. Remove itineraries with any flight on these airlines (IATA code, airline name, or alliance). Single-date searches only. |
| include_airlines | array | – | Optional. Keep only itineraries where every flight is on one of these airlines: 2-character IATA code such as LH, airline name, or an alliance (Star Alliance, oneworld, SkyTeam). Single-date searches… |
| max_stops | integer | – | Optional maximum number of stops (0 = nonstop only, 1 = up to 1 stop). |
| outbound_date | string | yes | Outbound date in YYYY-MM-DD format. To compare several departure days, pass outbound_end_date in this one call rather than sending one call per day. |
| outbound_end_date | string | – | Optional inclusive end date for a cheapest-returned-fare-per-day calendar, up to 7 outbound dates beginning at outbound_date. Each day reports priced, no_results, failed, or not_searched; prices are… |
| return_date | string | – | Optional return date in YYYY-MM-DD format for round-trip searches. |
| trip_id | string | – | Optional Tineo trip ID (from trips_list) this request is for. Used only to default the currency to that trip's currency when currency is omitted and the user has no preferred currency; ignored if the… |
No output schema declared.
No examples provided.
search_hotels Search Hotels & Lodging ~570
Search for hotels and accommodations. Ordinary searches use the text query. Dated radius searches use a geographic bounding box and exact distance filter; SearchAPI does not apply the text query or style preferences within the radius. Provider coverage may be incomplete and prices may change. A hotel_place_id without radius_meters searches by the resolved hotel name; with radius_meters it searches nearby. Only a unique identity match retains its offer links.
| Name | Type | Req | Description |
|---|---|---|---|
| adult_count | integer | – | Number of adults (alias: adults). |
| center_place_id | string | – | Optional place ID for the radius center, from places_search. Requires check_in and check_out. |
| check_in | string | – | Check-in date in YYYY-MM-DD format (alias: checkIn). |
| check_out | string | – | Check-out date in YYYY-MM-DD format (alias: checkOut). |
| currency | string | – | Optional ISO-style three-letter currency code. Omit to use the user's preferred currency, then the currency of the trip given by trip_id, then USD. |
| hotel_place_id | string | – | Optional specific hotel place ID. Searches priced inventory by hotel name, or nearby when radius_meters is supplied. Retains offer links only if identity is uniquely verified. Requires check_in and c… |
| latitude | number | – | Radius center latitude. Supply together with longitude instead of a place ID. Query may be omitted for a coordinate-only radius search. |
| limit | integer | – | Maximum number of hotel results to return (max 10). |
| longitude | number | – | Radius center longitude. Supply together with latitude instead of a place ID. Query may be omitted for a coordinate-only radius search. |
| query | string | – | Search query or destination city (e.g. 'hotels in Tokyo'). Required for ordinary hotel search. Google Hotels can mix in properties from nearby towns or districts; cards outside the searched place car… |
| radius_meters | integer | – | Geographic search radius, default 1000 meters when center_place_id or coordinates are given. Requires stay dates and a center. Text query and style preferences are not applied to radius provider sele… |
| trip_id | string | – | Optional Tineo trip ID (from trips_list) this request is for. Used only to default the currency to that trip's currency when currency is omitted and the user has no preferred currency; ignored if the… |
No output schema declared.
No examples provided.
search_tours Search Tours & Activities ~310
Search for bookable tours, activities, excursions, and experiences at a destination using GetYourGuide with Viator and Tiqets travelpayouts fallbacks. Returns tour options with titles, prices, ratings, durations, and booking links. Use when the user asks about things to do, tours, activities, excursions, or experiences in a city or destination. Search one destination per call.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Optional ISO-style three-letter currency code. Omit to use the user's preferred currency, then the currency of the trip given by trip_id, then USD. |
| date | string | – | Optional date in YYYY-MM-DD format to filter tours available on that day. |
| limit | integer | – | Maximum number of tour results to return (default 10, max 30). |
| provider | string | – | Preferred tour provider to search ('all', 'getyourguide', or 'viator'). Default is 'all'. |
| query | string | yes | Search query for ONE destination, optionally with an activity type (e.g. 'walking tour Rome', 'snorkeling Cancun'). Never list several cities in one query: for a multi-city trip, call this tool once… |
| trip_id | string | – | Optional Tineo trip ID (from trips_list) this request is for. Used only to default the currency to that trip's currency when currency is omitted and the user has no preferred currency; ignored if the… |
No output schema declared.
No examples provided.
segment_associate_place Associate Place With Segment ~177
Attach a Google Place to an ALREADY-EXISTING segment retroactively — writes a place association and syncs the segment's address/city/country/coordinates from the place. Use when a segment has a venue/name but no address (e.g. imported from a ticket confirmation with venue-only data). Requires a place_id from places_search/place_details. For CarRental/Transfer segments pass role "origin" or "destination"; omit for single-location segments (Activity, Lodging, EventTicket, Parking), which default to "primary".
| Name | Type | Req | Description |
|---|---|---|---|
| place_id | string | yes | Google Place ID from a prior places_search/place_details call. |
| role | string | – | Which location this place represents. Default "primary". |
| segment_id | string | yes | Segment ID (from segment_details/trip_details) to attach the place to. |
No output schema declared.
No examples provided.
segment_booking_links Get Segment Booking Links ~88
Return useful booking, reservation, ticket, check-in, itinerary, voucher, receipt, and travel-document links for one trip segment as booking_link_cards.
| Name | Type | Req | Description |
|---|---|---|---|
| classifications | array | – | Optional link classification filter, such as DirectReservation, CheckIn, ViewTickets, ManageBooking, ViewItinerary, or TravelDocuments. |
| segment_id | string | yes | The segment ID to search for booking links. |
No output schema declared.
No examples provided.
segment_create Create itinerary item ~544
Create a new segment in a trip. FIRST call segment_get_schema to get the required fields for the segment type. Required in fields, besides trip_id: Flight airline (or a flightNumber starting with the airline code, e.g. UA 123), departureAirportCode, arrivalAirportCode, startDateTime; Lodging propertyName, startDateTime; Activity title, startDateTime; EventTicket eventName, startDateTime; CarRental rentalCompany, startDateTime; Train and Ferry operator, departureCity, arrivalCity, startDateTime; Transfer provider, pickupLocation, dropoffLocation, startDateTime; Parking facilityName, startDateTime; Note title; Poll title, options. Then provide the trip_id, segment_type, and fields matching the schema. Segment dates must fall within the parent trip dates. Dates up to 1 day outside the trip extend it, with a warning; further out, call trip_update first. For an Activity, Lodging, EventTicket or Parking at a real place, call places_search first and put the result's place ID in fields.placeId: Tineo links that place (map pin and coordinates) and fills a missing name, address, phone and website. Never invent a time: if the user has not given or chosen one, ask, or send the date only (YYYY-MM-DD) in startDateTime and Tineo stores it as time not set. Send a clock time only when the user stated it or a booking shows it. For commercial cruise reservations and sea/port days use cruise_* tools. Never substitute Activity, CruiseActivity or another segment type for a cruise day. Ordinary shore excursions remain valid Activity/CruiseActivity. If cruise tools are unavailable explain the limitation and ask for clarification. Cruise/CruiseDay generic writes require the dedicated cruise tools; their schemas and full reads remain available.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | Field values matching the schema for the segment type. Get schema first with segment_get_schema. Activity activityType is one of: tour, dining, show, spa, class, sports, sightseeing, other (other wor… |
| segment_type | string | – | The type of segment to create (Flight, Lodging, CarRental, Train, Transfer, Ferry, EventTicket, Parking, Activity, Note, Poll) |
| trip_id | string | yes | The trip ID to add the segment to |
No output schema declared.
No examples provided.
segment_delete Delete itinerary item ~110
Delete a segment from a trip. This action cannot be undone. For commercial cruise reservations and sea/port days use cruise_* tools. Never substitute Activity, CruiseActivity or another segment type for a cruise day. Ordinary shore excursions remain valid Activity/CruiseActivity. If cruise tools are unavailable explain the limitation and ask for clarification. Cruise/CruiseDay generic writes require the dedicated cruise tools; their schemas and full reads remain available.
| Name | Type | Req | Description |
|---|---|---|---|
| segment_id | string | yes | The ID of the segment to delete |
No output schema declared.
No examples provided.
segment_details View itinerary item ~167
Get full details for a specific trip segment. Returns complete information based on segment type: flight details (airline, flight number, airports, terminals, seats, baggage), hotel details (property, address, check-in/out times, room type, amenities), activity details (venue, tickets, timing), event ticket details (event name, venue, timing, vendor, order, confirmation), car rental details (company, vehicle, pickup/dropoff locations), or transfer details (provider, transfer type, pickup/dropoff locations, addresses, and local times). bookingContext describes whether Tineo can prepare an in-app reviewed change or needs the full editor; it is not a save confirmation or additional write authority.
| Name | Type | Req | Description |
|---|---|---|---|
| segment_id | string | yes | The unique identifier of the segment to fetch details for |
| Name | Type | Req | Description |
|---|---|---|---|
| bookingContext | object|null | – | – |
| canEdit | boolean | – | – |
| duplicateStatus | object|null | – | – |
| segment | object | – | – |
No examples provided.
segment_get_schema Get itinerary item fields ~201
Get the schema for a segment type. CALL THIS FIRST before creating/updating segments. Returns required fields and their types for the specified segment type. Supported types: Flight, Lodging, CarRental, Train, Transfer, Ferry, EventTicket, Parking, Activity, Note, Poll. For commercial cruise reservations and sea/port days use cruise_* tools. Never substitute Activity, CruiseActivity or another segment type for a cruise day. Ordinary shore excursions remain valid Activity/CruiseActivity. If cruise tools are unavailable explain the limitation and ask for clarification. Cruise/CruiseDay generic writes require the dedicated cruise tools; their schemas and full reads remain available. Additional supported schemas: Cruise, CruiseDay, CruiseActivity.
| Name | Type | Req | Description |
|---|---|---|---|
| segment_type | string | yes | The segment type to get schema for (Flight, Lodging, CarRental, Train, Transfer, Ferry, EventTicket, Parking, Activity, Note, Poll); also Cruise, CruiseDay and CruiseActivity |
No output schema declared.
No examples provided.
segment_link_add Add Link To Segment ~219
Add a separate labeled, clickable URL (for example a restaurant Menu, online check-in, or directions link) to an ALREADY-EXISTING itinerary segment. Additive only: imported and existing links are never changed or removed, and an identical URL already on the segment is reported instead of duplicated. Find the segment first: call trips_list, then trip_details with sections ["segments"] on each candidate trip and match the segment by title or venue (keyword search can miss names), then confirm with the user. Returns the saved link and every link now on the segment.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Short button label shown for the link, such as "Menu", "Online Check-in", or "Directions". |
| link_type | string | – | Optional link category. Defaults to Other (use Other for menus and general websites). |
| segment_id | string | yes | Segment ID (from trip_details/segment_details) to add the link to. |
| url | string | yes | Absolute http(s) URL to add, such as a restaurant menu page. |
No output schema declared.
No examples provided.
segment_update Update itinerary item ~355
Update an existing segment. Only provide the fields you want to change. Get field names from segment_get_schema if unsure. Segment dates must fall within the parent trip dates; use trip_update first to extend the trip. To change a checklist's tasks use checklist_items_add, checklist_item_update, checklist_items_remove or checklist_items_reorder (IDs from trip_checklists). The result lists the saved value of every field you sent, read back from Tineo, so do not call segment_details to confirm the change. On an Activity, Lodging, EventTicket or Parking, fields.placeId (a place_id from places_search) attaches that place the same way segment_associate_place does, replacing the stored address with the place's. Never invent a time: if the user has not given or chosen one, ask, or send the date only (YYYY-MM-DD) in startDateTime and Tineo stores it as time not set. Send a clock time only when the user stated it or a booking shows it. For commercial cruise reservations and sea/port days use cruise_* tools. Never substitute Activity, CruiseActivity or another segment type for a cruise day. Ordinary shore excursions remain valid Activity/CruiseActivity. If cruise tools are unavailable explain the limitation and ask for clarification. Cruise/CruiseDay generic writes require the dedicated cruise tools; their schemas and full reads remain available.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | Field values to update. Only include fields that should be changed. Send null to clear an optional field; an empty string is ignored and the stored value is kept. |
| id | string | – | Alias for segment_id (widget compatibility) |
| segment_id | string | – | The ID of the segment to update |
No output schema declared.
No examples provided.
settings_read Read Tineo Settings ~34
Reads the user's Tineo display and notification settings: units, date and time formats, flight monitoring, and trip reminder emails.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| layout | array | – | – |
| schema | object | yes | – |
| values | object | yes | – |
No examples provided.
settings_update Update Tineo Settings ~35
Changes the user's Tineo display and notification settings. Only include settings the user asked to change.
| Name | Type | Req | Description |
|---|---|---|---|
| set | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| values | object | yes | – |
No examples provided.
support_ticket_create Create Support Ticket ~222
Create a Tineo support ticket after the user explicitly asks or confirms and notify Tineo support by email. Use when the assistant cannot complete a request, a tool fails, or the requested capability is unsupported. Tineo attaches the user's app version, platform, device model and OS version automatically, so do not ask for them or list them as unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | Optional image attachments as base64 data URIs. |
| confirmed | boolean | yes | Must be true only after the user directly asks to create a ticket or confirms the assistant's offer. |
| description | string | yes | User-facing explanation of what failed or could not be completed. |
| failure_context | string | – | The failed Tineo tool name and its error text, if a Tineo tool failed. |
| segment_id | string | – | Related segment ID, if known. |
| source | string | – | Why the support ticket is being created. |
| summary | string | yes | Short support-ticket summary. |
| trip_id | string | – | Related trip ID, if known. |
No output schema declared.
No examples provided.
tineo_ping Check Tineo connection ~39
Check that Tineo is connected and the user is signed in. Returns the signed-in account's name and email; it does not list trips.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | – |
| user | object | – | – |
No examples provided.
train_booking_link Train Booking Link ~295
Return a train or bus search handoff between two cities, routed by region. Asian routes open 12Go with the route and date prefilled. European routes open the Omio route page (Madrid-Barcelona opens a prefilled search; Tokyo-Kyoto also gets the Omio page). Routes in other regions, such as the Americas, return no handoff. Confirm dates and passengers on the partner site; the card preserves the requested date for reference. No live fares, availability, or tickets are provided.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Optional ISO-style three-letter display currency, such as EUR. Omit to use the user's preferred currency, then the currency of the trip given by trip_id, then EUR. |
| departureDate | string | yes | Local departure date in YYYY-MM-DD format. |
| destination | string | yes | Arrival city or station. |
| locale | string | – | Optional locale, such as en. |
| origin | string | yes | Departure city or station. |
| passengers | integer | – | Optional passenger count. Defaults to 1. |
| returnDate | string | – | Optional return date in YYYY-MM-DD format. |
| trip_id | string | – | Optional Tineo trip ID (from trips_list) this request is for. Used only to default the currency to that trip's currency when currency is omitted and the user has no preferred currency; ignored if the… |
No output schema declared.
No examples provided.
travel_document_assign_trip Assign Travel Document To Trip ~180
Move or assign a travel document (insurance, visa, passport scan, voucher) to another trip the user OWNS, or back to the general library. Provide document_id from a documents listing and trip_id from trips_list. Omit trip_id (or pass null) to move the document to the library. Only trips the user owns are valid targets. The document's linked files move with it; a file also attached to another document is left in place and reported. If more than one document could match the request, confirm which one before moving. Returns the document, its previous and new trip, and how many linked files were re-pointed.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | Id of the travel document to move. |
| trip_id | – | – | Target trip id owned by the user; omit or null to unassign the document to the library. |
No output schema declared.
No examples provided.
traveler_add Add trip traveler ~164
Add a traveler only after known_participants and the user's explicit invitation decision. With an invitation, pass email and invite_confirmed=true; this creates and sends the trip invitation. If the user explicitly declines, omit email and pass invite_confirmed=false. If the email matches someone the user already added to a trip, that existing traveler's name is reused instead of creating a second identity for the same person.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Confirmed invitation email. Required when invite_confirmed=true and forbidden when false. | |
| invite_confirmed | boolean | yes | True only after the user explicitly confirms sending an invitation. False only after they explicitly decline. |
| name | string | yes | Traveler's display name |
| trip_id | string | yes | The trip ID to add the traveler to |
No output schema declared.
No examples provided.
traveler_assign Assign traveler to itinerary item ~209
Assign one or more travelers to one or more segments in a single call. To put the same travelers on several segments (for example every flight of a trip), pass all of them in segment_ids and all travelers in traveler_ids in one call instead of one call per segment. Up to 50 segments and 50 travelers per call, and at most 200 segment-traveler pairs. Assigning an already-assigned traveler is a no-op, and each segment succeeds or fails on its own: the result lists what was assigned and, per segment, what failed and why.
| Name | Type | Req | Description |
|---|---|---|---|
| segment_id | string | – | One segment ID to assign travelers to. Use segment_ids for several. |
| segment_ids | array | – | Segment IDs to assign the same travelers to, in one call. |
| traveler_id | string | – | One trip traveler ID to assign. Use traveler_ids for several. |
| traveler_ids | array | – | Trip traveler IDs (from trip_travelers) to assign to every listed segment. |
No output schema declared.
No examples provided.
traveler_update_email Correct pending traveler email ~103
Correct one pending, unaccepted trip traveler's email after the owner supplies the exact traveler ID and new email. A changed address revokes the old link and automatically sends a renewed invitation. Report invitationSent truthfully; an unchanged address sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | New email explicitly supplied by the owner | |
| traveler_id | string | yes | Exact pending traveler ID from trip_travelers |
| trip_id | string | yes | Trip ID owned by the caller |
No output schema declared.
No examples provided.
trip_booking_links Get Trip Booking Links ~183
Return useful booking, reservation, ticket, check-in, itinerary, and affiliate flight-search links for a user's trip as booking_link_cards. Use this when the user asks for booking links, reservations, tickets, check-in, vouchers, receipts, or comparable flight-booking options.
| Name | Type | Req | Description |
|---|---|---|---|
| classifications | array | – | Optional link classification filter, such as DirectReservation, CheckIn, ViewTickets, ManageBooking, ViewItinerary, TravelDocuments, or FlightAffiliateSearch. |
| max_results | integer | – | Maximum number of booking-link cards to return. Defaults to 12 and is capped at 25. |
| segment_types | array | – | Optional segment type filter, such as Flight, Lodging, Activity, EventTicket, CarRental, Transfer, Train, Ferry, Parking, or CruiseActivity. |
| trip_id | string | yes | The trip ID to search for booking links. |
No output schema declared.
No examples provided.
trip_checklists Trip Checklists ~261
Read every checklist on a trip with its items. Returns each checklist's title and, for every task, a stable itemId, text, category (section heading), position (0-based stored order; the app groups tasks under their section headings in first-appearance order), isChecked (complete for everyone on a shared trip) and checkedByMe (on a shared trip a task you ticked stays unchecked until every traveler ticks it). Tasks are a flat list: there are no subtasks or nested items. Pass checklist_id (the checklist's segment ID) to read just one checklist. Call this before editing items so you have the item IDs. To create a checklist use segment_create (type Note, isChecklist true, checklistItems [{text, category?}]). To change tasks use checklist_items_add (append tasks), checklist_item_update (text, category, or checked to mark done/not done), checklist_items_remove, or checklist_items_reorder, passing checklist_id and the item IDs. Delete a whole checklist with segment_delete. Never show IDs to users.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_id | string | – | Optional. The checklist note's segment ID, to read just that one checklist. |
| trip_id | string | yes | ID of the trip (from trips_list). |
No output schema declared.
No examples provided.
trip_cities_list List Trip Cities ~43
List the ordered city associations for a trip. Returns trip_city_id values used by update, remove, and reorder.
| Name | Type | Req | Description |
|---|---|---|---|
| trip_id | string | yes | Trip ID. |
No output schema declared.
No examples provided.
trip_cities_reorder Reorder Trip Cities ~67
Replace the trip city order using every current trip_city_id exactly once. The first city drives the automatic cover when an image is available.
| Name | Type | Req | Description |
|---|---|---|---|
| ordered_trip_city_ids | array | yes | Complete ordered list of current trip_city_id values. |
| trip_id | string | yes | Trip ID. |
No output schema declared.
No examples provided.
trip_city_add Add Trip City ~205
Add a city to the end of a trip's ordered city list. This is idempotent when an equivalent city is already present. Pass city_name plus country: names are matched against the catalog (including aliases), a major city that shares its name with smaller places resolves to the major one, and a real town or island missing from the catalog (for example Bijagua or Santorini) is looked up in that country and added automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| city_id | string | – | Exact city catalog ID. Provide this OR city_name. |
| city_name | string | – | City, town or island name. Provide this OR city_id; ambiguous names return candidates, so pass country as well. |
| country | string | – | Country name or ISO code (for example CR or Costa Rica). Strongly recommended with city_name: it disambiguates same-named cities and lets Tineo add a place that is missing from the catalog. |
| trip_id | string | yes | Trip ID. |
No output schema declared.
No examples provided.
trip_city_remove Remove Trip City ~59
Remove one city association from a trip by trip_city_id. Confirm this destructive action with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| trip_city_id | string | yes | Trip-city association ID returned by trip_cities_list. |
| trip_id | string | yes | Trip ID. |
No output schema declared.
No examples provided.
trip_city_update Update Trip City ~154
Replace one trip-city association with another city. This never edits the shared city catalog record.
| Name | Type | Req | Description |
|---|---|---|---|
| city_id | string | – | Exact city catalog ID. Provide this OR city_name. |
| city_name | string | – | City, town or island name. Provide this OR city_id; ambiguous names return candidates, so pass country as well. |
| country | string | – | Country name or ISO code (for example CR or Costa Rica). Strongly recommended with city_name: it disambiguates same-named cities and lets Tineo add a place that is missing from the catalog. |
| trip_city_id | string | yes | Trip-city association ID returned by trip_cities_list. |
| trip_id | string | yes | Trip ID. |
No output schema declared.
No examples provided.
trip_cover_update Update Trip Cover Photo ~116
Set a trip's cover photo from an image URL or a place_photo_reference returned by places_search/place_details. Becomes the trip's hero image immediately. Provide the trip_id from trips_list.
| Name | Type | Req | Description |
|---|---|---|---|
| image_url | string | – | Direct https:// image URL to use as the cover. Provide this or place_photo_reference. |
| place_photo_reference | string | – | A photoReference from a places_search/place_details photos entry. Provide this or image_url. |
| trip_id | string | yes | Tineo trip ID (from trips_list). |
No output schema declared.
No examples provided.
trip_create Create trip ~180
Create a new trip with explicit start_date and end_date (YYYY-MM-DD), covering its planned segments. Returns its ID; the authenticated user becomes the owner.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional trip description or notes, up to 1000 characters (keep it under about 900) |
| destination | string | – | Primary destination city or region |
| end_date | string | yes | Trip end date in YYYY-MM-DD format |
| start_date | string | yes | Trip start date in YYYY-MM-DD format |
| title | string | yes | Trip title MUST be a human-readable destination name (e.g. 'Barcelona', 'Tokyo & Kyoto (Oct 2026)'). DO NOT use hyphenated airport corridor codes (e.g. 'DAC-IST-BCN-IST-DAC-CXB'). If unsure, provide… |
No output schema declared.
No examples provided.
trip_delete Delete trip ~74
Delete a trip owned by the authenticated user and its itinerary segments. Requires confirmed=true after explicit user confirmation. Also removes connected calendar events when automatic sync is enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | True only after the user explicitly confirms deleting this trip and its itinerary. |
| trip_id | string | yes | ID of the trip to delete. |
No output schema declared.
No examples provided.
trip_details View trip itinerary ~195
Get detailed information about a specific trip. The text response includes the trip summary plus a chronological list of every segment (flights, hotels, activities, etc.) with each segment_id, so you can chain directly to segment_details, segment_update, segment_delete, or flight_status_for_segment without another search. Also includes traveler count. For full per-segment details, use segment_details with the returned segment_id. Use sections and segment_types to filter the response.
| Name | Type | Req | Description |
|---|---|---|---|
| sections | array | – | Optional: filter which sections to include in the response. Values: 'segments', 'travelers'. Default: all sections. |
| segment_types | array | – | Optional: filter segments by type. Values: Flight, Lodging, CarRental, Train, Transfer, Ferry, EventTicket, Parking, Activity, Note, Poll. Default: all types. |
| trip_id | string | yes | The unique identifier of the trip to fetch details for |
| Name | Type | Req | Description |
|---|---|---|---|
| canEdit | boolean | – | – |
| capabilities | object | – | – |
| contractVersion | string | – | – |
| trip | object | – | – |
No examples provided.
trip_expense_create Add trip expense ~477
Add expenses to a trip's shared expense ledger, with who paid and how each is split. Uses the same rules as the Expenses screen in Tineo. For one expense, send description and amount; for several (a list of receipts, a spreadsheet, a whole trip's costs), send them all in expenses in one call, up to 50 per call, instead of one call per expense. Each item in expenses is added or rejected on its own; failed items come back by index with the reason, so resend only those. Get traveler IDs from trip_expenses_list. Defaults: payer is the user, date is today in the user's profile time zone, an equal split with everyone on the trip (all on the payer on a solo trip). Confirm the amounts, payers and splits with the user before calling; for a batch, confirm the list once.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Total amount, greater than 0. |
| category | string | – | – |
| currency | string | – | 3-letter currency code. Defaults to the trip currency, else USD. |
| date | string | – | Expense date, YYYY-MM-DD. Defaults to today in the user's profile time zone; send the user's local date when you know it. |
| description | string | – | What the expense was for, e.g. Travel insurance. |
| expenses | array | – | Several expenses in one call, each with the same fields as a single expense. Use instead of description and amount at the top level. |
| notes | string | – | – |
| paid_by | string | – | Traveler ID from trip_expenses_list travelers, or "me". Defaults to me. |
| split | object | – | Who the cost belongs to. type payer = all of it is the payer's cost (no split). equal = divided evenly among participants (omit participants for everyone on the trip). percentage = each participant's… |
| trip_id | string | yes | Tineo trip ID (from trips_list). |
| vendor | string | – | Merchant or vendor. |
No output schema declared.
No examples provided.
How do I install the Tineo MCP server?
Tineo is a hosted endpoint at https://api.tineo.ai/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 · api.tineo.ai
claude mcp add --transport http ai-tineo-tineo 'https://api.tineo.ai/mcp'
What is the Tineo MCP server?
Tineo is an MCP server listed in the public MCP registry as ai.tineo/tineo. Plan trips, search flights and hotels, and keep every booking in one shared itinerary. This page covers its hosted endpoint (https://api.tineo.ai/mcp).
Is the Tineo MCP server safe to use?
Tineo scores 85 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 Tineo MCP server expose?
Tineo exposes 110 tools: support_ticket_create, tineo_ping, search, fetch, import_parse_text_preview, and 105 more. Their descriptions and schemas cost roughly 19,641 tokens of context every time the server is loaded.
Does the Tineo MCP server require authentication?
Yes. Tineo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Tineo MCP server still maintained?
Tineo 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 Tineo MCP server?
VerifyMCP ran 14 checks on Tineo, 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.