Tineo
REMOTE · API.TINEO.AI
Plan trips, search flights and hotels, and keep every booking in one shared itinerary.
Available components
Last scanned (13 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 →
affiliate_program_catalog Affiliate Program Catalog ~337
Return Tineo's travel-affiliate catalog with truthful implementation status. Use only for questions about supported affiliate programs, never for a link to a specific or previously searched travel result. With generic search intent, validated generic adapters may include safe Tineo-owned CTA links. A card with bookingLink=null is metadata only, not a booking handoff or live inventory.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Optional ISO-style three-letter display currency. Omit to use the user's preferred currency, then the currency of the trip given by trip_id, then USD. |
| endDate | string | – | Optional local end/check-out date in YYYY-MM-DD format. |
| includeResearch | boolean | – | Include catalogued/research programs. Defaults to true. |
| limit | integer | – | Optional result cap. Defaults to 54. |
| locale | string | – | Optional locale. Defaults to en. |
| location | string | – | Optional city or destination used to build the provider search. |
| searchTerm | string | – | Concrete search intent. Required to generate booking CTA buttons. |
| startDate | string | – | Optional local start/check-in date in YYYY-MM-DD format. |
| travelers | integer | – | Optional traveler count. Defaults to 1. |
| 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… |
| vertical | string | – | Optional category filter, such as Hotels, Tours, Flights, Trains, or Transfers. |
No output schema declared.
No examples provided.
assistant_airbnb_search_trip Search Airbnbs for a Trip ~388
Search Airbnb listings for an existing Tineo trip. Derives location and dates from the trip; the model may override. location must be a city or area, not a whole country (ask the user which city). Each card has distance_km from the requested place and in_requested_area; listings outside the area come last. If none are in the area, say so with their distances and do NOT re-search the same place with a reworded location string. Amenity filtering only via the amenities enum; there is NO keyword/free-text filter, so tell the user anything else can't be filtered. If structuredContent.status is 'unavailable', do NOT retry the same search: share structuredContent.fallback_search_url (a prefilled airbnb.com search), offer a hotel search, or a support ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | – |
| amenities | array | – | Only listings with ALL of these amenities. These are the only supported amenity filters; there is no keyword/free-text filter. |
| check_in | string | – | Check-in date YYYY-MM-DD. |
| check_out | string | – | Check-out date YYYY-MM-DD. |
| children | integer | – | – |
| currency | string | – | ISO 4217 currency code (default USD). |
| infants | integer | – | Infants under 2. Airbnb does not count them as guests. |
| location | string | – | Optional override for the trip's destination. |
| max_results | integer | – | Default 5, max 5. |
| min_bathrooms | integer | – | – |
| min_bedrooms | integer | – | – |
| min_beds | integer | – | – |
| price_max | integer | – | – |
| price_min | integer | – | – |
| room_type | string | – | – |
| trip_id | string | yes | Tineo trip ID. Defaults below are derived from this trip when omitted. |
No output schema declared.
No examples provided.
assistant_airbnb_search_user Search Airbnbs ~409
Search Airbnb listings by location and dates. Use when the user is not asking about a specific trip in Tineo. Returns a slim list of cards (title, type, rating, host, URL). location must be a city or area, not a whole country (ask the user which city). Each card has distance_km from the requested place and in_requested_area; listings outside the area come last. If none are in the area, say so with their distances and do NOT re-search the same place with a reworded location string. Amenity filtering only via the amenities enum; there is NO keyword/free-text filter, so tell the user anything else can't be filtered. If structuredContent.status is 'unavailable', do NOT retry the same search: share structuredContent.fallback_search_url (a prefilled airbnb.com search), offer a hotel search, or a support ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | – |
| amenities | array | – | Only listings with ALL of these amenities. These are the only supported amenity filters; there is no keyword/free-text filter. |
| check_in | string | yes | Check-in date YYYY-MM-DD. |
| check_out | string | yes | Check-out date YYYY-MM-DD. |
| children | integer | – | – |
| currency | string | – | ISO 4217 currency code (default USD). |
| infants | integer | – | Infants under 2. Airbnb does not count them as guests. |
| location | string | yes | City, neighborhood, or landmark with its region and country (e.g., 'Lisbon, Portugal', 'Brooklyn, NY, USA', 'Orange, NSW, Australia'). |
| max_results | integer | – | Default 5, max 5. |
| min_bathrooms | integer | – | – |
| min_bedrooms | integer | – | – |
| min_beds | integer | – | – |
| price_max | integer | – | – |
| price_min | integer | – | – |
| room_type | string | – | – |
No output schema declared.
No examples provided.
audit_travel_documents Audit Travel Documents ~63
Audit expiration dates of the user's travel documents (passports, visas, insurance) and flag expired, expiring soon (<180 days), or expiring before trip end.
| Name | Type | Req | Description |
|---|---|---|---|
| trip_id | string | – | Optional trip ID to check documents against that trip's dates. |
No output schema declared.
No examples provided.
batch_segment_create Create itinerary items ~443
Create multiple segments in a trip in one call. To save into a trip that does not exist yet, send new_trip (title, start_date, end_date) instead of trip_id: the trip and its items are created in this one call. Put each item's values in fields, named as segment_get_schema returns them (Activity activityType is one of: tour, dining, show, spa, class, sports, sightseeing, other). Each item succeeds or fails on its own: valid items are created and failed items are returned by index with the reason, so resend only the failed items. Max 50 segments per call; split larger itineraries into several calls. 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 |
|---|---|---|---|
| new_trip | object | – | Use instead of trip_id to create the trip and its segments in one call. A trip of the user's with the same title and dates is reused. |
| segments | array | yes | Array of segments to create. Each must have segment_type and fields. |
| trip_id | string | – | The trip ID to add segments to. Send this or new_trip. |
No output schema declared.
No examples provided.
car_rental_booking_links Car Rental Booking Links ~231
Return DiscoverCars, Expedia and Booking.com affiliate car-rental search cards for a pickup city or airport and dates. These are provider search handoffs only, not live availability, prices, vehicles, or confirmed bookings.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Optional ISO-style three-letter display currency. Omit to use the user's preferred currency, then the currency of the trip given by trip_id, then USD. |
| dropoff_date | string | – | Optional local drop-off date in YYYY-MM-DD format. |
| locale | string | – | Optional locale. Defaults to en. |
| pickup_date | string | yes | Local pickup date in YYYY-MM-DD format. |
| pickup_location | string | yes | Pickup city or airport, e.g. Lisbon or LIS. Prefer the airport IATA code when picking up at an airport. |
| 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.
checklist_item_update Update Checklist Item ~177
Change one task on a trip checklist: its text, its category (section heading), or whether it is done. Get checklist_id and item_id from trip_checklists. Send only what changes. checked true marks the task done for the current user (on a shared trip it shows complete once every traveler ticks it); checked false unticks it. category "" removes the task from its section. Never show IDs to users.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | New section heading; "" clears it. |
| checked | boolean | – | true marks the task done for the current user; false unticks it. |
| checklist_id | string | yes | The checklist note's segment ID (checklist_id from trip_checklists). |
| item_id | string | yes | The task's itemId from trip_checklists. |
| text | string | – | New task text. |
No output schema declared.
No examples provided.
checklist_items_add Add Checklist Items ~131
Add one or more tasks to the end of an existing trip checklist. Get checklist_id from trip_checklists. Each item has text and an optional category (the section heading it appears under). A checklist holds at most 100 tasks; tasks are a flat list with no subtasks. Calling this twice adds the tasks twice. To create a new checklist use segment_create (type Note, isChecklist true). Never show IDs to users.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_id | string | yes | The checklist note's segment ID (checklist_id from trip_checklists). |
| items | array | yes | Tasks to append, in order. |
No output schema declared.
No examples provided.
checklist_items_remove Remove Checklist Items ~98
Permanently remove one or more tasks from a trip checklist. Get checklist_id and the item IDs from trip_checklists. Confirm with the user before removing. To delete a whole checklist use segment_delete. Never show IDs to users.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_id | string | yes | The checklist note's segment ID (checklist_id from trip_checklists). |
| item_ids | array | yes | IDs of the tasks to remove (itemId from trip_checklists). |
No output schema declared.
No examples provided.
checklist_items_reorder Reorder Checklist Items ~107
Put a trip checklist's tasks in a new order. Get checklist_id and the item IDs from trip_checklists, then send order listing every task ID exactly once in the new order. The app groups tasks under their section headings in first-appearance order. Never show IDs to users.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_id | string | yes | The checklist note's segment ID (checklist_id from trip_checklists). |
| order | array | yes | Every task ID on the checklist, in the new order. |
No output schema declared.
No examples provided.
cities_search Search City Catalog ~189
Search the saved city catalog by city name or alias before adding a city to a trip. Matches whole names, name prefixes and word starts (not text inside a word), exact matches first. Pass country to limit results to one country. An empty result does not mean the place does not exist: trip_city_add can add a real town or island that is missing from the catalog when you pass city_name and country. Returns stored city IDs and location details. Search results do not add or select a city.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country name or ISO code (for example CR or Costa Rica) to limit results to that country. Pass it whenever the user named a country. |
| limit | integer | – | Maximum number of results, from 1 to 50. Defaults to 10. |
| query | string | yes | City name or alias to search; two to 100 characters after trimming. |
No output schema declared.
No examples provided.
cruise_create cruise create ~170
Preview and commit cruise create operations atomically. First call cruise_get for expectedVersion. Omit confirmationToken to preview, show the changes to the user, then repeat the unchanged request with its token only after the user approves. Reuse idempotencyKey for retries. Omitting a field preserves it; null clears nullable fields. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Omit to preview. After the user reviews and approves the exact preview, repeat the unchanged request with its token to commit. Never manufacture approval. |
| request | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
cruise_day_create cruise day create ~172
Preview and commit cruise day create operations atomically. First call cruise_get for expectedVersion. Omit confirmationToken to preview, show the changes to the user, then repeat the unchanged request with its token only after the user approves. Reuse idempotencyKey for retries. Omitting a field preserves it; null clears nullable fields. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Omit to preview. After the user reviews and approves the exact preview, repeat the unchanged request with its token to commit. Never manufacture approval. |
| request | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
cruise_day_delete cruise day delete ~172
Preview and commit cruise day delete operations atomically. First call cruise_get for expectedVersion. Omit confirmationToken to preview, show the changes to the user, then repeat the unchanged request with its token only after the user approves. Reuse idempotencyKey for retries. Omitting a field preserves it; null clears nullable fields. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Omit to preview. After the user reviews and approves the exact preview, repeat the unchanged request with its token to commit. Never manufacture approval. |
| request | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
cruise_day_restore cruise day restore ~172
Preview and commit cruise day restore operations atomically. First call cruise_get for expectedVersion. Omit confirmationToken to preview, show the changes to the user, then repeat the unchanged request with its token only after the user approves. Reuse idempotencyKey for retries. Omitting a field preserves it; null clears nullable fields. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Omit to preview. After the user reviews and approves the exact preview, repeat the unchanged request with its token to commit. Never manufacture approval. |
| request | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
cruise_day_update cruise day update ~172
Preview and commit cruise day update operations atomically. First call cruise_get for expectedVersion. Omit confirmationToken to preview, show the changes to the user, then repeat the unchanged request with its token only after the user approves. Reuse idempotencyKey for retries. Omitting a field preserves it; null clears nullable fields. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Omit to preview. After the user reviews and approves the exact preview, repeat the unchanged request with its token to commit. Never manufacture approval. |
| request | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
cruise_delete cruise delete ~170
Preview and commit cruise delete operations atomically. First call cruise_get for expectedVersion. Omit confirmationToken to preview, show the changes to the user, then repeat the unchanged request with its token only after the user approves. Reuse idempotencyKey for retries. Omitting a field preserves it; null clears nullable fields. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Omit to preview. After the user reviews and approves the exact preview, repeat the unchanged request with its token to commit. Never manufacture approval. |
| request | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
cruise_get Get commercial cruise ~116
Read the complete commercial Cruise and linked CruiseDay fields, including soft-deleted items and version. Null and empty fields are omitted. Omit cruiseId to read the trip version before creation. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cruiseId | string|null | – | – |
| tripId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
cruise_reorder cruise reorder ~171
Preview and commit cruise reorder operations atomically. First call cruise_get for expectedVersion. Omit confirmationToken to preview, show the changes to the user, then repeat the unchanged request with its token only after the user approves. Reuse idempotencyKey for retries. Omitting a field preserves it; null clears nullable fields. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Omit to preview. After the user reviews and approves the exact preview, repeat the unchanged request with its token to commit. Never manufacture approval. |
| request | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
cruise_restore cruise restore ~170
Preview and commit cruise restore operations atomically. First call cruise_get for expectedVersion. Omit confirmationToken to preview, show the changes to the user, then repeat the unchanged request with its token only after the user approves. Reuse idempotencyKey for retries. Omitting a field preserves it; null clears nullable fields. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Omit to preview. After the user reviews and approves the exact preview, repeat the unchanged request with its token to commit. Never manufacture approval. |
| request | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
cruise_update cruise update ~170
Preview and commit cruise update operations atomically. First call cruise_get for expectedVersion. Omit confirmationToken to preview, show the changes to the user, then repeat the unchanged request with its token only after the user approves. Reuse idempotencyKey for retries. Omitting a field preserves it; null clears nullable fields. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | – | Omit to preview. After the user reviews and approves the exact preview, repeat the unchanged request with its token to commit. Never manufacture approval. |
| request | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contractVersion | string | yes | – |
| result | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
diagnose_failed_import Diagnose Failed Import ~79
Triage a failed, held, or partially processed email import on the user's account. Returns the failure step, error message, likely reason, and actionable next steps.
| Name | Type | Req | Description |
|---|---|---|---|
| import_id | string | – | Specific EmailImport ID to diagnose. |
| trip_id | string | – | Optional trip ID to look up the most recent non-clean import for that trip. |
No output schema declared.
No examples provided.
discover Discover travel options ~225
Search for hotels, restaurants, attractions, or activities to recommend to the traveler, returned as rich visual cards (image, rating, price level, link). Use this when the user wants suggestions or things to do/eat/stay near a place.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | What to discover: hotels, restaurants, attractions, or activities. |
| check_in_date | string | – | Optional YYYY-MM-DD check-in date (hotels). |
| check_out_date | string | – | Optional YYYY-MM-DD check-out date (hotels). |
| latitude | number | – | Optional latitude to bias the search. |
| location | string | – | City or area to search in, such as "Madrid" or "Lisbon, Portugal". Provide this when latitude/longitude are unknown. |
| longitude | number | – | Optional longitude to bias the search. |
| max_results | integer | – | Max cards to return, 1-10. Defaults to 8. |
| query | string | – | Optional refinement, such as "luxury", "family friendly", "tapas", or "museums". |
No output schema declared.
No examples provided.
duplicate_checklist Duplicate Checklist ~102
Duplicate a checklist into one or more new checklists on the same trip. Each copy keeps item text and sections; every item starts unchecked. Provide source_note_id (a checklist segment ID from trip_details) and one title per copy (max 10).
| Name | Type | Req | Description |
|---|---|---|---|
| source_note_id | string | yes | ID of the checklist to copy (from trip_details). |
| titles | array | yes | One title per copy (1 to 10, each up to 200 characters). |
No output schema declared.
No examples provided.
estimate_transfer_drive_time Estimate Transfer Drive Time ~155
Estimate the drive time of a Transfer or Transport segment (taxi, car service, airport transfer, ground transport) from its pickup and drop-off at its pickup time, using Apple Maps traffic prediction. apply=false (default) only reports the estimate; apply=true saves it as the estimated drop-off time so the Tineo calendar and iCal feed show the real ride length instead of a flat hour. A drop-off time already on the booking or set by the user is never changed, and a failed lookup changes nothing. Present the result as an estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | – | Save the estimate as the drop-off time. Default false. |
| segment_id | string | yes | ID of the Transfer or Transport segment. |
No output schema declared.
No examples provided.
fetch Fetch Tineo Item ~65
Use this when the user wants the full text for a specific Tineo search result. Pass an ID returned by search, such as trip:{id}, segment:{id}, travel-document:{id}, or document:{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID returned by the search tool |
No output schema declared.
No examples provided.
flight_booking_link Get Flight Booking Link ~80
Return a Tineo redirect card for comparable flight search for a trip flight when affiliate flight deep links are enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| flight_number | string | – | Optional flight number to target when segment_id is not known. |
| segment_id | string | – | Optional flight segment ID to target. |
| trip_id | string | yes | The trip ID that owns the flight. |
No output schema declared.
No examples provided.
flight_quickadd Add flight to trip ~201
Look up a real flight by number and date, then create it as a segment in the trip. Combines flight_quickadd_lookup + segment_create in one call. May take 2-5 seconds due to external flight data lookup. Segment dates must fall within the parent trip dates; use trip_update first to extend the trip.
| Name | Type | Req | Description |
|---|---|---|---|
| airline | string | – | Full airline name as fallback (e.g., 'American Airlines'). Used only if airline_code is not provided. |
| airline_code | string | – | IATA or ICAO airline code (AA, UA, DL, AAL). Optional if embedded in flight_number. |
| departure_date | string | yes | Departure date in YYYY-MM-DD format |
| flight_number | string | yes | Flight number, e.g. 'AA3242', 'UA100', or just '3242' if airline_code is provided |
| trip_id | string | yes | The trip ID to add the flight to |
No output schema declared.
No examples provided.
flight_quickadd_lookup Look up a flight ~143
Look up flight details by airline, flight number, and departure date before creating or editing a flight segment. Use this when the user gives a flight number and wants to add, preview, or verify a flight.
| Name | Type | Req | Description |
|---|---|---|---|
| airline | string | – | Optional airline name or callsign, such as American Airlines |
| airline_code | string | – | Optional IATA or ICAO airline code, such as AA, UA, DL, or AAL |
| departure_date | string | yes | Local scheduled departure date in YYYY-MM-DD format |
| flight_number | string | yes | Flight number, with or without the airline prefix, such as AA3242 or 3242 |
No output schema declared.
No examples provided.
flight_route_lookup Flight Route Lookup ~149
Find scheduled flights by route and date when the flight number is NOT known: origin airport, destination airport, local departure date, and optionally an airline. Returns matching flights with their flight numbers so the exact flight can then be added via flight_quickadd. Use flight_quickadd_lookup instead when the user already has the full flight number.
| Name | Type | Req | Description |
|---|---|---|---|
| airline_code | string | – | Optional IATA airline code filter, such as W6 for Wizz Air. |
| date | string | yes | Local departure date in YYYY-MM-DD format. |
| destination | string | yes | Arrival airport IATA code, such as SKG. |
| origin | string | yes | Departure airport IATA code, such as BUD. |
No output schema declared.
No examples provided.
flight_status_for_segment Check saved flight status ~125
Get current flight status for an existing flight segment in a user's trip. Use this when the user asks if a flight in their itinerary is delayed, canceled, on time, boarding, or has gate/terminal updates. Status is cached for a few minutes, so call it once per flight per answer; calling again for the same flight soon after returns the same result. The text says when the provider last updated the data.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Alias for segment_id |
| segment_id | string | yes | The flight segment ID from a trip itinerary or segment details result |
| Name | Type | Req | Description |
|---|---|---|---|
| flight | object | – | – |
| flightStatus | object | – | – |
| matched | boolean | – | – |
| type | string | – | – |
No examples provided.
forwarding_address_create Create Forwarding Address ~118
Create the authenticated user's personal Tineo forwarding address when they explicitly ask for one. Tineo reads email sent to that address and adds the travel bookings it finds to the user's trips, so the user can forward confirmations from any inbox or give it to a travel agent or booking site. Never replaces or changes an existing address: if one already exists it is returned unchanged. Use forwarding_address_get to read addresses without creating one.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | Must be true, set only after the user explicitly asks to create a forwarding address. |
No output schema declared.
No examples provided.
forwarding_address_get Get Forwarding Address ~98
Read the authenticated user's Tineo email forwarding addresses without changing anything. Returns the personal forwarding address when one exists, any other active personal addresses, and the universal trips@tineo.ai address, which works for mail forwarded from the user's primary or registered email. A personal address can also receive mail sent by an assistant or travel provider. If the user has no personal address and wants one, use forwarding_address_create after they ask for it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
friend_request_accept Accept Friend Request ~58
Accept an INCOMING pending friend request by request_id (from friend_requests_pending). This connects you and notifies the sender, so confirm with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The incoming request id from friend_requests_pending. |
No output schema declared.
No examples provided.
friend_request_decline Decline Friend Request ~50
Decline an INCOMING pending friend request by request_id (from friend_requests_pending). Confirm with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The incoming request id from friend_requests_pending. |
No output schema declared.
No examples provided.
friend_request_resend Resend Friend Request ~123
Resend the notification email for one of YOUR OUTGOING pending friend requests by request_id (from friend_requests_pending). This re-emails the recipient, so confirm with the user first and pass confirmed=true. Throttled on an escalating cadence (60s after the original send, 24h after the first resend) and capped at 2 total resends per request.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | Must be true. Set only after the user confirms they want to resend. |
| request_id | string | yes | The outgoing request id from friend_requests_pending. |
No output schema declared.
No examples provided.
friend_request_send Send Friend Request ~188
Send a friend request to another user by user_id, or by email. This emails a real person, so ALWAYS confirm the recipient with the user before calling, and pass confirmed=true only once they agree. Provide exactly one of user_id or email. If the email belongs to someone not on Tineo, an invitation to join is sent instead. For privacy, the email path always reports the same neutral result whether or not the address is registered.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | Must be true. Set only after the user has confirmed they want to send this request/invite. |
| string | – | Target email address. Provide this OR user_id, not both. | |
| message | string | – | Optional personal note (max 280 chars). |
| user_id | string | – | Target user id (e.g. from friends_list or a suggestion). Provide this OR email, not both. |
No output schema declared.
No examples provided.
friend_requests_pending Pending Friend Requests ~66
List the authenticated user's pending friend requests, split into incoming (awaiting your response) and outgoing (awaiting the other person). Returns the counterpart's name only, never their email. Use the returned request_id with friend_request_accept / friend_request_decline / friend_request_resend.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
friends_list List Friends ~98
List the authenticated user's accepted friends (paged). Returns each friend's name, home location, your label for them (Friend/Family) and your two-way trip-sharing state. Never returns other users' email addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number. Default 1. |
| page_size | integer | – | Friends per page (max 50). Default 20. |
| search | string | – | Optional case-insensitive name filter. |
No output schema declared.
No examples provided.
generate_packing_list Generate Packing List ~231
Create a weather- and activity-aware packing checklist for a trip, grouped into sections and saved as a pinned checklist note. Never changes an existing list: if one already exists it is returned unchanged; use packing_list_regenerate to replace it. Requires the trip to have a destination or at least one itinerary item. Provide the trip_id from trips_list. For one list per person, pass people (max 6). 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.
get_day_of_travel_brief Day Of Travel Brief ~92
Get airport day-of-travel intelligence combining cached airport conditions and ground-transportation guides (trains, shuttles, taxis) for an airport code or flight segment.
| Name | Type | Req | Description |
|---|---|---|---|
| flight_segment_id | string | – | Optional flight segment ID (from trip_details) to check departure and arrival airports. |
| iata_code | string | – | 3-letter IATA airport code, such as ATL. |
| Name | Type | Req | Description |
|---|---|---|---|
| airports | array | – | – |
| note | string | – | – |
| retrievedAt | string | – | – |
| type | string | – | – |
No examples provided.
get_flight_airport_conditions Flight Airport Conditions ~130
Get cached airport conditions, delay indices, weather, and flight rules for an IATA airport code (e.g. "ORD") or a flight segment's departure and arrival airports. Cache-only: reads existing airport intelligence and never triggers an external fetch.
| Name | Type | Req | Description |
|---|---|---|---|
| flight_segment_id | string | – | Optional flight segment ID (from trip_details) to look up both departure and arrival conditions. |
| iata_code | string | – | 3-letter IATA airport code, such as ORD or LHR. |
| route_to | string | – | Optional destination IATA airport code when checking a specific route. |
No output schema declared.
No examples provided.
get_flight_change_history Flight Change History ~134
Get recorded historical timeline of flight schedule changes, gate changes, and delays for flights monitored on the user's trips.
| Name | Type | Req | Description |
|---|---|---|---|
| airline_code | string | – | Optional 2-letter airline code, such as UA. |
| flight_date | string | – | Optional flight departure date in YYYY-MM-DD format. |
| flight_number | string | – | Optional flight number, such as 1234. |
| flight_segment_id | string | – | Optional flight segment ID. |
| since_days | integer | – | Lookback window in days. Default 30. |
| trip_id | string | – | Optional trip ID to filter changes for flights on that trip. |
No output schema declared.
No examples provided.
get_routes Get Routes ~198
Compare available driving, transit, walking, and bicycling route summaries between two places using Google Maps. Returns duration and distance estimates for supported modes, plus Uber, Lyft, Waymo, and Google Maps handoff buttons for the destination. Set origin to 'home' for the user's saved home address. Ground time excludes airport check-in and security. Fares, detailed legs, flights, and ferries are unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Ending place or address (1 to 300 characters). |
| modes | array | – | Modes to compare. Defaults to all four. |
| origin | string | yes | Starting place or address (1 to 300 characters), or 'home' for the user's private saved home address. |
| time | string | – | ISO 8601 date-time with an explicit UTC offset. Required for leave_by or arrive_by; omit for leave_now. |
| time_mode | string | – | When to travel. Default leave_now. |
No output schema declared.
No examples provided.
get_travel_stats Get Travel Stats ~37
Get lifetime travel summary statistics across all owned and shared trips: total trips, completed trips, total segments, and segment counts by type.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trip_expense_summary Trip Expense Summary ~79
Get trip spend totals, per-currency breakdowns, traveler balances, and calculated who-pays-whom settlement suggestions for a trip.
| Name | Type | Req | Description |
|---|---|---|---|
| include_settlements | boolean | – | Whether to include optimal who-pays-whom settlement suggestions. Default true. |
| trip_id | string | yes | Tineo trip ID (from trips_list). |
No output schema declared.
No examples provided.
get_trip_weather Trip Weather ~175
Get trip weather. Daily detail returns a city-grouped forecast bounded to trip dates with confidence tiers; current or hourly detail returns observed or near-term conditions for one trip city. Provide trip_id from trips_list. The Tineo itinerary already shows each day's weather and refreshes it automatically as the trip gets closer.
| Name | Type | Req | Description |
|---|---|---|---|
| city_id | string | – | Trip city ID, used for current or hourly weather. If omitted on a multi-city trip, the result lists available city IDs. |
| detail | string | – | Weather detail. Default daily. |
| hours | integer | – | Hourly forecast horizon, default 12 hours. Used only when detail is hourly. |
| max_days | integer | – | Optional forecast horizon cap in days. Default 16. |
| trip_id | string | yes | Tineo trip ID (from trips_list). |
| Name | Type | Req | Description |
|---|---|---|---|
| availableCities | array|null | – | – |
| cities | array | – | – |
| detail | string | – | – |
| outcome | string | – | – |
| tripId | string | – | – |
| type | string | – | – |
| weather | object|null | – | – |
No examples provided.
ground_transfer_booking_links Ground Transfer Booking Links ~235
Return Welcome Pickups and GetTransfer affiliate cards for a dated pickup and drop-off route. These are provider search or quote handoffs only, not live availability, prices, or confirmed bookings.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Optional ISO-style three-letter display currency. Omit to use the user's preferred currency, then the currency of the trip given by trip_id, then USD. |
| dropoff_location | string | yes | Drop-off hotel, airport, port, station, address, or place name. |
| locale | string | – | Optional locale. Defaults to en. |
| passengers | integer | – | Optional passenger count. Defaults to 1. |
| pickup_date | string | yes | Local pickup date in YYYY-MM-DD format. |
| pickup_location | string | yes | Pickup airport, hotel, port, station, address, or place name. |
| 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.
import_parse_text_preview Preview Travel Text Import ~173
Parse pasted travel confirmation text into proposed itinerary segments without saving anything. Use this before creating segments from copied email, PDF, or booking text.
| Name | Type | Req | Description |
|---|---|---|---|
| max_segments | integer | – | Maximum number of segment previews to return, from 1 to 20. Defaults to 10. |
| text | string | yes | Travel confirmation, booking, or itinerary text to parse: one booking confirmation per call, or a few days of an itinerary. A whole trip page listing many bookings can exceed the 90-second parse limi… |
| trip_id | string | – | Optional trip ID used only to verify access and give the parser trip context |
| user_hint | string | – | Optional user-provided context, such as provider name or expected segment type |
No output schema declared.
No examples provided.
journal_entry_create Save Journal Entry ~375
Save one real entry in the user's Library Journal when they ask to save or create a journal entry or travel memory. This is NOT a trip NoteSegment: never substitute a note categorized Journal or claim a journal was saved without this tool succeeding. Use the user's text or, when requested, a factual summary of retrieved trip events. Do not invent attendance, experiences or feelings from itinerary plans. Use dates supplied or established by the user; ask when the date or source is unclear. An explicit create/save request authorizes this private additive save without another confirmation; a request to draft text alone does not. Entries are private and excluded from shared travel books; linking a trip does not share the entry. Generate a new clientId UUID once per entry and reuse the exact UUID and content on retries. On success use the returned entryUrl to open the actual saved entry. On errors do not claim success or silently switch to another storage type.
| Name | Type | Req | Description |
|---|---|---|---|
| clientId | string | yes | New UUID for this entry. Reuse unchanged on a transport retry. |
| entryDate | string | yes | Journal date, YYYY-MM-DD. Resolve relative dates from the user's context; ask if unclear. |
| locationName | string|null | – | Optional user-supplied place label. |
| story | string | yes | Preserve the user's own account. When summarizing retrieved itinerary events, describe them neutrally as booked or scheduled plans, even for past dates. A booking is not evidence the user attended. N… |
| title | string | yes | A concise title from the user's text or requested factual event summary. |
| tripId | string|null | – | Optional exact accessible trip ID. Null saves without a trip. |
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.