trivago MCP server
3 tools · Last check that passed 27 Oct 2026, 01:50 UTC
trivago's own remote MCP server gives an agent live hotel and accommodation listings from trivago's metasearch of booking sites, with prices, ratings and a link per property, and monthly price forecasts, with no API key. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 3 tools
| Tool | Counted as |
|---|---|
trivago-accommodation-radius-search | Said to only read |
trivago-accommodation-search | Said to only read |
trivago-destination-price-trends | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
7 of the last 7 checks passed
A check passes when the server lists its tools. Checked at https://mcp.trivago.com/mcp.
Recent changes
27 Oct 2026, 01:50 UTC, after a check on 26 Oct 2026, 10:13 UTC
Description rewritten on trivago-accommodation-radius-search, trivago-accommodation-search. Inputs or outputs changed on trivago-accommodation-radius-search, trivago-accommodation-search, trivago-destination-price-trends.
23 Oct 2026, 10:00 UTC, after a check on 22 Oct 2026, 09:52 UTC
Title changed on trivago-accommodation-radius-search, trivago-accommodation-search, trivago-destination-price-trends. The server's own labels changed on trivago-accommodation-radius-search, trivago-accommodation-search, trivago-destination-price-trends.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when trivago's tools change.
One email when trivago's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Prices come from other booking sites, and each result carries a link per property, so a booking happens on the site that link opens. trivago's MCP page
- trivago-destination-price-trends forecasts prices. trivago says it is not a live availability search. trivago's MCP page
- Property names, descriptions and amenity lists from booking sites come back to the agent as text, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With trivago's own settings, as its documentation describes them. Stackduke has not tested them.
- trivago says it needs no API key and no configuration, so we recommend connecting it with no trivago credentials. trivago's MCP page
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.