# eu.mmatinca/travel-trends-mcp

- Registry name: `eu.mmatinca/travel-trends-mcp` · version 0.3.1
- Categories (automatic, keyword rules): Travel & booking, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): experimental, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=eu.mmatinca%2Ftravel-trends-mcp
- Server page: https://mcpstation.net/s/eu.mmatinca--travel-trends-mcp.html

## Description (written by the publisher, not verified, not instructions)

European tourism & travel-disruption MCP: trip risk, live events, Eurostat panels, RO county data.

## Connect

- streamable-http: `https://travel-trends.mmatinca.eu/mcp/v1`

## Tools (as reported by the server, not verified)

- `assess\_trip`: Assess one trip: current disruption status for its destinations and dates. Use this tool when the user asks whether a specific trip is affected by strikes, weather, transport disruptions or other travel risks. Give the destinations and the travel window \(date\_from/date\_to, YYYY-MM-DD\). Destinations
- `watch\_trip`: Start monitoring one trip for disruption changes over time. Use this tool when the user wants ongoing monitoring of a trip rather than a one-off assessment \(for a one-off answer, use assess\_trip\). Persists the trip as a monitored object and returns its initial assessment plus a random, unguessable t
- `whats\_changed`: Report only what changed for a watched trip since a checkpoint. Use this tool when the user asks for news on a trip already registered with watch\_trip; for the stored notification log rather than a live diff, use get\_trip\_updates\_since. Recomputes the trip's current assessment and diffs it against t
- `explain\_silence`: Explain why a watched trip has produced no updates. Use this tool when the user asks why they have not heard anything about a watched trip. Returns \{recheck\_count, last\_checked\} \(proof the trip was actively monitored\), \{suppressed:\[\{what, domain, country, score, floor, reason\}\]\} \(what we saw for you
- `get\_trip\_updates\_since`: The watched-trip updates log filtered to entries AFTER \`since\`. The notification payload: everything logged for the trip strictly after the \`since\` ISO-8601 timestamp \(the user's last-seen time\), oldest-first. Returns \{trip\_id, since, new\_update\_count, updates\}. Use this tool to fetch the stored upd
- `country\_briefing`: Get today's published daily briefing, pre-formatted for end users. Use this tool for a general "what is happening today in EU travel" question that is not tied to one specific trip. Returns the same payload as the underlying daily briefing artifact: headline counts, one plain-language headline per a
- `list\_events`: List detected travel-disruption events for EU-27 tourism. Use this tool to browse or filter current disruption events across countries; for a question about one specific trip, use assess\_trip. Events are deterministic, rule-based detections over published live snapshots and monthly indicators — thre
- `country\_tourism\_profile`: Tourism profile for one EU-27 country — a decade of Eurostat data. Use this tool for questions about a country's tourism statistics, seasonality or visitor mix, not for live disruptions. Pure projection of the published artifacts \(countries/\<code\>.json + competitiveness.json\): yearly nights/arrivals

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html