Travel Trends is an MCP server with 8 tools an agent can call, among them assess_trip, country_briefing, country_tourism_profile. It answers at https://travel-trends.mmatinca.eu/mcp/v1 over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
European tourism & travel-disruption MCP: trip risk, live events, Eurostat panels, RO county data.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 Inputs: destinations, date_from, date_to, lang, audience |
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 Inputs: country |
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 Inputs: code |
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, d Inputs: trip_id, since |
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_u Inputs: trip_id, since |
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 Inputs: status, country, domain, min_severity |
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 Inputs: destinations, date_from, date_to, label, lang, audience |
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. Rec Inputs: trip_id, since, audience |
Every block below points at https://travel-trends.mmatinca.eu/mcp/v1. Pick your client and copy.
claude mcp add --transport http travel-trends-mcp https://travel-trends.mmatinca.eu/mcp/v1
{
"mcpServers": {
"travel-trends-mcp": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://travel-trends.mmatinca.eu/mcp/v1"]
}
}
}{
"mcpServers": {
"travel-trends-mcp": {
"url": "https://travel-trends.mmatinca.eu/mcp/v1"
}
}
}{
"servers": {
"travel-trends-mcp": {
"type": "http",
"url": "https://travel-trends.mmatinca.eu/mcp/v1"
}
}
}{
"context_servers": {
"travel-trends-mcp": {
"url": "https://travel-trends.mmatinca.eu/mcp/v1"
}
}
}{
"mcpServers": {
"travel-trends-mcp": {
"serverUrl": "https://travel-trends.mmatinca.eu/mcp/v1"
}
}
}{
"mcpServers": {
"travel-trends-mcp": {
"url": "https://travel-trends.mmatinca.eu/mcp/v1"
}
}
}name: travel-trends-mcp
version: 0.0.1
schema: v1
mcpServers:
- name: travel-trends-mcp
type: streamable-http
url: https://travel-trends.mmatinca.eu/mcp/v1{
"mcpServers": {
"travel-trends-mcp": {
"httpUrl": "https://travel-trends.mmatinca.eu/mcp/v1"
}
}
}{
"mcpServers": {
"travel-trends-mcp": {
"type": "http",
"url": "https://travel-trends.mmatinca.eu/mcp/v1"
}
}
}{
"mcpServers": {
"travel-trends-mcp": {
"url": "https://travel-trends.mmatinca.eu/mcp/v1"
}
}
}goose://extension?url=https%3A%2F%2Ftravel-trends.mmatinca.eu%2Fmcp%2Fv1&type=streamable_http&id=travel-trends-mcp&name=travel-trends-mcp
It answered our last check on 18 October 2026 in 348 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by mmatinca.eu and served from travel-trends.mmatinca.eu, the vendor's own domain: https://travel-trends.mmatinca.eu/mcp/v1.
8, as returned by the server's own tools/list on 31 August 2026: assess_trip, country_briefing, country_tourism_profile, explain_silence, get_trip_updates_since, list_events, watch_trip, whats_changed.
It answered our last check on 18 October 2026 in 348 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://travel-trends.mmatinca.eu/mcp/v1. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: eu.mmatinca. Endpoint host: travel-trends.mmatinca.eu. ARD identifier: urn:air:eu.mmatinca:mcp:travel-trends-mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.