Sparkling Tracks Tours
REMOTE · MCP.SPARKLINGTRACKS.COM
Read-only MCP for Sparkling Tracks European tours: packages, itineraries, pricing, contacts.
Available components
Last scanned (20 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8439 tokens (~444/item across 19 items; 19 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 0
- Server version: 1.1.0 → 1.2.0 functional
- 12 Nov 26 +1
- Stability: fail → pass ▲ security
- 11 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_trips” rewrote its description, which is the text the model reads security
- Tool “get_package_details” rewrote its description, which is the text the model reads security
- Tool “get_trip_price” rewrote its description, which is the text the model reads security
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Oct 26 0
- Stability: pass → fail ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_availability” rewrote its description, which is the text the model reads security
- Tool “check_departure_live” rewrote its description, which is the text the model reads security
- Tool “get_package_details” rewrote its description, which is the text the model reads security
- Tool “list_packages” rewrote its description, which is the text the model reads security
- Tool “request_to_book” rewrote its description, which is the text the model reads security
- Tool “search_all_tours” rewrote its description, which is the text the model reads security
- Tool “search_destinations” rewrote its description, which is the text the model reads security
- Schema quality: 304 → 439 ▼ functional
- “request_to_book” changed the type of “travellers”: number → integer ▼ functional
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “find_trips” functional
- New tool “get_city” functional
- New tool “get_terms” functional
- New tool “get_trip_price” functional
- “check_availability” reworded the description of “destination” cosmetic
- “check_availability” reworded the description of “from” cosmetic
- “check_availability” reworded the description of “limit” cosmetic
- “check_departure_live” reworded the description of “title” cosmetic
- “check_departure_live” reworded the description of “trip_id” cosmetic
- “get_affiliate_services” reworded the description of “currency” cosmetic
- “get_affiliate_services” reworded the description of “language” cosmetic
- “get_contact_info” reworded the description of “currency” cosmetic
- “get_contact_info” reworded the description of “language” cosmetic
- “get_package_details” reworded the description of “currency” cosmetic
- “get_package_details” reworded the description of “id” cosmetic
- “get_package_details” reworded the description of “language” cosmetic
- “list_destinations” reworded the description of “currency” cosmetic
- “list_destinations” reworded the description of “language” cosmetic
- “list_destinations” reworded the description of “query” cosmetic
- “list_packages” reworded the description of “badge” cosmetic
- “list_packages” reworded the description of “currency” cosmetic
- “list_packages” reworded the description of “date_from” cosmetic
- “list_packages” reworded the description of “destination” cosmetic
- “list_packages” reworded the description of “language” cosmetic
- “list_packages” reworded the description of “traveler_count” cosmetic
- “plan_multi_city_trip” reworded the description of “currency” cosmetic
- “plan_multi_city_trip” reworded the description of “language” cosmetic
- “plan_multi_city_trip” reworded the description of “month” cosmetic
- “request_custom_itinerary” reworded the description of “month” cosmetic
- “request_custom_itinerary” reworded the description of “party_size” cosmetic
- “request_to_book” reworded the description of “title” cosmetic
- “request_to_book” reworded the description of “trip_id” cosmetic
- “search_all_tours” reworded the description of “country” cosmetic
- “search_all_tours” reworded the description of “currency” cosmetic
- “search_all_tours” reworded the description of “language” cosmetic
- “search_all_tours” reworded the description of “limit” cosmetic
- “search_all_tours” reworded the description of “query” cosmetic
- “search_destinations” reworded the description of “currency” cosmetic
- “search_destinations” reworded the description of “date_from” cosmetic
- “search_destinations” reworded the description of “language” cosmetic
- “search_destinations” reworded the description of “query” cosmetic
- “request_to_book” made “title” optional cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Aug 26 0
- Stability: 0.97 → pass security
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://mcp.sparklingtracks.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sparklingtracks.com | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e465c4d5edb155f80e47505fbf68d964 |
| SANs: sparklingtracks.com, *.sparklingtracks.com | ||||||
| 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 insecure
Validation of mcp.sparklingtracks.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| sparklingtracks.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self), payment=(self), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.sparklingtracks.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.sparklingtracks.com/mcp | HTTPS enforced | 301 | https://mcp.sparklingtracks.com/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 →
check_availability ~444
Search departure dates, per-person prices in EUR and the status of each departure across the whole group-trip catalogue. Unlike list_packages and get_package_details, which return "from" prices, this returns dated departures with the price of each. It is STORED data, read from the operators at the time given in asOf, and not a live check: a departure listed as available was available at that time. Departures that have already left are never returned, and neither are trips that have no page on the website. Each departure carries a status: "available" can be offered; "on-request" must be confirmed with the operator before it is promised to a traveller and must be described as "on request"; "closed" cannot be sold and is hidden unless include_unsellable is set. seatsLeft is always null, because no seat count is published from stored data: do not say how many places remain. Prices are per person in EUR and are the operator price. Use this for any question about when a trip runs or what a specific date costs, then confirm the chosen date with check_departure_live before it is promised.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Country or city, in English or in any of our languages, matched loosely against countries, cities and trip titles. A name we know is read as its English name, which is repeated under asked. Omit to s… |
| from | string | – | Earliest departure date, ISO YYYY-MM-DD. A date before today is read as today. |
| include_unsellable | boolean | – | Include closed departures. Default false. Only set this to explain why a date is unavailable, never to offer one. |
| limit | number | – | Maximum trips to return, 1 to 50. Default 20. A number outside 1 to 50 is brought inside it, and the limit used is repeated under asked. |
| max_days | number | – | Maximum trip length in days. |
| max_price | number | – | Maximum per-person price in EUR. |
| min_days | number | – | Minimum trip length in days. |
| to | string | – | Latest departure date, ISO YYYY-MM-DD. |
No output schema declared.
No examples provided.
check_departure_live ~294
Confirm ONE departure date with the operator right now. check_availability answers from stored data; this asks the operator live and is what should be trusted before a date is promised to a traveller. Returns status (available, on-request, closed or unknown) and the time of the check. seatsAvailable is a number only where the operator publishes a real count of places left. Null means no real count is published for that departure, NOT that no seats remain: do not present null as scarcity or as a sell-out. Some operators require an agent session and cannot be checked from a public request; those return an explanatory error rather than a status that could be mistaken for a refusal. Use before request_to_book.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Departure date, ISO YYYY-MM-DD. |
| title | string | – | Trip title, only when no tripId is available. If it names more than one trip the call is refused and the candidates are returned with their ids. One of trip_id and title must be given. |
| trip_id | number | – | The tripId returned by check_availability. PREFER THIS: titles are not unique, and two different trips can share one on the same date at very different prices. The trip number (1024). The same digits… |
No output schema declared.
No examples provided.
find_trips ~920
START HERE. One search over every trip on the website: where, when, how long, how many travellers, which room, what budget. Put ONLY the place or the trip name in query: a city, a country, a trip name in any word order and any of our languages, a trip number, or a trip link pasted whole. Put the dates in date_from and date_to and never in query. Returns at most 8 trips a page, lowest price first, with a trip whose name matches the words ahead of the rest; total_matches says how many there are, and next_offset gives the next page. Each trip has its link, its length, its route, whether it has tiers, the lowest price per person among the departures that match (from), and its next 3 matching departures, each with the day it ends, its status and its price per tier in the room asked for. A departure matches when it LEAVES between date_from and date_to; use return_by when the traveller must be home by a date. For a trip with dates "fixed" the prices are the published prices of those departures when the operator was last read (as_of): exact for the date, stored and not live. A trip with dates "flexible" is one of our own self-paced trips: it can start on any date, or on any date within its season where start_window gives one, and its figure is a starting price. left_out counts the trips that matched the words and were ruled out by the dates or the budget, and nothing_found gives the nearest real departures when nothing matches. Follow with get_package_details for what a trip includes, get_trip_price for one date and one party, and request_to_book to ask for a place. Nothing is held or charged by searching.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| date_from | string | – | Earliest day the trip may LEAVE, ISO YYYY-MM-DD. For "in November 2026" give 2026-11-01 here and 2026-11-30 in date_to. A date before today is read as today. |
| date_to | string | – | Latest day the trip may LEAVE, ISO YYYY-MM-DD. For "November or December" give the last day of December. |
| days_max | number | – | Longest trip, in days. |
| days_min | number | – | Shortest trip, in days. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
| limit | number | – | How many trips to return, 1 to 8. Default 8. A number outside 1 to 8 is brought inside it, and the limit used is repeated under asked. |
| max_price_eur | number | – | Budget per person in EUR, land only, in the room and tier asked for. Only departures at or under it are returned. |
| offset | number | – | How many trips to pass over, for the next page. Ask the same question again with offset set to next_offset from the last reply. Default 0. next_offset is null on the last page. |
| query | string | – | The place or the trip, and nothing else: "Italy", "Rome", "Great Iberian", "2767", or a pasted trip link. A place may be written in any of our languages ("Wien" is read as Vienna). Omit it to search… |
| return_by | string | – | The trip must have ended on or before this day, ISO YYYY-MM-DD. Use it only when the traveller must be home by a date. |
| room | string | – | Room type the prices are per person in. Default: double. shared is a solo traveller sharing with others of the same gender. |
| tier | string | – | Only this tier. Omit to get every tier a trip is sold in; "from" and max_price_eur are then read at Economy. Luxury is priced individually and has no figure. |
| travellers | integer | – | Party size, 1 to 40. When given, each price also has the total for the party. |
No output schema declared.
No examples provided.
get_affiliate_services ~190
List the affiliate booking services available on sparklingtracks.com (flights, hotels, cars, activities, eSIMs). Each entry is a whitelabel widget hosted on a site page; direct API booking is not supported through this MCP. The AI should route the user to the returned URL to complete the search and booking. Service titles and descriptions are currently English-only regardless of language param.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter. If omitted, all categories are returned. |
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
No output schema declared.
No examples provided.
get_careers ~55
List open jobs at Sparkling Tracks (roles, locations, responsibilities, requirements, compensation notes) and how to apply. Read-only: applying is always by email with the subject "Job: <ROLE_ID>". English only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_city ~267
What we hold about ONE city: the text of its guide with its highlights, its history and a few facts, the weather month by month, its photo and its position. Give the city by name. Only the parts we hold are in the reply, and not_held names the parts we hold nothing for (out of guide, history, climate, photo, position): do not fill a part that is not held from anywhere else. Every text is returned exactly as we publish it, so quote it and do not restate it. climate.months has twelve entries, January first, each with the average daily high and low in degrees Celsius, the rain in millimetres and a one-word condition; climate.source is the credit that must be shown with it. photo.url is our own photo of that city. trips.count is the number of trips find_trips finds for the city: use find_trips for the trips themselves, with their dates and prices. No hotel price is given here. A name we hold nothing for, and a country, is refused with city_not_found.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | The name of one city, in English or in any language we publish (e.g. "Vienna", "Wien"). Letter case and accents do not matter. |
No output schema declared.
No examples provided.
get_contact_info ~131
Get Sparkling Tracks contact paths for tour-package quotes: WhatsApp number, email, contact form URL, business hours, languages spoken. Tour packages always require a human-in-the-loop quote.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
No output schema declared.
No examples provided.
get_package_details ~781
Fetch the full itinerary, descriptions, included attractions, optional add-ons, pricing notes, and booking pathway for one Sparkling Tracks tour package by id: any trip that find_trips, list_packages or search_all_tours returns. The response includes city_date_windows: for each city on the route, the next upcoming departures with the real calendar dates the traveller is in that city (departure, arrive, leave, season) and the 1-based tour day the stay starts on; self-paced packages are flagged date_flexible instead, and one that runs in one season gives its start dates in departures.start_window. Guided group coach tours also return a family block: the edition descriptor for this package (days, whether the coach is reserved for English speakers rather than shared with other language groups, the city it ends in, and whether it loops back to its start city) plus the sibling editions of the same physical coach route, each with a one-line difference and its own page. departures lists the next departures that can still be requested, each with its price per person by tier and by room. When departures.source is "live" the operator was asked as this was answered (departures.checked_at) and a date it has closed is left out; when it is "snapshot" the statuses are the stored ones and departures.live_check says why, so do not promise a date. The prices are always the stored ones, read at departures.as_of. Use get_trip_price for one date and one party. whats_included says what is and is not included, once per tier (flights are never included: every price is land-only). itinerary is the day-by-day plan where the package has one, and an empty list where it is described stop by stop under highlights. Each entry of optional_addons carries included_from_tier: at that tier and every tier above it the add-on is part of the package at no charge, and null means it is a paid extra at every tier. payment.deposit is the share of the price that holds a reservation; use get_terms for the paym…
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| id | integer | yes | The trip, as find_trips, list_packages or search_all_tours return it. The trip number (1024). The same digits as text, the start of its page address (1024-from-london-to-budapest) and a link to its p… |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
No output schema declared.
No examples provided.
get_reviews ~32
Get Sparkling Tracks customer reviews and the aggregate rating (out of 5), for citing social proof. English only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_terms ~277
Read the published Sparkling Tracks Terms and Conditions: deposit, payment, cancellation charges, changes, travel documents, liability, the Package Travel Directive rights of EU customers, and the rest. Called with no section it returns the list of sections with their numbers, the deposit share and the link to the Terms page. Called with section set to a number (for example 7 or 7.1) or a plain word (for example "cancellation", "deposit", "visa") it returns that section in full, in the words of the Terms page. Use it for any question about what a traveller pays and when, what they are charged if they cancel, or what is refunded. Quote a charge or a deadline from the returned text and never from memory: the Terms page and the written invoice are what bind. Available in en, de, nl, fr and es. English is the source of truth, and a language outside that list is refused: ask in one of the five.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of the terms. Default: en. English is the source of truth. |
| section | string | – | A section number ("7", "7.1"), or a plain word for the topic ("cancellation", "deposit", "refund", "visa", "liability"). Omit to list the sections. |
No output schema declared.
No examples provided.
get_trip_price ~624
The price of ONE trip for one departure date, one room type and one party. Give trip_id and, for a trip that leaves on set dates, date (YYYY-MM-DD, one of the departures listed by get_package_details). Returns the price per person for each tier the trip is sold in, and the total for the party when travellers is given, with the status of that departure. The figure is the published price for that date, tier and room when the operator was last read (as_of): it is exact for the date, it is stored and not live, and a person confirms the final price. The STATUS of the date is checked with the operator as this is answered: source is "live" with checked_at when it answered, and a date it has closed is refused with departure_closed and the nearest open dates. When source is "snapshot", live_check says the operator was not heard: do not promise the date. room is double (two sharing, the default), single, triple or shared (a solo traveller sharing with others of the same gender); a room that is not sold on that date is answered in words, with the rooms that are. Luxury is planned and priced individually and has no figure. A trip sold at one price per room type has no tiers. Our own self-paced trips have no fixed departures: they return the figure their page shows for every start date, as a starting price, and one that runs in one season refuses a date outside it with out_of_season, its window and its next start. If the date is not a departure, the nearest real departures are returned in place of a guess. deposit_share is the deposit stated in the Terms; use get_terms for the clause. Nothing is held or charged by asking.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| date | string | – | Departure date, ISO YYYY-MM-DD. Required for a trip that leaves on set dates. Omit it to get the list of departures back. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
| room | string | – | Room type the price is per person in. Default: double. |
| tier | string | – | Only this tier. Omit to get every tier the trip is sold in. |
| travellers | integer | – | Party size, 1 to 40. When given, the total for the party is returned as well. |
| trip_id | number | yes | The trip, as find_trips, list_packages, search_all_tours or check_availability return it. The trip number (1024). The same digits as text, the start of its page address (1024-from-london-to-budapest)… |
No output schema declared.
No examples provided.
list_destinations ~256
List the featured European destination cities Sparkling Tracks publishes a guide page for (at /destinations/:slug). Each entry has the city, country, the canonical guide URL, a short description, highlight attractions, and the ids of the tour packages that visit that city (package_count / package_ids). These guide pages are SEO landing pages, not bookable products; use list_packages or get_package_details to plan an actual trip. Optional query filters by city or country substring. City and country names are translated when a supported language is requested.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
| query | string | – | Optional filter by city or country name, in English or in any of our languages (e.g. "spain", "lisbon", "Wien"). Letter case and accents do not matter. If omitted, all featured destinations are retur… |
No output schema declared.
No examples provided.
list_packages ~878
To answer a traveller, use find_trips first: it searches every trip on the site by place, name, number or link and returns dated prices. List Sparkling Tracks tour packages with optional filters. Returns a compact summary (id, title, route, starting per-person price in EUR for the land-only option, the with-flights total when available (price_eur_with_flights), whether flights are optional (flights_optional), an approximate price in the requested currency, duration, badges, URL). The default starting price is land-only (without flights); customers can add round-trip flights. Optional date_from/date_to (ISO YYYY-MM-DD) filter by the real departure calendar: combined with a destination city they keep only packages whose stay in that city overlaps the range (annotated with city_date_windows); dates alone keep only packages that fit entirely inside the range. Accepts optional language and currency params; city names, country names, and trip titles are translated when a supported locale is requested. Tour packages are quote-based: prices are starting per-person prices, final pricing depends on party size, dates, and customisations. Every response carries price_basis, which states the exactness of every price field it returns (these are "from" prices, never per-date quotes) and the booking path. A package on a coach route that is also sold in other editions carries an editions count; get_package_details returns those editions in its family block. Where a package is sold in tiers, its summary carries tiers: the starting price of Economy and of Premium, and Luxury marked quote_only because it is priced individually. price_eur is always the Economy figure. A package sold at one price per room type has no tiers key. Use get_package_details for the full itinerary and for what each tier includes.
| Name | Type | Req | Description |
|---|---|---|---|
| badge | string | – | Filter to packages carrying a marketing badge. Accepted values include: bestseller, new, most_romantic, young_travelers, couples_choice, selling_fast. Partial substring match. No package carries a ba… |
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| date_from | string | – | Start of the travel date range (ISO YYYY-MM-DD). A date before today is read as today. When the destination/query names a city on a package route, only packages whose stay in that city overlaps [date… |
| date_to | string | – | End of the travel date range (ISO YYYY-MM-DD, inclusive). Must be on or after date_from. When omitted: with a city query and date_from it defaults to date_from (a single day); without a city the rang… |
| destination | string | – | A city or country on the route, in English or in any of our languages (e.g. "italy", "amsterdam", "Wien"). Letter case and accents do not matter. A name we know is read as its English name, which is… |
| duration_days | integer | – | Filter to packages with exactly this many days (parsed from the duration string, e.g. "12D/11N" is 12 days). |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
| max_price_eur | number | – | Filter to packages with starting price at or below this EUR amount. Custom-quote packages (price not yet set) are always included. |
| traveler_count | integer | – | Number of travellers in the party, 1 or more. Does not affect filtering; included in the response note so the AI can mention quote variability. |
No output schema declared.
No examples provided.
plan_multi_city_trip ~550
Assemble a whole journey through several named cities and return the best options. Unlike list_packages and search_all_tours, which look for a single published trip, this builds one journey out of guided sections that connect in a hub city on real departure dates, plus the days Sparkling Tracks arranges itself around and between them. Give the cities in the order the traveller wants to see them; optionally a month (YYYY-MM) and the number of nights they have. Each journey returns its guided sections with their real departure and end dates, the days that are the traveller's own with the city and the nights, and the total length. THERE IS NO PRICE FOR A JOURNEY AND NO PRICE FOR A SECTION: the only figure returned is whole_tour_from_eur, the starting price of the ENTIRE published trip that a section is taken from, and it must never be added to another, divided by its nights, or presented as the cost of the journey or of the section. A person quotes each section by hand and one figure for the whole journey comes back with the reply to the enquiry, so tell the traveller plainly that a quote will follow. Every journey is returned even when we cannot price it yet; needs_quote says so and it is never a reason to hide an option. A city we cannot sell at all is named in unknown_cities and left out of every journey, so the journeys returned never contain it.
| Name | Type | Req | Description |
|---|---|---|---|
| cities | array | yes | Cities in the order the traveller wants to visit them, English or local spelling (e.g. ["Paris", "Prague", "Rome"]). The first is where the journey starts and the last is where it ends; the ones in b… |
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
| month | string | – | Month of travel, ISO YYYY-MM (e.g. "2026-09"). Only journeys starting in that month are returned. Omit when the traveller has not chosen one. A month that has gone is refused. |
| nights | integer | – | Total nights the traveller has. Journeys longer than this are not returned at all, and nights left over once the guided sections are counted become days we arrange for them. |
No output schema declared.
No examples provided.
request_custom_itinerary ~206
Record a REQUEST for a custom multi-city itinerary and send it to the Sparkling Tracks team. Use when the customer has picked an option from plan_multi_city_trip or one of the self-paced alternatives and has given their name and email. This does NOT book anything. Returns a reference the traveller can quote.
| Name | Type | Req | Description |
|---|---|---|---|
| cities | array | yes | Cities the traveller wants to visit. |
| string | yes | Contact email address. | |
| month | string | – | ISO month YYYY-MM. A month that has gone is refused. |
| name | string | yes | Lead traveller name. |
| nights | integer | – | Total nights for the journey. |
| notes | string | – | Anything else the traveller wants us to know. |
| party_size | integer | – | Number of travellers, 1 or more. |
| phone | string | – | Contact phone, with country code. |
| preferred_option_index | integer | – | Which option they preferred: 0 for the first, 1 for the second, etc. |
No output schema declared.
No examples provided.
request_to_book ~519
Record a traveller REQUEST to book and send it to the Sparkling Tracks team. This does NOT book, hold or charge anything, and no confirmation exists until a human replies: none of the operators we work with can be booked programmatically. Call it only after check_availability has returned a specific trip and departure date that the traveller has chosen, and only once they have given a name and email. The request is checked against the stored departure list and is rejected if the departure has already left, is closed or does not exist. The team then confirms it with the operator. Returns a reference the traveller can quote. NEVER ask for or pass a passport number, a full date of birth, or any card or bank detail; those are collected securely by a human later. Tell the traveller plainly that nothing is held or charged yet.
| Name | Type | Req | Description |
|---|---|---|---|
| accessibility | string | – | Accessibility or mobility requirements. |
| ages | string | – | Coarse age bands only, for trips with an age policy, for example "2 adults, 1 child 9". Never a full date of birth. |
| departure_city | string | – | Where the traveller would fly from, for a flight quote. |
| departure_date | string | yes | ISO YYYY-MM-DD, must be one of that trip's departures. |
| dietary | string | – | Dietary requirements. |
| string | yes | Contact email address. | |
| name | string | yes | Lead traveller name. |
| nationality | string | – | Drives visa requirement. Not an identity document. |
| needs_flights | boolean | – | Whether they want flights quoted alongside the trip. |
| notes | string | – | Anything else the traveller wants us to know. |
| occupancy | string | – | Twin, Single, Triple, Twin Share, or cabin class for a cruise. |
| phone | string | – | Contact phone, with country code. |
| rooms | string | – | Room split, for example "1 twin + 1 single". |
| title | string | – | Trip title, only when no tripId is available. One of trip_id and title must be given. |
| travellers | integer | yes | Party size, 1 to 40. |
| trip_id | number | – | The tripId returned by check_availability. PREFER THIS: it names exactly one trip. A title can name several, and the request is refused rather than guessing which. The trip number (1024). The same di… |
No output schema declared.
No examples provided.
search_all_tours ~587
To answer a traveller, use find_trips first: it searches every trip on the site by place, name, number or link and returns dated prices. Search the FULL Sparkling Tracks coach-tour catalogue, not just the packages that have a dedicated page. list_packages and search_destinations cover the curated packages; this tool covers every tour on sale, including the hundreds that are sold on enquiry only, so "do you have anything in Portugal" gets a real answer instead of the curated slice. Each result gives the tour name, duration in days, the countries it visits, the Sparkling Tracks starting price in EUR (a "from" price for the cheapest departure of the year, land-only, lowest hotel tier), the next departure date or a dates-on-request flag, a one-click WhatsApp enquiry link with the tour name filled in, and the trip page URL when the tour has one (site_trip). Results are capped; when total_matches exceeds the cap, narrow the filters rather than asking for more. Every tour here is quote-based: a human confirms the final price after an enquiry, and no booking happens through this MCP.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Matched against the countries visited only (e.g. "portugal"), in English or in any of our languages. Use this instead of query when the user named a country rather than a theme. |
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| days_max | integer | – | Only tours lasting at most this many days. |
| days_min | integer | – | Only tours lasting at least this many days. |
| has_departures | boolean | – | true keeps only tours with a fixed departure still ahead on the published calendar; false keeps only the dates-on-request tours. Omit for both. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
| limit | integer | – | Maximum results to return, 1 to 25. A number outside 1 to 25 is brought inside it, and the limit used is repeated under asked. |
| max_price_eur | number | – | Only tours whose starting price is at or below this EUR amount. |
| min_price_eur | number | – | Only tours whose starting price is at or above this EUR amount. |
| query | string | – | Text matched against the tour name, the countries it visits, and the cities on its route (e.g. "portugal", "fatima", "scandinavia"). Letter case and accents do not matter, and a city or country writt… |
No output schema declared.
No examples provided.
search_destinations ~506
To answer a traveller, use find_trips first: it searches every trip on the site by place, name, number or link and returns dated prices. Find Sparkling Tracks packages that visit a given city or country, named in English or in any of our languages. Optional date_from/date_to (ISO YYYY-MM-DD) filter by the real departure calendar: with a city query, only packages whose stay in that city overlaps the range are returned, each annotated with city_date_windows giving the departure, arrive and leave dates and the tour day; with a country query, only packages that fit entirely inside the range. Returned package summaries are translated to the requested language; currency follows the currency param. Every response carries price_basis, which states the exactness of every price field it returns (these are "from" prices, never per-date quotes) and the booking path.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused. |
| date_from | string | – | Start of the travel date range (ISO YYYY-MM-DD). A date before today is read as today. When the destination/query names a city on a package route, only packages whose stay in that city overlaps [date… |
| date_to | string | – | End of the travel date range (ISO YYYY-MM-DD, inclusive). Must be on or after date_from. When omitted: with a city query and date_from it defaults to date_from (a single day); without a city the rang… |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused. |
| query | string | yes | City or country name, in English or in any of our languages (e.g. "Lisbon", "Switzerland", "Czech", "Wien"). Letter case and accents do not matter. A name we know is read as its English name, which i… |
No output schema declared.
No examples provided.
send_whatsapp_message ~120
Send a WhatsApp message to a traveller from the Sparkling Tracks team. Use when the user has provided their phone number and wants details, a reminder, or confirmation sent to WhatsApp. The message is forwarded to the team and sent from the business WhatsApp number.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Why this message is being sent, for the team. |
| message | string | yes | The exact message to send. Keep it short and friendly. |
| phone | string | yes | Phone number with country code, e.g. +919876543210. |
No output schema declared.
No examples provided.
How do I install the Sparkling Tracks Tours MCP server?
Sparkling Tracks Tours is a hosted endpoint at https://mcp.sparklingtracks.com/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 · mcp.sparklingtracks.com
claude mcp add --transport http com-sparklingtracks-mcp 'https://mcp.sparklingtracks.com/mcp'
What is the Sparkling Tracks Tours MCP server?
Sparkling Tracks Tours is an MCP server listed in the public MCP registry as com.sparklingtracks/mcp. Read-only MCP for Sparkling Tracks European tours: packages, itineraries, pricing, contacts. This page covers its hosted endpoint (https://mcp.sparklingtracks.com/mcp).
Is the Sparkling Tracks Tours MCP server safe to use?
Sparkling Tracks Tours 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 Sparkling Tracks Tours MCP server expose?
Sparkling Tracks Tours exposes 19 tools: find_trips, list_packages, get_package_details, search_destinations, search_all_tours, and 14 more. Their descriptions and schemas cost roughly 7,637 tokens of context every time the server is loaded.
Does the Sparkling Tracks Tours MCP server require authentication?
No. We connected to Sparkling Tracks Tours without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sparkling Tracks Tours MCP server still maintained?
Sparkling Tracks Tours 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 Sparkling Tracks Tours MCP server?
VerifyMCP ran 13 checks on Sparkling Tracks Tours, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.