# trivago (remote · mcp.trivago.com)

trivago's mcp server to find your ideal hotel and compare prices from multiple providers.

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

## Components

- remote · `mcp.trivago.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-trivago-mcp-mcp/mcp.md), [page](https://verifymcp.io/servers/com-trivago-mcp-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.trivago.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.0`

## 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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2573 tokens (~643/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability check failed: schema churn in the 15 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the trivago MCP server?

trivago is a hosted endpoint at https://mcp.trivago.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.

### Claude

```bash
claude mcp add --transport http com-trivago-mcp-mcp 'https://mcp.trivago.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-trivago-mcp-mcp": {
      "url": "https://mcp.trivago.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-trivago-mcp-mcp": {
      "type": "http",
      "url": "https://mcp.trivago.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-trivago-mcp-mcp]
url = "https://mcp.trivago.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-trivago-mcp-mcp": {
      "type": "remote",
      "url": "https://mcp.trivago.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-trivago-mcp-mcp --url 'https://mcp.trivago.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-trivago-mcp-mcp:
    url: "https://mcp.trivago.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-trivago-mcp-mcp": {
      "Transport": "http",
      "Url": "https://mcp.trivago.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-trivago-mcp-mcp -t streamable-http -u 'https://mcp.trivago.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-trivago-mcp-mcp": {
      "type": "http",
      "url": "https://mcp.trivago.com/mcp"
    }
  }
}
```

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-11-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13.

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

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7.

### 2026-10-28 (score 70, 0)

- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “language”
- [cosmetic] “trivago-accommodation-search” reworded the description of “language”
- [cosmetic] “trivago-destination-price-trends” reworded the description of “language”

### 2026-10-27 (score 70, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “trivago-accommodation-radius-search” rewrote its description, which is the text the model reads
- [security] Tool “trivago-accommodation-search” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 381 → 627
- [cosmetic] “trivago-accommodation-radius-search” added an optional parameter “price_range”
- [cosmetic] “trivago-accommodation-search” added an optional parameter “price_range”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “country”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “currency”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “language”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “latitude”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “longitude”
- [cosmetic] “trivago-accommodation-search” reworded the description of “country”
- [cosmetic] “trivago-accommodation-search” reworded the description of “currency”
- [cosmetic] “trivago-accommodation-search” reworded the description of “language”
- [cosmetic] “trivago-accommodation-search” reworded the description of “query”
- [cosmetic] “trivago-destination-price-trends” reworded the description of “country”
- [cosmetic] “trivago-destination-price-trends” reworded the description of “currency”
- [cosmetic] “trivago-destination-price-trends” reworded the description of “language”
- [cosmetic] “trivago-accommodation-radius-search” dropped the optional parameter “user_prompt”
- [cosmetic] “trivago-accommodation-search” dropped the optional parameter “user_prompt”
- [cosmetic] “trivago-destination-price-trends” dropped the optional parameter “user_prompt”

### 2026-10-24 (score 71, 0)

- [cosmetic] Tool “trivago-accommodation-radius-search” changed its title: trivago-accommodation-radius-search → Search hotels near a location on trivago
- [cosmetic] Tool “trivago-accommodation-search” changed its title: trivago-accommodation-search → Search hotels on trivago
- [cosmetic] Tool “trivago-destination-price-trends” changed its title: trivago-destination-price-trends → Forecast hotel prices on trivago

### 2026-10-23 (score 71, 0)

- [security regression] Stability: 0.03 → fail
- [security] Tool “trivago-accommodation-radius-search” rewrote its description, which is the text the model reads
- [security] Tool “trivago-accommodation-search” rewrote its description, which is the text the model reads
- [security] Tool “trivago-destination-price-trends” rewrote its description, which is the text the model reads
- [functional regression] Tool coverage: 100% → 33%
- [functional regression] “trivago-accommodation-radius-search” changed the type of “adults”: number → integer
- [functional regression] “trivago-accommodation-radius-search” changed the type of “children”: number → integer
- [functional regression] “trivago-accommodation-radius-search” changed the type of “rooms”: number → integer
- [functional regression] “trivago-accommodation-search” changed the type of “adults”: number → integer
- [functional regression] “trivago-accommodation-search” changed the type of “children”: number → integer
- [functional regression] “trivago-accommodation-search” changed the type of “rooms”: number → integer
- [functional regression] Tool “trivago-accommodation-radius-search” dropped its output schema
- [functional regression] Tool “trivago-accommodation-search” dropped its output schema
- [functional] The server no longer declares the “logging” capability
- [functional] Server version: 0.5.0 → 0.6.0
- [cosmetic] “trivago-accommodation-radius-search” added an optional parameter “user_prompt”
- [cosmetic] “trivago-accommodation-search” added an optional parameter “user_prompt”
- [cosmetic] “trivago-destination-price-trends” added an optional parameter “user_prompt”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “adults”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “arrival”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “children”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “children_ages”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “departure”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “filters”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “hotel_rating”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “review_rating”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “rooms”
- [cosmetic] “trivago-accommodation-search” reworded the description of “adults”
- [cosmetic] “trivago-accommodation-search” reworded the description of “arrival”
- [cosmetic] “trivago-accommodation-search” reworded the description of “children”
- [cosmetic] “trivago-accommodation-search” reworded the description of “children_ages”
- [cosmetic] “trivago-accommodation-search” reworded the description of “departure”
- [cosmetic] “trivago-accommodation-search” reworded the description of “filters”
- [cosmetic] “trivago-accommodation-search” reworded the description of “hotel_rating”
- [cosmetic] “trivago-accommodation-search” reworded the description of “review_rating”
- [cosmetic] “trivago-accommodation-search” reworded the description of “rooms”
- [cosmetic] “trivago-destination-price-trends” reworded the description of “end_month”
- [cosmetic] “trivago-destination-price-trends” reworded the description of “hotel_rating”
- [cosmetic] “trivago-destination-price-trends” reworded the description of “query”
- [cosmetic] “trivago-destination-price-trends” reworded the description of “start_month”
- [cosmetic] Tool “trivago-accommodation-radius-search” changed its title: trivago-accommodation-radius-search
- [cosmetic] Tool “trivago-accommodation-search” changed its title: trivago-accommodation-search
- [cosmetic] Tool “trivago-destination-price-trends” changed its title: trivago-destination-price-trends

### 2026-10-22 (score 71, +1)

- [security] Tool “trivago-accommodation-radius-search” rewrote its description, which is the text the model reads
- [security] Tool “trivago-accommodation-search” rewrote its description, which is the text the model reads
- [security] Tool “trivago-destination-price-trends” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “arrival”
- [cosmetic] “trivago-accommodation-radius-search” reworded the description of “departure”
- [cosmetic] “trivago-accommodation-search” reworded the description of “arrival”
- [cosmetic] “trivago-accommodation-search” reworded the description of “departure”

### 2026-10-21 (score 70)

First indexed and scored.

## MCP tools (3)

### `trivago-accommodation-radius-search` (~916 tokens)

Search hotels near a location on trivago

PREFERRED way to search hotels. Search live hotel and accommodation listings around coordinates — the center of a city, a neighborhood, a landmark, an address, or a venue — aggregated via trivago's metasearch of major booking sites. Returns the same, filterable results as trivago-accommodation-search. Before calling, resolve the latitude and longitude of the place the user wants to stay in yourself (e.g. Berlin → 52.52, 13.405). Use it for every city, neighborhood, or landmark search, including plain requests like "hotels in Paris". Use trivago-accommodation-search only for one specific property by name, or for a region or country too large for one point.

Input parameters:

- `adults` (integer): The number of adults.
- `arrival` (string, required): The arrival date in YYYY-MM-DD format. It must be today or in the future and MUST be before the departure date. If the arrival date is not in the future, notify the user that the arrival date is not…
- `children` (integer): The number of children.
- `children_ages` (string): Dashed separated list of children ages, e.g. 10-12-14
- `country` (string): The user's own market as an ISO alpha-2 country code: where the user lives or browses from, NOT the destination's country. It determines market-specific pricing and content. Use ONLY one of the liste…
- `currency` (string): ISO 4217 code of the currency the user wants to see prices in: the one they ask for, or else the currency of their own country, NOT the destination's unless the user asks for it. Use ONLY one of the…
- `departure` (string, required): The departure date in YYYY-MM-DD format. It MUST be after the arrival date. If the departure date is not after the arrival date, notify the user that the departure date is not after the arrival date.
- `filters` (object): The filters that you want to apply to the search. Set true or false for each filter. Multiple filters can be selected.
- `hotel_rating` (object): The hotel rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
- `language` (string): Language for translated content: the language the user writes in. Their country only picks the regional variant, never the language (e.g. a German speaker in Switzerland → DE_CH, an English speaker i…
- `latitude` (number, required): Latitude of the place the user wants to stay near: the center of the city or neighborhood, or the landmark, address, or venue. Resolve it yourself; not the user's own location.
- `longitude` (number, required): Longitude of the place the user wants to stay near: the center of the city or neighborhood, or the landmark, address, or venue. Resolve it yourself; not the user's own location.
- `price_range` (object): Optional price filter. minPrice/maxPrice are in major units of the resolved currency (e.g. 100 for $100). When both are given, minPrice must be strictly less than maxPrice. budgetType (PRICE_PER_NIGH…
- `review_rating` (object): The guest review rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
- `rooms` (integer): The number of rooms, Number of rooms must be lower than or equal to the number of adults

### `trivago-accommodation-search` (~836 tokens)

Search hotels on trivago

Search live hotel and accommodation listings by name or free text, aggregated via trivago's metasearch of major booking sites. Returns results with price, rating, amenities, and a link per property. Supports date range, guest/room configuration, and filters for star rating, guest rating, amenities, and price range. Use it ONLY when the user asks about one specific property by name, or for a region or country too large fora single point. For a city, neighborhood or landmark, call trivago-accommodation-radius-search with that place's coordinates instead: it returns far more options.

Input parameters:

- `adults` (integer): The number of adults.
- `arrival` (string, required): The arrival date in YYYY-MM-DD format. It must be today or in the future and MUST be before the departure date. If the arrival date is not in the future, notify the user that the arrival date is not…
- `children` (integer): The number of children.
- `children_ages` (string): Dashed separated list of children ages, e.g. 10-12-14
- `country` (string): The user's own market as an ISO alpha-2 country code: where the user lives or browses from, NOT the destination's country. It determines market-specific pricing and content. Use ONLY one of the liste…
- `currency` (string): ISO 4217 code of the currency the user wants to see prices in: the one they ask for, or else the currency of their own country, NOT the destination's unless the user asks for it. Use ONLY one of the…
- `departure` (string, required): The departure date in YYYY-MM-DD format. It MUST be after the arrival date. If the departure date is not after the arrival date, notify the user that the departure date is not after the arrival date.
- `filters` (object): The filters that you want to apply to the search. Set true or false for each filter. Multiple filters can be selected.
- `hotel_rating` (object): The hotel rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
- `language` (string): Language for translated content: the language the user writes in. Their country only picks the regional variant, never the language (e.g. a German speaker in Switzerland → DE_CH, an English speaker i…
- `price_range` (object): Optional price filter. minPrice/maxPrice are in major units of the resolved currency (e.g. 100 for $100). When both are given, minPrice must be strictly less than maxPrice. budgetType (PRICE_PER_NIGH…
- `query` (string, required): A specific property name, or a region or country. For a city, neighborhood, or landmark, use trivago-accommodation-radius-search instead.
- `review_rating` (object): The guest review rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
- `rooms` (integer): The number of rooms, Number of rooms must be lower than or equal to the number of adults

### `trivago-destination-price-trends` (~659 tokens)

Forecast hotel prices on trivago

Forecast monthly hotel price trends for a destination — average, minimum, and maximum nightly rate by star rating, across a date window. Use for planning questions like "when is the cheapest month to visit X" or "how do prices change through the year" — this is a forecasting tool, not a live-availability search.

Input parameters:

- `country` (string): The user's own market as an ISO alpha-2 country code: where the user lives or browses from, NOT the destination's country. It determines market-specific pricing and content. Use ONLY one of the liste…
- `currency` (string): ISO 4217 code of the currency the user wants to see prices in: the one they ask for, or else the currency of their own country, NOT the destination's unless the user asks for it. Use ONLY one of the…
- `end_month` (string): Optional end year-month in YYYY-MM format (e.g. 2026-12). Must not be before start_month. Requires start_month to also be set.
- `hotel_rating` (object): The hotel star ratings to include in the price statistics. Only 3, 4, and 5-star hotels are supported — forecasted price statistics are not available for 1 or 2-star hotels. Set true or false for eac…
- `language` (string): Language for translated content: the language the user writes in. Their country only picks the regional variant, never the language (e.g. a German speaker in Switzerland → DE_CH, an English speaker i…
- `query` (string, required): Destination query. Accepts two formats: - Free-text destination name, e.g. "Berlin", "Paris", "New York". - Coordinate pair in the format lat:<latitude>,long:<longitude>, e.g. "lat:52.52,long:13.405…
- `start_month` (string): Optional start year-month in YYYY-MM format (e.g. 2026-06). When omitted, the bridge defaults to the current month plus the next two months. It must be set when end_month is set.

Output parameters:

- `currency` (string|null): ISO 4217 currency code used to format prices in the response.
- `destinations` (array): Destinations matching the query, each with a list of monthly price statistics.
- `error` (string|null): The error if the tool failed to execute.
- `query` (string|null): The original destination query echoed back from the bridge.
- `system_message` (string|null): Presentation guidance for the LLM. Summarize the price trend across months, calling out the cheapest and most expensive months.
- `validation_errors` (array): The validation errors if the tool failed to execute.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-trivago-mcp-mcp/mcp#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 71
- 2026-10-22: 71
- 2026-10-21: 70

## Common questions

### What is the trivago MCP server?

trivago is an MCP server listed in the public MCP registry as com.trivago.mcp/mcp. trivago's mcp server to find your ideal hotel and compare prices from multiple providers. This page covers its hosted endpoint (https://mcp.trivago.com/mcp).

### Is the trivago MCP server safe to use?

trivago scores 72 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 trivago MCP server expose?

trivago exposes 3 tools: trivago-accommodation-radius-search, trivago-accommodation-search, trivago-destination-price-trends. Their descriptions and schemas cost roughly 2,411 tokens of context every time the server is loaded.

### Does the trivago MCP server require authentication?

No. We connected to trivago without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the trivago MCP server still maintained?

trivago is still listed as active in the MCP registry. We last reached this channel on 5 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 trivago MCP server?

VerifyMCP ran 14 checks on trivago, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.

## Links

- Remote endpoint: https://mcp.trivago.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-trivago-mcp-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-trivago-mcp-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-trivago-mcp-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-trivago-mcp-mcp/mcp