mcpbeat Sign in

HotelUse - Hotel Metasearch MCP Server

answering

HotelUse - Hotel Metasearch is answering right now. Last checked moments ago. It exposes 3 tools.

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

Uptime history 4 days of history
4 days agonow
100.0%
Uptime 24h
92 of 92 checks
3
Tools
read from the server
723 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check HotelUse - Hotel Metasearch every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add hoteluse --transport http https://www.hoteluse.dev/mcp/search
Settings → Connectors → Add custom connector, then paste this address
https://www.hoteluse.dev/mcp/search
~/.codex/config.toml
[mcp_servers.hoteluse]
url = "https://www.hoteluse.dev/mcp/search"
.cursor/mcp.json
{
  "mcpServers": {
    "hoteluse": {
      "url": "https://www.hoteluse.dev/mcp/search"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "hoteluse": {
      "type": "http",
      "url": "https://www.hoteluse.dev/mcp/search"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

hotel
get_hotel
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.
hotels
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 page and present it as a new destination search: that page may omit matching hotels. For nearest, closest, or distance order use sort: distance_asc. The geographic_scope.radius_km value is the search radius, never any hotel’s distance. Per-hotel distance_meters is measured from the destination center. For cheapest hotels use sort: stay_total_asc. For "4-star only" use hotel_filters.star_ratings: [4]; for "4- and 5-star only" use [4,5], not star_rating_min: 4 (which includes 4.5). Never broaden explicit criteria silently. Omit providers unless the user requests specific providers; the server handles occupancy support. A successful partial response is the result of this search: show the returned prices and do not automatically repeat the search to fill missing provider quotes. An explicit user refresh calls the tool again. Pagination with quote_session_id/cursor is only for unchanged criteria.
room
get_room_rates
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 tool. Existing returned prices may be explained without refreshing when no new search or current quote is requested.

Endpoints

URLTransportStateLatencyChecked
https://www.hoteluse.dev/mcp/search streamable-http answering 751 ms 0 min ago

Alternatives to HotelUse - Hotel Metasearch

same job, measured the same way
Booking.com Hotel Search (Live Prices)
by flightpowers

Live Booking.com hotel prices, plus per-country pricing for rate-parity monitoring.

4 tools answering
VICATOO
by vicatoo

Hotel search in Arabic or English with live rates and real room videos. Book on vicatoo.com.

answering
MyService Hotels
by myservice

AI hotel search and booking: millions of properties, 85,000+ cities, live rates.

10 tools answering
Kompare travel search
by kompare

Live prices on package holidays and niche trips from Danish travel agencies, with booking links.

4 tools answering
Working Proxy Sites
by workingproxysites

Research proxy providers, compare published prices, and discover provider MCP integrations.

20 tools answering
searchit model catalog
by searchit-agent

AI model prices, providers, EU hosting and benchmarks: find, compare, save and watch offers.

answering
Brek - Hotel Wholesale Booking
by leo9

Search hotels, compare room offers and public or masked wholesale rates, then continue on Brek.

3 tools answering
Hotel & Vacation Rental MCP - live prices & reviews across Booking, Airbnb, Vrbo & Google Hotels
by stayingapi

Search hotels & rentals: live prices & reviews across Booking.com, Airbnb, Vrbo & Google Hotels.

answering

HotelUse - Hotel Metasearch — questions

Answers built from our own checks of this server.

What can HotelUse - Hotel Metasearch do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_hotel, get_room_rates, search_hotels. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is HotelUse - Hotel Metasearch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 723 ms. The bar chart above shows every period we have measured.
How do I connect HotelUse - Hotel Metasearch?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does HotelUse - Hotel Metasearch need an API key?
No. HotelUse - Hotel Metasearch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is HotelUse - Hotel Metasearch?
It answers our handshake in 723 ms on average, which is faster than 12% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.