# HasData Google Hotels (remote · mcp.hasdata.com)

Google Hotels search: rates, ratings, amenities and what each booking site charges, as JSON.

- Trust score: 86/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- remote · `mcp.hasdata.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-hasdata-google-hotels/mcp.md), [page](https://verifymcp.io/servers/com-hasdata-google-hotels/mcp)
- npm · `@hasdata/google-hotels-mcp`: 49/100, [markdown](https://verifymcp.io/servers/com-hasdata-google-hotels/hasdata-google-hotels-mcp.md), [page](https://verifymcp.io/servers/com-hasdata-google-hotels/hasdata-google-hotels-mcp)
- pypi · `hasdata-google-hotels-mcp`: 34/100, [markdown](https://verifymcp.io/servers/com-hasdata-google-hotels/hasdata-google-hotels-mcp-2.md), [page](https://verifymcp.io/servers/com-hasdata-google-hotels/hasdata-google-hotels-mcp-2)

## Channel facts

- Endpoint: `https://mcp.hasdata.com/mcp?apis=google_travel_hotels`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.2`

## 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-10-16.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/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 1461 tokens (~182/item across 8 items; 1 tools + 7 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.

## Install

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

HasData Google Hotels is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=google_travel_hotels, 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-hasdata-google-hotels 'https://mcp.hasdata.com/mcp?apis=google_travel_hotels'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hasdata-google-hotels": {
      "url": "https://mcp.hasdata.com/mcp?apis=google_travel_hotels"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hasdata-google-hotels": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=google_travel_hotels"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hasdata-google-hotels]
url = "https://mcp.hasdata.com/mcp?apis=google_travel_hotels"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hasdata-google-hotels": {
      "type": "remote",
      "url": "https://mcp.hasdata.com/mcp?apis=google_travel_hotels",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hasdata-google-hotels --url 'https://mcp.hasdata.com/mcp?apis=google_travel_hotels' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hasdata-google-hotels:
    url: "https://mcp.hasdata.com/mcp?apis=google_travel_hotels"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hasdata-google-hotels": {
      "Transport": "http",
      "Url": "https://mcp.hasdata.com/mcp?apis=google_travel_hotels"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hasdata-google-hotels -t streamable-http -u 'https://mcp.hasdata.com/mcp?apis=google_travel_hotels'
```

### Other

```json
{
  "mcpServers": {
    "com-hasdata-google-hotels": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=google_travel_hotels"
    }
  }
}
```

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-10-16 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 17. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-07 (score 82, +43)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.07
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: good
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] New resource “google_travel_rating”
- [functional] New resource “google_travel_propertyType__”
- [functional] New resource “google_travel_hotels_sortBy”
- [functional] New resource “google_travel_hl”
- [functional] New resource “google_travel_gl”
- [functional] New resource “google_travel_currency”
- [functional] New resource “google_travel_amenity__”

### 2026-09-28 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 39)

First indexed and scored.

## MCP tools (1)

### `hasdata_google_travel_hotels_getGoogleHotels` (~959 tokens)

google_travel_hotels: GET /

Get Google Hotels Results

Searches Google Hotels for hotels and vacation rentals with check-in/check-out dates, guest mix (adults, children with ages), localization (country, language, currency), and advanced filters: price range, property types, amenities, minimum rating, brands, hotel class, free cancellation, special offers, eco-certified, vacation rentals only, bedrooms, bathrooms, and sort order (lowest price, highest rating, most reviewed). Returns per-property name, description, link, GPS coordinates, check-in/out times, rate per night and total rate, price comparisons across sources, hotel class, overall rating, reviews, location rating, images, amenities, nearby places, deals, eco-certification, and pagination tokens. Use for travel research agents, hotel rate monitoring, OTA dashboards, and competitive analysis of accommodations across markets.

Input parameters:

- `adults` (number): Number of adult guests (1-6).
- `amenity__` (array): List of amenities to filter by (e.g., `hotelFreeWifi,hotelPool`). Values prefixed `hotel*` apply when searching hotels (the default mode). Values prefixed `rental*` apply when `vacationRentals=true`…
- `bathrooms` (number): Minimum number of bathrooms (vacation rentals only).
- `bedrooms` (number): Minimum number of bedrooms (vacation rentals only).
- `brands` (string): Comma-separated list of brand IDs to filter by. Brand IDs are returned in the response under `brands` for the same query.
- `checkInDate` (string, required): The check-in date in 'yyyy-MM-dd' format.
- `checkOutDate` (string, required): The check-out date in 'yyyy-MM-dd' format.
- `children` (number): Number of child guests (1-5). Total guests (adults + children) cannot exceed 6.
- `childrenAges` (string): Comma-separated list of children ages (e.g., `5,8,12`). Must match the number of children.
- `currency` (string): Parameter defines the currency of the returned prices Provide one exact documented value (71 allowed), e.g. `ALL`, `DZD`.
- `ecoCertified` (boolean): Show only eco-certified properties.
- `freeCancellation` (boolean): Show only properties offering free cancellation.
- `gl` (string): The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`.
- `hl` (string): The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`.
- `hotelClass` (string): Comma-separated list of hotel star classes to include (e.g., `2,3,4,5`).
- `maxPrice` (number): Maximum price per night, in the selected currency.
- `minPrice` (number): Minimum price per night, in the selected currency.
- `nextPageToken` (string): Token to fetch the next page of hotel results. Returned in the `pagination` field of a previous response.
- `propertyToken` (string): Token used to retrieve details for a specific property. Returned in each property in the results.
- `propertyType__` (array): List of property types to filter by (e.g., `hotelResort,hotelMotel`). Values prefixed `hotel*` apply when searching hotels (the default mode). Values prefixed `rental*` apply when `vacationRentals=t…
- `q` (string, required): The search query for Google Hotels (e.g., a city, neighborhood, or hotel name).
- `rating` (string): Filter by minimum overall guest rating. Options:   - `threePointFivePlus` — 3.5 stars or higher   - `fourPlus` — 4.0 stars or higher   - `fourPointFivePlus` — 4.5 stars or higher
- `sortBy` (string): Sort hotel results. Options:   - `lowestPrice` — lowest price   - `highestRating` — highest rating   - `mostReviewed` — most reviewed
- `specialOffers` (boolean): Show only properties with special offers.
- `vacationRentals` (boolean): Search vacation rentals instead of hotels.

## Diagnostics

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

## Score history

- 2026-10-16: 86
- 2026-10-15: 85
- 2026-10-14: 85
- 2026-10-13: 85
- 2026-10-12: 84
- 2026-10-10: 83
- 2026-10-07: 82
- 2026-10-04: 39
- 2026-10-03: 39
- 2026-10-02: 39
- 2026-10-01: 39
- 2026-09-30: 39
- 2026-09-29: 39
- 2026-09-28: 39
- 2026-09-27: 39
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 39
- 2026-09-23: 39
- 2026-09-22: 39

## Common questions

### What is the HasData Google Hotels MCP server?

HasData Google Hotels is an MCP server listed in the public MCP registry as com.hasdata/google-hotels. Google Hotels search: rates, ratings, amenities and what each booking site charges, as JSON. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=google_travel_hotels).

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

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

HasData Google Hotels exposes 1 tool: hasdata_google_travel_hotels_getGoogleHotels. Their descriptions and schemas cost roughly 959 tokens of context every time the server is loaded.

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

Yes. HasData Google Hotels asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

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

HasData Google Hotels is still listed as active in the MCP registry. We last reached this channel on 16 October 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.hasdata.com/mcp?apis=google_travel_hotels
- Authorisation metadata: https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/HasData/google-hotels-mcp
- Website: https://hasdata.com/apis/google-hotels-api
- Changelog RSS feed: https://verifymcp.io/servers/com-hasdata-google-hotels/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hasdata-google-hotels/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hasdata-google-hotels/mcp