# Google Hotels MCP (remote · mcp.wondel.ai)

Live Google Hotels search: properties with rates and ratings, plus photos and reviews.

- Trust score: 57/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.wondel.ai`: 57/100 (this document), [markdown](https://verifymcp.io/servers/ai-wondel-google-hotels/google-hotels-mcp.md), [page](https://verifymcp.io/servers/ai-wondel-google-hotels/google-hotels-mcp)

## Channel facts

- Endpoint: `https://mcp.wondel.ai/google-hotels/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 49/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1450 tokens (~483/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Google Hotels MCP server?

Google Hotels MCP is a hosted endpoint at https://mcp.wondel.ai/google-hotels/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 ai-wondel-google-hotels 'https://mcp.wondel.ai/google-hotels/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-wondel-google-hotels": {
      "url": "https://mcp.wondel.ai/google-hotels/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-wondel-google-hotels": {
      "type": "http",
      "url": "https://mcp.wondel.ai/google-hotels/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-wondel-google-hotels]
url = "https://mcp.wondel.ai/google-hotels/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-wondel-google-hotels --url 'https://mcp.wondel.ai/google-hotels/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-wondel-google-hotels:
    url: "https://mcp.wondel.ai/google-hotels/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-wondel-google-hotels": {
      "Transport": "http",
      "Url": "https://mcp.wondel.ai/google-hotels/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-wondel-google-hotels -t streamable-http -u 'https://mcp.wondel.ai/google-hotels/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-wondel-google-hotels": {
      "type": "http",
      "url": "https://mcp.wondel.ai/google-hotels/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-05 (score 57, +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-11-03 (score 56, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 55)

First indexed and scored.

## MCP tools (3)

### `google_hotels_search` (~939 tokens)

Search Google Hotels (SerpAPI)

Search Google Hotels live via SerpAPI. Returns properties (hotels and, with vacation_rentals, rentals) with names, prices/rates, overall ratings, review counts, amenities, images and location, plus the brands/property_types/amenities filter ids you can feed back in. Requires q (a destination, area or hotel name), check_in_date and check_out_date (YYYY-MM-DD). Every property in the results carries a `property_token`: pass it back here (keeping the same check_in_date/check_out_date) to get that one property's full details, or hand it to google_hotels_photos and google_hotels_reviews. Paginate with next_page_token. Prices are in `currency` (default USD). Result shape: { source, fetchedAt, query, search_metadata, search_parameters, search_information, brands, ads, properties: [...], serpapi_pagination } — the list key is `properties` (ads are separate). Each property: { type, name, property_token, link, gps_coordinates, rate_per_night: { lowest, extracted_lowest }, total_rate, prices: [{ source, num_guests, rate_per_night }], overall_rating, reviews, hotel_class (label), extracted_hotel_class (number), amenities, images: [{ thumbnail, original_image }], nearby_places, description }. With property_token the single property's fields come back at the top level instead of `properties`.

Input parameters:

- `adults` (integer): Number of adults. Default 2.
- `amenities` (string): Filter by amenities: comma-separated amenity ids (see amenities in a prior response).
- `bathrooms` (integer): Minimum number of bathrooms. Vacation rentals only. Default 0.
- `bedrooms` (integer): Minimum number of bedrooms. Vacation rentals only. Default 0.
- `brands` (string): Filter by hotel brand: comma-separated brand ids (see brands in a prior response). Not applicable to vacation rentals.
- `check_in_date` (string, required): Check-in date, YYYY-MM-DD.
- `check_out_date` (string, required): Check-out date, YYYY-MM-DD.
- `children` (integer): Number of children. Default 0.
- `children_ages` (string): Ages of the children as comma-separated values, e.g. '5,8'. Each age 1-17; the count should match `children`.
- `currency` (string): Currency of returned prices (ISO code, e.g. 'USD', 'EUR'). Default USD.
- `eco_certified` (boolean): Only show eco-certified properties. Default false.
- `free_cancellation` (boolean): Only show properties offering free cancellation. Default false.
- `gl` (string): Country code for the search, e.g. 'us', 'uk', 'de'.
- `hl` (string): Language code, e.g. 'en', 'es', 'pt-br'.
- `hotel_class` (string): Filter by hotel class (stars): comma-separated values from 2 to 5, e.g. '4,5'.
- `max_price` (integer): Maximum price per night in the selected currency.
- `min_price` (integer): Minimum price per night in the selected currency.
- `next_page_token` (string): Token from a prior response to fetch the next page of results.
- `no_cache` (boolean): Force a fresh SerpAPI fetch and bypass this server's result cache. Default false.
- `property_token` (string): Token for a single property from a prior search result; returns that property's full details. Still pass check_in_date and check_out_date.
- `property_types` (string): Filter by property type: comma-separated type ids (see property_types in a prior response).
- `q` (string, required): Search query: a destination, area, or hotel name (e.g. 'Bali resorts', 'hotels in Paris').
- `rating` (integer): Minimum overall rating: 7 = 3.5+, 8 = 4.0+, 9 = 4.5+.
- `sort_by` (integer): Sort order: 3 = lowest price, 8 = highest rating, 13 = most reviewed. Omit for SerpAPI's default relevance ranking.
- `special_offers` (boolean): Only show properties with special offers. Default false.
- `vacation_rentals` (boolean): Search vacation rentals instead of hotels. Default false (hotels).
- `zero_trace` (boolean): Enterprise-only ZeroTrace mode: don't store search params/metadata on SerpAPI. Default false.

Output parameters:

- `ads`
- `brands`
- `fetchedAt` (string)
- `properties` (array)
- `query` (object)
- `search_information`
- `search_metadata`
- `search_parameters`
- `serpapi_pagination`
- `source` (string)

### `google_hotels_photos` (~147 tokens)

Get Google Hotels Property Photos (SerpAPI)

Fetch the full set of photos for a single Google Hotels property via SerpAPI. Requires a `property_token` taken from a google_hotels_search result. Paginate with next_page_token.

Input parameters:

- `next_page_token` (string): Token from a prior response to fetch the next page of photos.
- `no_cache` (boolean): Force a fresh SerpAPI fetch and bypass this server's result cache. Default false.
- `property_token` (string, required): Property token from a google_hotels_search result identifying the property whose photos to fetch.
- `zero_trace` (boolean): Enterprise-only ZeroTrace mode: don't store search params/metadata on SerpAPI. Default false.

### `google_hotels_reviews` (~259 tokens)

Get Google Hotels Property Reviews (SerpAPI)

Fetch reviews for a single Google Hotels property via SerpAPI. Requires a `property_token` taken from a google_hotels_search result. Filter by category_token or source_number, order with sort_by, and paginate with next_page_token.

Input parameters:

- `category_token` (string): Token to filter reviews by a category/topic (from a prior reviews response).
- `hl` (string): Language code, e.g. 'en', 'es', 'pt-br'.
- `next_page_token` (string): Token from a prior response to fetch the next page of reviews.
- `no_cache` (boolean): Force a fresh SerpAPI fetch and bypass this server's result cache. Default false.
- `property_token` (string, required): Property token from a google_hotels_search result identifying the property whose reviews to fetch.
- `sort_by` (integer): Sort order: 1 = most helpful, 2 = most recent, 3 = highest rating, 4 = lowest rating.
- `source_number` (integer): Filter reviews by a specific review source (provider) number, as listed in a prior response.
- `zero_trace` (boolean): Enterprise-only ZeroTrace mode: don't store search params/metadata on SerpAPI. Default false.

## Diagnostics

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

## Score history

- 2026-11-05: 57
- 2026-11-04: 56
- 2026-11-03: 56
- 2026-11-02: 55

## Common questions

### What is the Google Hotels MCP server?

Google Hotels MCP is listed in the public MCP registry as ai.wondel/google-hotels. Live Google Hotels search: properties with rates and ratings, plus photos and reviews. This page covers its hosted endpoint (https://mcp.wondel.ai/google-hotels/mcp).

### Is the Google Hotels MCP server safe to use?

Google Hotels MCP scores 57 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 Google Hotels MCP server expose?

Google Hotels MCP exposes 3 tools: google_hotels_search, google_hotels_photos, google_hotels_reviews. Their descriptions and schemas cost roughly 1,345 tokens of context every time the server is loaded.

### Does the Google Hotels MCP server require authentication?

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

### Is the Google Hotels MCP server still maintained?

Google Hotels MCP 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.

## Links

- Remote endpoint: https://mcp.wondel.ai/google-hotels/mcp
- Website: https://mcps.wondel.ai/servers/google-hotels/
- Changelog RSS feed: https://verifymcp.io/servers/ai-wondel-google-hotels/google-hotels-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-wondel-google-hotels/google-hotels-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-wondel-google-hotels/google-hotels-mcp