# HotelUse - Hotel Metasearch (remote · www.hoteluse.dev)

Compare hotel prices, room options and booking providers with live HotelUse searches.

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.hoteluse.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/leo9-hoteluse/mcp-search.md), [page](https://verifymcp.io/servers/leo9-hoteluse/mcp-search)

## Channel facts

- Endpoint: `https://www.hoteluse.dev/mcp/search`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 29/100
  - 0% 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 2851 tokens (~712/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.
  - Supports UI / widget rendering.

## Install

### How do I install the HotelUse - Hotel Metasearch MCP server?

HotelUse - Hotel Metasearch is a hosted endpoint at https://www.hoteluse.dev/mcp/search, 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 leo9-hoteluse 'https://www.hoteluse.dev/mcp/search'
```

### Cursor

```json
{
  "mcpServers": {
    "leo9-hoteluse": {
      "url": "https://www.hoteluse.dev/mcp/search"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "leo9-hoteluse": {
      "type": "http",
      "url": "https://www.hoteluse.dev/mcp/search"
    }
  }
}
```

### Codex

```toml
[mcp_servers.leo9-hoteluse]
url = "https://www.hoteluse.dev/mcp/search"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "leo9-hoteluse": {
      "type": "remote",
      "url": "https://www.hoteluse.dev/mcp/search",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add leo9-hoteluse --url 'https://www.hoteluse.dev/mcp/search' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  leo9-hoteluse:
    url: "https://www.hoteluse.dev/mcp/search"
```

### Netclaw

```json
{
  "McpServers": {
    "leo9-hoteluse": {
      "Transport": "http",
      "Url": "https://www.hoteluse.dev/mcp/search"
    }
  }
}
```

### Vellum

```bash
assistant mcp add leo9-hoteluse -t streamable-http -u 'https://www.hoteluse.dev/mcp/search'
```

### Other

```json
{
  "mcpServers": {
    "leo9-hoteluse": {
      "type": "http",
      "url": "https://www.hoteluse.dev/mcp/search"
    }
  }
}
```

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 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 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-11-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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-11-01 (score 67, +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-10-30 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 65)

First indexed and scored.

## MCP tools (3)

### `search_hotels` (~1136 tokens)

Search hotels

Search a destination or latitude/longitude (with country) for explicit hotel-local dates (including today), or date_intent: tonight. Tonight is resolved server-side in the destination time zone, never UTC. Returns hotel summaries and the lowest eligible full-stay total from Expedia, Booking, Agoda and Brek, with direct provider booking links. Search starts at a 20 km core radius, expanding to 40 km then 60 km while fewer than 50 matching static candidates exist, within the same tool call and deadline. Explicit max_distance_km disables expansion. Providers are queried once after the final candidate scope is chosen. Default order is nearest 5 km distance bands first, then greatest Brek price advantage over the cheapest other provider in each band. The advantage uses comparable full-stay totals in the same currency; missing comparisons go last within their band. Preserve the returned hotel order unless the user requests another sort. Supports star ranges or exact stars, guest-review minimum and review count, facilities, property types, distance and full-stay price budgets. Hotel and rate filters can be combined; budgets cover all nights and requested rooms, including mandatory taxes and fees. Guest scores and hotel star classifications have separate filters. no_matching_offer means prices/terms failed the requested filters, not sold out. Room types and room-level rate plans are not included. No HotelUse account or API credits required. Device detection is automatic with a desktop fallback. For a fresh search supply destination or latitude/longitude with country, and either check_in/check_out or date_intent. Search pagination accepts only quote_session_id and cursor. Omit unknown optional values; do not send null. On follow-ups that change destination, dates, guests, hotel/rate filters or sort, call search_hotels again once with the updated criteria and preserve unchanged itinerary/preferences from the latest relevant search. Do not filter or reorder an earlier result…

Input parameters:

- `check_in` (string): Hotel-local calendar date; today is allowed in the destination time zone, even after UTC midnight.
- `check_out` (string)
- `country` (string)
- `currency` (string): Requested display currency. Omission defaults to client visitor country, then locale, then USD.
- `cursor` (string): Copy the returned next_cursor exactly. Do not calculate an offset or mix new filters with a quote page.
- `date_intent` (string): A one-night stay resolved server-side in the destination or hotel time zone. Mutually exclusive with check_in/check_out.
- `destination` (string)
- `device` (string): Optional traveler device. Omission uses trusted client hints, then desktop. Room follow-ups inherit the effective search device. Mobile app rates require an approved native-app integration.
- `hotel_filters` (object)
- `latitude` (number): Search center latitude. Supply together with longitude. Explicit coordinates take precedence over city/region.
- `locale` (string): Traveler BCP 47 language, such as en-GB, independent of the destination.
- `longitude` (number): Search center longitude. Supply together with latitude.
- `page_size` (integer)
- `providers` (array)
- `quote_session_id` (string): Copy the exact quote_session_id from the result being paged.
- `rate_filters` (object)
- `region` (string)
- `residency_country` (string)
- `rooms` (array)
- `sort` (string): For nearest, closest, or sorting by distance use distance_asc (exact straight-line distance ascending). Default: nearest 5 km distance bands first (0–5, 5–10, 10–15, 15–20 km), then greatest Brek pri…
- `user_locale` (string): Optional traveler locale from client context, such as en-GB. Independent of the hotel destination.
- `user_location_country` (string): Optional traveler country from client context, used for default currency and residency. Independent of the hotel destination.

### `get_room_rates` (~785 tokens)

Room options

Get one identified or named hotel’s room options and provider prices for explicit hotel-local dates (including today), or date_intent: tonight, and occupancy. Tonight is resolved server-side in the hotel time zone. Accepts the exact HotelUse hotel_id from search_hotels, or hotel_name and destination when the ID is unavailable; destination is optional but helps disambiguation. A unique hotel match is required. Returns server-grouped room types, rate terms and full-stay provider prices in a separate Room options view. Provider price links open external booking pages; no reservation is made. Providing search_quote_session_id inherits omitted dates, occupancy, currency, language, residency and rate filters from that exact search. Explicit itinerary changes create a new quote; the search device is preserved. Supply exactly one hotel_id or hotel_name. Supply check_in/check_out, date_intent, or an existing search_quote_session_id for room quotes. All returned room groups are included in the first response; no room pagination is needed. Omit unknown optional values; do not send null. Resolve a hotel follow-up by name or position against the most recent relevant ordered search list. Copy its hotel_id exactly; if unavailable, use hotel_name and destination. Ask only if the hotel is ambiguous. For room options or current room prices call get_room_rates directly, passing search_quote_session_id from that search to preserve its stay and preferences. The first get_room_rates response includes all returned room groups and every provider minimum in room_groups. For all room options and prices, use that complete list after one call; do not paginate raw supplier offers or re-query the same stay. The raw_offer_page count describes supplier rate plans, not additional room types. Users can expand room cards locally without another price query. For undated amenities, policies or other hotel facts call get_hotel directly. Do not repeat a destination search before either hotel-specific to…

Input parameters:

- `check_in` (string): Hotel-local calendar date; today is allowed in the destination time zone, even after UTC midnight.
- `check_out` (string)
- `country` (string)
- `currency` (string): Requested display currency. Omission defaults to client visitor country, then locale, then USD.
- `date_intent` (string): A one-night stay resolved server-side in the destination or hotel time zone. Mutually exclusive with check_in/check_out.
- `destination` (string): City or region to disambiguate the hotel name.
- `device` (string): Optional traveler device. Omission uses trusted client hints, then desktop. Room follow-ups inherit the effective search device. Mobile app rates require an approved native-app integration.
- `hotel_id` (string): Exact HotelUse hotel_id from a previous result.
- `hotel_name` (string): Hotel name when no exact hotel_id is available. A unique, confident match is required. A full hotel name may be used without a destination; add the destination when ambiguous.
- `locale` (string): Traveler BCP 47 language, such as en-GB, independent of the destination.
- `providers` (array)
- `rate_filters` (object)
- `region` (string)
- `residency_country` (string)
- `rooms` (array)
- `search_quote_session_id` (string): A search result’s search_session_id. Inherits omitted stay dates, rooms, currency, language, residency and rate_filters from that search. Its device is preserved even if current client metadata chang…
- `user_locale` (string): Optional traveler locale from client context, such as en-GB. Independent of the hotel destination.
- `user_location_country` (string): Optional traveler country from client context, used for default currency and residency. Independent of the hotel destination.

### `get_hotel` (~492 tokens)

Hotel information

Get undated facts for one identified or named hotel: address, photos, descriptions, star classification, sourced guest ratings, consecutive positive review count, facilities, pet/parking policies and timezone. Optional fee amounts may be absent in the catalog. Accepts the exact HotelUse hotel_id from a previous result, or hotel_name and destination. A unique, confident match is required. A full hotel name may be used without a destination; add the destination when ambiguous. No stay dates, availability, live prices or room-level offers are included. Supply exactly one hotel_id or hotel_name. Omit unknown optional values; do not send null. Resolve a hotel follow-up by name or position against the most recent relevant ordered search list. Copy its hotel_id exactly; if unavailable, use hotel_name and destination. Ask only if the hotel is ambiguous. For room options or current room prices call get_room_rates directly, passing search_quote_session_id from that search to preserve its stay and preferences. The first get_room_rates response includes all returned room groups and every provider minimum in room_groups. For all room options and prices, use that complete list after one call; do not paginate raw supplier offers or re-query the same stay. The raw_offer_page count describes supplier rate plans, not additional room types. Users can expand room cards locally without another price query. For undated amenities, policies or other hotel facts call get_hotel directly. Do not repeat a destination search before either hotel-specific tool. Existing returned prices may be explained without refreshing when no new search or current quote is requested.

Input parameters:

- `country` (string)
- `destination` (string): City or region to disambiguate the hotel name.
- `hotel_id` (string): Exact HotelUse hotel_id from a previous result.
- `hotel_name` (string): Hotel name when no exact hotel_id is available. A unique, confident match is required. A full hotel name may be used without a destination; add the destination when ambiguous.
- `locale` (string): Traveler BCP 47 language, such as en-GB, independent of the destination.
- `region` (string)
- `user_locale` (string): Optional traveler locale from client context, such as en-GB. Independent of the hotel destination.
- `user_location_country` (string): Optional traveler country from client context, used for default currency and residency. Independent of the hotel destination.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/leo9-hoteluse/mcp-search#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 66
- 2026-10-29: 65

## Common questions

### What is the HotelUse - Hotel Metasearch MCP server?

HotelUse - Hotel Metasearch is an MCP server listed in the public MCP registry as io.github.leo9/hoteluse. Compare hotel prices, room options and booking providers with live HotelUse searches. This page covers its hosted endpoint (https://www.hoteluse.dev/mcp/search).

### Is the HotelUse - Hotel Metasearch MCP server safe to use?

HotelUse - Hotel Metasearch scores 69 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 HotelUse - Hotel Metasearch MCP server expose?

HotelUse - Hotel Metasearch exposes 3 tools: search_hotels, get_room_rates, get_hotel. Their descriptions and schemas cost roughly 2,413 tokens of context every time the server is loaded.

### Does the HotelUse - Hotel Metasearch MCP server require authentication?

No. We connected to HotelUse - Hotel Metasearch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the HotelUse - Hotel Metasearch MCP server still maintained?

HotelUse - Hotel Metasearch 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://www.hoteluse.dev/mcp/search
- Website: https://www.hoteluse.dev/docs/
- Changelog RSS feed: https://verifymcp.io/servers/leo9-hoteluse/mcp-search.xml
- Changelog JSON feed: https://verifymcp.io/servers/leo9-hoteluse/mcp-search.json
- HTML version of this page: https://verifymcp.io/servers/leo9-hoteluse/mcp-search