# eu.mmatinca/travel-trends-mcp (remote · travel-trends.mmatinca.eu)

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

- Trust score: 72/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `travel-trends.mmatinca.eu`: 72/100 (this document), [markdown](https://verifymcp.io/servers/eu-mmatinca-travel-trends-mcp/mcp-v1.md), [page](https://verifymcp.io/servers/eu-mmatinca-travel-trends-mcp/mcp-v1)

## Channel facts

- Endpoint: `https://travel-trends.mmatinca.eu/mcp/v1`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3431 tokens (~381/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http eu-mmatinca-travel-trends-mcp https://travel-trends.mmatinca.eu/mcp/v1
```

### Codex

```toml
[mcp_servers.eu-mmatinca-travel-trends-mcp]
url = "https://travel-trends.mmatinca.eu/mcp/v1"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-mmatinca-travel-trends-mcp": {
      "type": "remote",
      "url": "https://travel-trends.mmatinca.eu/mcp/v1",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add eu-mmatinca-travel-trends-mcp --url https://travel-trends.mmatinca.eu/mcp/v1 --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  eu-mmatinca-travel-trends-mcp:
    url: "https://travel-trends.mmatinca.eu/mcp/v1"
```

### Other

```json
{
  "mcpServers": {
    "eu-mmatinca-travel-trends-mcp": {
      "type": "http",
      "url": "https://travel-trends.mmatinca.eu/mcp/v1"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 70, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 64, +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.

### 2026-07-27 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (8)

### `assess_trip` (~1251 tokens)

Decision support for ONE trip: "should I care?", answered honestly.

    Give the destinations and the travel window (date_from/date_to,
    YYYY-MM-DD). Destinations are the EU-27 ISO2 codes (Greece = "EL") PLUS the
    non-EU27 countries we actively monitor: Norway ("NO", rail via Entur, live),
    the United Kingdom ("UK" or "GB", transit via TfL, live), and Switzerland
    ("CH", rail via SBB — key-pending, so it is reported as a declared blind
    spot until the feed is keyed, never a false all-clear). A code we do not
    monitor is rejected with {"error": "unknown_country"} rather than silently
    all-cleared. Returns a Decision-Support answer, not raw data:
      * travel_status: NORMAL | MINOR_DISRUPTION | MAJOR_DISRUPTION;
      * actionable_lines: per-event DECISION-IMPACT guidance — what the
        disruption means for THIS trip and what to do (e.g. "affects regional
        trains, not airports -> take a road airport transfer, leave ~30 min
        earlier"), or a clearly-labelled "nothing material" line when calm;
      * confidence: a LABELLED model output (coverage/corroboration/recency/
        blind-spots blend, not a probability) — read its caveats;
      * sources_checked: proof of what was monitored (sources_ok, blind spots);
      * events + caveats.
    Sub-floor noise (a deep, far-field seismic blip) is omitted; calm is a
    monitoring result for the window, never an invented forecast. Invalid
    inputs return an explicit {"error": ...}; nothing is fabricated.

    Top-level MCP-facing structure (additive; existing fields preserved):
      * presentation: a three-section block — affects_your_trip[] (each
        item with verified_sources[] as display-ready names, source_count,
        corroborated flag (≥2 distinct sources), an honest for_you line
        bound to destinations+dates only, report_url, first_detected_at,
        last_verified_at); doesnt_affect_your_trip (the proof-of-work
        pile — shown[] of {headline, reason_exclu…

Input parameters:

- `audience`
- `date_from` (string, required)
- `date_to` (string, required)
- `destinations` (array, required)
- `lang`

### `watch_trip` (~831 tokens)

Watch a trip over time — the continuity primitive a chat cannot match.

    Persists the trip as a MONITORED OBJECT and returns its initial
    assessment plus a stable trip_id. Idempotent on identity: re-watching the
    same destinations+window refreshes the same trip rather than duplicating
    it. Thereafter each pipeline run re-evaluates the trip and appends an
    update ONLY when something materially changes (a new/cleared event, a
    severity/status shift, or a travel_status change) — never on a calm tick.
    Args: destinations — EU-27 ISO2 codes (Greece = "EL") plus the non-EU27
    countries we monitor: Norway "NO" (Entur, live), United Kingdom "UK"/"GB"
    (TfL, live), Switzerland "CH" (SBB, key-pending → declared blind spot until
    keyed); date_from/date_to (YYYY-MM-DD); optional label. An unmonitored code
    is rejected with {"error": "unknown_country"} rather than a false all-clear.
    Returns {trip_id, assessment, created_at}; invalid inputs return an explicit
    {"error": ...}.

    Destinations also accept natural input: IATA airport codes (e.g. 'TSR',
    'AMS', 'ZRH') and major city names (e.g. 'Timișoara', 'Amsterdam',
    'Zürich', 'London'), resolved deterministically to a monitored country
    code. The initial assessment includes a 'resolved' list
    ([{input, country, kind}]) disclosing how each token was mapped
    (e.g. 'TSR -> RO via iata-airport'). A token that resolves to a country we
    do not monitor is rejected with {'error': 'unknown_country'}; a token we
    cannot resolve at all is rejected with
    {'error': 'unknown_destination', 'tokens': [...]} — we reject not guess.

    Pass `lang` (e.g. "de", "ro", "pl"; default English) to localise the
    initial assessment into the traveller's language: the returned
    assessment carries the same `localized` block as assess_trip (honest
    reassurance, AI-translated-and-LABELLED source text, and the localized
    caveats + blind_spots that are never dropped). Localization ne…

Input parameters:

- `audience`
- `date_from` (string, required)
- `date_to` (string, required)
- `destinations` (array, required)
- `label`
- `lang`
- `notify_webhook_url`

### `whats_changed` (~429 tokens)

What changed for a watched trip since last time — ONLY the delta.

    The continuity payload a memoryless chat cannot produce: recomputes the
    trip's current assessment and diffs it against the checkpoint at/just-
    before `since` (or the last evaluation when `since` is omitted). Returns
    {material, summary, added_events, removed_events, changed_events,
    previous_travel_status, travel_status, confidence_from, confidence_to}.
    `summary` is a plain-language line ('Since your last check: rail strike
    CONFIRMED (was: announced); a road closure cleared; confidence 63->71%').
    A non-material tick returns material=False with a clearly-flagged 'No
    material change' summary — never invented churn. `since` is an optional
    ISO-8601 timestamp (e.g. the user's last-seen time). Id is regex-validated
    (^trip-[a-z0-9-]+$); unknown id -> {"error": "not_found"}, malformed id ->
    {"error": "invalid_trip_id"}.

    The response also forwards the MCP-facing moat blocks from the current
    assessment so the LLM consumer has full context alongside the delta:
    presentation (affects_your_trip / doesnt_affect_your_trip / next_steps),
    track_record_ref (90-day counts + URL), and suggested_next_call
    (factual continuity hint). Forwarded in both material=True and
    material=False branches; absent if upstream did not compute them
    (legacy code paths) — never fabricated.

    `audience` (optional: tmc | hotel | ota | tour_operator) attaches the
    same `persona` block as assess_trip/watch_trip to the change alert —
    audience-tagged actions for the events currently affecting the trip, so
    the alert itself carries the operational next step. Unknown audience ->
    honest error listing valid_audiences.

Input parameters:

- `audience`
- `since`
- `trip_id` (string, required)

### `explain_silence` (~229 tokens)

Why you heard nothing — the SILENCE AUDIT for a calm watched trip.

    Answers 'why didn't I hear from you?' honestly, which a stateless model
    cannot: {recheck_count, last_checked} (we WERE monitoring),
    {suppressed:[{what, domain, country, score, floor, reason}]} (what we saw
    for your destinations and dropped below the disclosed relevance floor —
    e.g. a deep quake at modelled felt-intensity 3.39 < floor 4.0),
    {confidence_during_window}, and {blind_spots:[{domain, country, note}]} —
    domains/countries we do NOT monitor live, so silence there is NOT a
    guarantee (e.g. aviation-IT blind spot => silence does not cover flights).
    `since` optionally scopes the recheck window. Id is regex-validated;
    unknown -> {"error": "not_found"}, malformed -> {"error": "invalid_trip_id"}.

Input parameters:

- `since`
- `trip_id` (string, required)

### `get_trip_updates_since` (~154 tokens)

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 to push only
    what is new since the user last looked. An empty `since` returns the whole
    log. Id is regex-validated (^trip-[a-z0-9-]+$); unknown id ->
    {"error": "not_found"}, malformed id -> {"error": "invalid_trip_id"}.

Input parameters:

- `since` (string, required)
- `trip_id` (string, required)

### `country_briefing` (~150 tokens)

Get today's published daily briefing, pre-formatted for end users.

    Returns the same payload as the underlying daily briefing artifact:
    headline counts, one plain-language headline per active event,
    monitoring coverage (sources_ok / blind_spots_count), backtest trust
    figures, and a caveats list. Always relay caveats alongside numbers.
    Optional ``country`` (EU-27 ISO2 alpha-2, Greece = "EL") narrows the
    events list only — headline_counts / monitoring / trust stay
    EU-27-wide, as flagged in the returned note. Missing artifact returns
    ``{"error": "unavailable"}``.

Input parameters:

- `country`

### `list_events` (~157 tokens)

List detected travel-disruption events for EU-27 tourism.

    Events are deterministic, rule-based detections over published live
    snapshots and monthly indicators — thresholds are disclosed in each
    event record; nothing is model-generated here. Filters: status (e.g.
    "active"/"resolved"), country (EU-27 ISO2, Greece = "EL"), domain
    (e.g. "weather", "aviation"), min_severity on the ordered scale
    info < watch < warning < severe. Returns {count, events, filters};
    on missing index returns {"error": "unavailable"}.

Input parameters:

- `country`
- `domain`
- `min_severity`
- `status`

### `country_tourism_profile` (~189 tokens)

Tourism profile for one EU-27 country — a decade of Eurostat data.

    Pure projection of the published artifacts (countries/<code>.json +
    competitiveness.json): yearly nights/arrivals totals with YoY, average
    stay, seasonality (peak month and peak-to-mean ratio, formula disclosed),
    domestic vs foreign visitor share, recovery vs 2019, growth vs the EU
    average, and computed competitiveness insights (each labeled with its
    basis). Every number is computed from the same public dataset the site
    serves — nothing narrated, nothing estimated; links carry the citable
    page + raw JSON. `code` is EU-27 ISO2 (Greece = "EL"). Unknown country ->
    {"error": "unknown_country"}; missing artifact -> {"error": "unavailable"}.

Input parameters:

- `code` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/eu-mmatinca-travel-trends-mcp/mcp-v1#diagnostics

## Score history

- 2026-08-04: 72
- 2026-08-03: 71
- 2026-08-02: 71
- 2026-08-01: 70
- 2026-07-31: 70
- 2026-07-30: 65
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 63

## Links

- Remote endpoint: https://travel-trends.mmatinca.eu/mcp/v1
- Website: https://travel-trends.mmatinca.eu/
- Changelog RSS feed: https://verifymcp.io/servers/eu-mmatinca-travel-trends-mcp/mcp-v1/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/eu-mmatinca-travel-trends-mcp/mcp-v1/changelog.json
- HTML version of this page: https://verifymcp.io/servers/eu-mmatinca-travel-trends-mcp/mcp-v1