trivago MCP server
Checked 2026-09-08. Alive: no. Handshake: not available.
Category: commerce-retail. API and field schema.
Facts
| id | registry--com.trivago.mcp--mcp |
| name | trivago |
| registry_name | com.trivago.mcp/mcp |
| repo_url | not available |
| endpoint_url | not available |
| transport | unknown |
| alive | no |
| liveness_reason | unreachable |
| check_reachable | no |
| check_recent_commit | not verifiable |
| check_installable | not verifiable |
| handshake_status | not available |
| handshake_checked_at | not available |
| handshake_protocol_version | not available |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | not available |
| handshake_latency_ms | not available |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | commerce-retail |
| license_spdx | not available |
How to install or connect
Connect using the published unknown transport; installation metadata is available through the API.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.