Sparkling Tracks Tours
REMOTE · MCP.SPARKLINGTRACKS.COM · SCANNED SEP 25
Read-only MCP for Sparkling Tracks European tours: packages, itineraries, pricing, contacts.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4568 tokens (~304/item across 15 items; 15 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_whatsapp_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 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
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'
{
"mcpServers": {
"com-sparklingtracks-mcp": {
"url": "https://mcp.sparklingtracks.com/mcp"
}
}
} {
"servers": {
"com-sparklingtracks-mcp": {
"type": "http",
"url": "https://mcp.sparklingtracks.com/mcp"
}
}
} [mcp_servers.com-sparklingtracks-mcp] url = "https://mcp.sparklingtracks.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-sparklingtracks-mcp": {
"type": "remote",
"url": "https://mcp.sparklingtracks.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-sparklingtracks-mcp --url 'https://mcp.sparklingtracks.com/mcp' --transport streamable-http
mcp_servers:
com-sparklingtracks-mcp:
url: "https://mcp.sparklingtracks.com/mcp" {
"McpServers": {
"com-sparklingtracks-mcp": {
"Transport": "http",
"Url": "https://mcp.sparklingtracks.com/mcp"
}
}
} assistant mcp add com-sparklingtracks-mcp -t streamable-http -u 'https://mcp.sparklingtracks.com/mcp'
{
"mcpServers": {
"com-sparklingtracks-mcp": {
"type": "http",
"url": "https://mcp.sparklingtracks.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 75
- Stability: pass → 0.87 functional
- 26 Aug 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 Aug 26 0
- Stability: 0.97 → pass security
- 16 Aug 26 0
- “check_departure_live” added an optional parameter “trip_id” cosmetic
- “request_to_book” added an optional parameter “trip_id” cosmetic
- “check_departure_live” reworded the description of “title” cosmetic
- “request_to_book” reworded the description of “title” cosmetic
- “check_departure_live” made “title” optional cosmetic
5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
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 25 Sept 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=mcp.sparklingtracks.com | CN=YR2,O=Let's Encrypt,C=US | 2 Aug 2026 | 31 Oct 2026 | RSA 2048 | SHA256-RSA | 596880f288f7ee18eeef570947b0769f622 |
| SANs: mcp.sparklingtracks.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
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. | present | 19718 | 13 | Verified |
| sparklingtracks.com. | absent | 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 | 308 | 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 ~338
Search real departure dates, per-person prices in EUR and remaining availability across the whole group-trip catalogue. Unlike list_packages and get_package_details, which return "from" prices and no live stock, this returns the actual departures we can sell right now. Each departure carries a status: "available" can be sold; "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. seats_left is a real remaining-seat count where the operator publishes one and null where they do not, so absence of a number is not an absence of scarcity and must not be presented as either. Prices are per person in EUR and are the operator price. Use this for any question about when a trip runs, what a specific date costs, or whether space remains.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Country or city, matched loosely against countries, cities and trip titles. Omit to search everywhere. |
| from | string | – | Earliest departure date, ISO YYYY-MM-DD. |
| 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. |
| 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 ~240
Confirm ONE departure date with the operator right now. check_availability answers from a snapshot refreshed periodically; 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), a remaining seat count where the operator publishes one, and the time of the check. seats_left of null means the operator does not publish a number, 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. |
| 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. |
No output schema declared.
No examples provided.
get_affiliate_services ~188
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. Unsupported values fall back to EUR. Default: EUR. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Unsupported values fall back to English. Default: en. zh is Simplified Chinese. |
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_contact_info ~129
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. Unsupported values fall back to EUR. Default: EUR. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Unsupported values fall back to English. Default: en. zh is Simplified Chinese. |
No output schema declared.
No examples provided.
get_package_details ~361
Fetch the full itinerary, descriptions, included attractions, optional add-ons, pricing notes, and booking pathway for one Sparkling Tracks tour package by id. 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. 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. 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. Accepts language and currency params; city names, country names, and trip titles are translated where available, English fallback otherwise. Booking always goes through WhatsApp, email, or the contact form; this MCP does not expose a booking endpoint.
| 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. Unsupported values fall back to EUR. Default: EUR. |
| id | integer | yes | Numeric package id (e.g. from list_packages or from /trips/:id). |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Unsupported values fall back to English. Default: en. zh is Simplified Chinese. |
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.
list_destinations ~241
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. Unsupported values fall back to EUR. Default: EUR. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Unsupported values fall back to English. Default: en. zh is Simplified Chinese. |
| query | string | – | Optional case-insensitive substring to filter destinations by city or country name in English (e.g. "spain", "lisbon"). If omitted, all featured destinations are returned. |
No output schema declared.
No examples provided.
list_packages ~719
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. Use get_package_details for the full itinerary.
| 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. |
| currency | string | – | Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Unsupported values fall back to EUR. Default: EUR. |
| date_from | string | – | Start of the travel date range (ISO YYYY-MM-DD). When the destination/query names a city on a package route, only packages whose stay in that city overlaps [date_from, date_to] are returned, each ann… |
| 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 | – | Case-insensitive substring match against city or country names in the itinerary (e.g. "italy", "amsterdam", "switzerland"). Match is run against the English source names regardless of language param. |
| 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). Unsupported values fall back to English. Default: en. zh is Simplified Chinese. |
| 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. 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 ~540
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. Unsupported values fall back to EUR. Default: EUR. |
| language | string | – | Output language for translatable fields (city names, country names, trip titles, descriptions). Unsupported values fall back to English. Default: en. zh is Simplified Chinese. |
| 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. |
| 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 ~193
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. |
| 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. |
| 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 ~464
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 validated against live availability and will be rejected if the departure is closed, does not exist, or has fewer remaining seats than the party size. 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 | yes | Trip title, only when no tripId is available. |
| travellers | number | 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. |
No output schema declared.
No examples provided.
search_all_tours ~516
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 | – | Case-insensitive substring matched against the countries visited only (e.g. "portugal"). 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. Unsupported values fall back to EUR. Default: EUR. |
| 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). Unsupported values fall back to English. Default: en. zh is Simplified Chinese. |
| limit | integer | – | Maximum results to return. Clamped to the server cap of 25; values above it are ignored rather than honoured. |
| 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 | – | Case-insensitive substring matched against the tour name, the countries it visits, and the cities on its route (e.g. "portugal", "fatima", "scandinavia"). |
No output schema declared.
No examples provided.
search_destinations ~432
Find Sparkling Tracks packages that visit a given city or country. Substring, case-insensitive, matched against the English source names. 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. Unsupported values fall back to EUR. Default: EUR. |
| date_from | string | – | Start of the travel date range (ISO YYYY-MM-DD). When the destination/query names a city on a package route, only packages whose stay in that city overlaps [date_from, date_to] are returned, each ann… |
| 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). Unsupported values fall back to English. Default: en. zh is Simplified Chinese. |
| query | string | yes | City or country name in English (e.g. "Lisbon", "Switzerland", "Czech"). |
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.
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 77 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 15 tools: list_packages, get_package_details, search_destinations, search_all_tours, plan_multi_city_trip, and 10 more. Their descriptions and schemas cost roughly 4,568 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 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.