trivago: MCP server, CLI and agent surfaces
Yes: trivago runs a public MCP server at mcp.trivago.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: trivago-accommodation-radius-search, trivago-accommodation-search, trivago-destination-price-trends. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for trivago.com is 55, grade C, read on 5 November 2026.
Fact sheet
| Company | trivago |
|---|---|
| Domain | trivago.com |
| Category | Travel & Hospitality (Ora leaderboard category) |
| MCP server | Verified (No authentication) |
| Ora score | 55, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for trivago.com, a vendor-published score) |
| Company found through | Ora's public leaderboard |
| Last verified | 4 November 2026 |
MCP server
| Endpoint | https://mcp.trivago.com/mcp |
|---|---|
| How it was found | listed in Ora's public leaderboard |
| Transport | streamable-http |
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server | trivago Accommodation Search 0.6.0 |
| Capabilities | resources, tools |
| Tools | 3 |
| Resources | 1 |
| Prompts | 0 |
| Connected | 4 November 2026, 20:04 UTC |
| Handshake time | 831 ms over 1 attempt |
Tools listed
3 tools
- trivago-accommodation-radius-search
- trivago-accommodation-search
- trivago-destination-price-trends
Connector log
2 connections on 4 November 2026, read-only methods only
- 20:00:00Z https://mcp.trivago.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 962 ms
- 20:04:55Z https://mcp.trivago.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 831 ms
Authentication
| Auth type | No authentication |
|---|
The sign-in route, step by step
- Send the handshake to
https://mcp.trivago.com/mcpover streamable-http. Servers on the 2026-07-28 revision answerserver/discover; older servers answerinitialize. - Send
tools/list, thenresources/listandprompts/listif the capabilities name them. - Send no token. The connector sent none and the server answered, so any MCP client can read this list.
- Calling a tool is a separate step this directory never takes.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
No CLI is on record for trivago. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.
Other agent surfaces
| Surface | Result |
|---|---|
| OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. |
| WebMCP in the initial HTML | Not detected on the home page by the shared crawl. |
| MCP discovery file | Not found (the crawl got a non-200 answer). |
| A2A agent card | Not found (the crawl got a non-200 answer). |
| A2A agent card (older path) | Not found (the crawl got a non-200 answer). |
| agents.json | Not found (the crawl got a non-200 answer). |
| OAuth authorization server metadata | Not found (the crawl got a non-200 answer). |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
| Registry | Listed |
|---|---|
| Official MCP Registry | Yes: com.trivago.mcp/mcp |
| GitHub MCP Registry | No |
| awesome-remote-mcp-servers | No |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |