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 →
trip_expense_update Edit trip expense ~323
Change an existing trip expense: amount, description, date, category, who paid, or how it is split (for example, make an expense 100% one person's). Get the expense ID and traveler IDs from trip_expenses_list. Send only the fields that change; a split replaces the whole split. Changing the amount of an equal or percentage split keeps the same people and proportions. Only the trip owner or an editor can edit expenses.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Total amount, greater than 0. |
| category | string | – | – |
| currency | string | – | 3-letter currency code. |
| date | string | – | Expense date, YYYY-MM-DD. |
| description | string | – | What the expense was for, e.g. Travel insurance. |
| expense_id | string | yes | Expense ID from trip_expenses_list. |
| notes | string | – | – |
| paid_by | string | – | Traveler ID from trip_expenses_list travelers, or "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… |
| vendor | string | – | Merchant or vendor. |
No output schema declared.
No examples provided.
trip_expenses_list Trip Expenses ~110
List a trip's individual expenses with who paid and how each is split, plus the trip's travelers (ID, name, and which one is the user). Use it to find an expense or traveler ID before trip_expense_update or trip_expense_create. For totals and who owes whom use get_trip_expense_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional words to match in the description, vendor or category. |
| trip_id | string | yes | Tineo trip ID (from trips_list). |
No output schema declared.
No examples provided.
trip_rename Rename trip ~68
Rename a trip owned by the authenticated user. Returns the old and new titles. May synchronize the title to the trip owner's connected calendars when automatic sync is enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| new_title | string | yes | The new trip title |
| trip_id | string | yes | The ID of the trip to rename |
No output schema declared.
No examples provided.
trip_restore Restore deleted trip ~168
Restore a deleted trip owned by the authenticated user, together with the itinerary items that were removed when it was deleted (items deleted separately before that stay deleted). Call without trip_id to list recently deleted trips. Call with trip_id to preview the restore; nothing changes until the user explicitly confirms and you call again with confirmed=true. May re-add the trip to the owner's connected calendars when automatic sync is enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | True only after the user explicitly confirms restoring this trip. Without it the tool only returns a preview. |
| expected_deleted_at | string | – | Optional deleted_at value from the preview. The restore is refused if the trip's deletion has changed since then. |
| trip_id | string | – | ID of the deleted trip to restore. Omit to list recently deleted trips. |
No output schema declared.
No examples provided.
trip_sharing_get Get trip sharing ~341
Read who can see the user's own trips, one trip (trip_id) or every trip they own (paged). For each trip it reports the three sharing mechanisms separately: people with per-trip access (access edit/view/invited/none, where invited means an invitation awaits acceptance and can still be revoked; invitation status pending/accepted/declined/expired, level view/edit, and traveler role), whether a public view link is active, and the trip's own friend-sharing switches (hidden from friends, plans shared with friends; per trip, not account settings). Pass friend_user_id (from friends_list) to also get that friend's exact state on each trip: per-trip access, invitation, and whether they see the trip summary or full plan through friend sharing (planVisibleVia: friend_grant = the user shares plans with this friend on every trip, trip_grant = this trip shares plans with all friends, or both). Use this before trip_sharing_set and to report sharing status. Only the trip owner can read this. Revoked invitations are deleted, so they are not listed. Never show IDs to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| friend_user_id | string | – | Optional friend user_id from friends_list. Adds that friend's access on each trip. |
| page | integer | – | 1-based page when trip_id is omitted. Default 1. |
| page_size | integer | – | Trips per page (max 50). Default 25. |
| trip_id | string | – | Optional trip ID. Omit to page through every trip the user owns. |
| upcoming_only | boolean | – | Only trips that have not ended yet. Default false. |
No output schema declared.
No examples provided.
trip_sharing_set Share trips with a friend ~604
Give one friend view or edit access to the user's own trips, change their level, or remove it (access=none), for specific trips (trip_ids) or every trip the user owns (all_trips=true, 25 per page). Idempotent: it checks each trip first and only changes what differs, so re-running it never sends a duplicate invitation. New access is an invitation emailed to the friend, who gets access once they accept. Without confirmed=true nothing is written or emailed: it returns the plan per trip (would_invite, would_update_access, would_revoke, already_correct, already_invited, needs_attention). Show that plan, and call again with the same arguments plus confirmed=true only once the user has explicitly asked for this change, in this conversation or in the instructions of a scheduled task they set up; after they approve the plan, apply it without previewing or asking again. Results per trip: invited, invitation_updated, access_updated, revoked, already_correct, already_invited, needs_attention (with a reason, e.g. not the owner or access via the traveler list) or failed; report them to the user, describing invited trips as pending invitations rather than access already granted. Friend summaries are separate and never changed here: they follow the user's friend settings and each trip's hide-from-friends switch. Only friends can get access; for someone who is not a friend yet, offer friend_request_send first. If their friend request is still pending, the call changes nothing and returns friendRequest and a note: tell the user they haven't accepted yet, and only if the user still wants it, call again with confirmed=true and pending_friend_confirmed=true. Get friend_user_id from friends_list; never guess it from a name. Never show IDs to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | yes | view = can see the trip; edit = can change it; none = remove their per-trip access. |
| all_trips | boolean | – | Apply to every trip the user owns, 25 per page. Provide this OR trip_ids. |
| confirmed | boolean | – | true applies the change. Omit or false to preview without writing or emailing anything. |
| friend_user_id | string | yes | The friend's user_id from friends_list. For access=none, any user_id listed with access in trip_sharing_get. |
| message | string | – | Optional note for new invitation emails (max 280 chars). |
| page | integer | – | With all_trips, the 1-based page of 25 trips. Default 1. |
| pending_friend_confirmed | boolean | – | Only when the friend request is still pending: true once the user, told they haven't accepted yet, still wants to grant this access. |
| trip_ids | array | – | Trip IDs to change. Provide this OR all_trips. |
| upcoming_only | boolean | – | With all_trips, only trips that have not ended yet. Default false. |
No output schema declared.
No examples provided.
trip_travelers List trip travelers ~56
Get the list of travelers/participants for a specific trip. Returns names, emails, roles, and which segments each traveler is assigned to.
| Name | Type | Req | Description |
|---|---|---|---|
| trip_id | string | yes | The unique identifier of the trip to get travelers for |
| Name | Type | Req | Description |
|---|---|---|---|
| canEdit | boolean | – | – |
| travelers | array | – | – |
| tripId | string | – | – |
No examples provided.
trip_update Update trip ~219
Update trip dates, title, destination, or description for a trip the authenticated user can edit. May synchronize changes to the trip owner's connected calendars when automatic sync is enabled.
| 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 |
| destination_confirmed | boolean | – | Required true when changing destination on a trip that already has dated itinerary items; confirms this is a parent-trip change, not an item location correction. |
| destination_scope | string | – | Required as 'trip' when changing destination on a trip that already has dated itinerary items. |
| end_date | string | – | Trip end date in YYYY-MM-DD format |
| name | string | – | Alias for title |
| start_date | string | – | Trip start date in YYYY-MM-DD format |
| title | string | – | New trip title (e.g., 'Japan October 2026') |
| trip_id | string | yes | The ID of the trip to update |
No output schema declared.
No examples provided.
trips_hub Tineo: My Trips ~49
Opens the Tineo trips app: browse current, upcoming, and past trips and open a trip's day-by-day itinerary. The user launches it from the ChatGPT sidebar or a conversation panel.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| activeCount | integer | yes | – |
| pastTruncated | boolean | yes | – |
| sections | object | yes | – |
| totalCount | integer | yes | – |
| type | string | yes | – |
| upcomingTruncated | boolean | yes | – |
No examples provided.
trips_list List trips ~102
List the user's trips. Use this when the user wants to see their trips, search for a specific trip, or asks about their travel plans.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of trips to return. Defaults to 10, max 50. |
| search | string | – | Search query to filter trips by destination, name, or location |
| status | string | – | Filter by trip status: all, upcoming, past, or ongoing. Defaults to all. |
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | – |
| totalCount | integer | – | – |
| trips | array | – | – |
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.