OKstays MCP server

• Registry namecom.okstays/okstaysverified in the MCP registry

The registry name sits under okstays.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-11-03
• Tools8
• Server calls itselfokstays
• Server version4.2.0
• Protocol version2025-06-18

On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 362 ms.

• Its tools do every use case we checked: filter stays by quiet rooms and comfy beds; shortlist hotels for a trip by travel style.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer333 ms
• Space in an agent's context≈ 2,873 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_hotels

  Use this when the user wants hotels in a destination (e.g. 'quiet hotels in Bangkok under $150'), or asks about a hotel by name (hotel_name). Returns up to 10 hotels per page, ranked by the OKstays Comfort Score (0-10 from what guests…

• get_hotel

  Use this when the user asks about one hotel: why it scores as it does, or whether it's quiet, clean or good for sleep or work. Returns the Comfort Score breakdown, what the scores rest on, the five must-haves, its strengths and complaints…

• list_cities

  Use this when the user asks which destinations OKstays covers, or before planning a trip through a country. Returns every destination we score with its country, slug and number of hotels; pass country to list one country only. Read-only…

• get_filters

  Use this to look up the comfort signals and travel styles that search_hotels accepts, when the user's wish doesn't map clearly to one. Returns every filter (id, name, description, category, whether it's a must-have) and every travel…

• compare_hotels

  Use this when the user is choosing between 2-4 specific hotels. Returns each hotel's Comfort Score breakdown, price, strengths and complaints, the signals where they differ most, and a verdict: best comfort, cheapest, best value. Hotel…

• find_similar_hotels

  Use this when the user likes a hotel but wants alternatives, e.g. 'like this one but cheaper' (cheaper_only). Returns hotels in the same destination with the closest comfort profile, none with repeated complaints about cleanliness, beds…

• get_city_overview

  Use this when the user is still choosing a destination or an area to stay in. Returns how many hotels we score, the average Comfort Score, median price, where its hotels beat and trail the average hotel, the best neighbourhoods with their…

• plan_trip

  Use this when the user plans a trip with several stops. Returns hotels for each stay in travel order (e.g. Lisbon 4 nights, Porto 3, Madrid 5): the best match for each stop by the OKstays Comfort Score (or the travel style's score)…