Search / io.github.roomza-inc/roomza
Roomza Hotel Intelligence
R0· no sign-inThe room-level truth layer of hospitality. Verified scores for exact hotel rooms, not just hotels.
v1.1.0 · active · website · descriptor JSON · versions
Search / io.github.roomza-inc/roomza
R0· no sign-inThe room-level truth layer of hospitality. Verified scores for exact hotel rooms, not just hotels.
v1.1.0 · active · website · descriptor JSON · versions
{
"mcpServers": {
"roomza": {
"type": "http",
"url": "https://www.roomza.com/api/mcp"
}
}
}claude mcp add --transport http roomza https://www.roomza.com/api/mcp[mcp_servers.roomza]
url = "https://www.roomza.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"roomza": {
"type": "remote",
"url": "https://www.roomza.com/api/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"roomza": {
"type": "http",
"url": "https://www.roomza.com/api/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=roomza&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vd3d3LnJvb216YS5jb20vYXBpL21jcCJ9"
}{
"servers": {
"roomza": {
"type": "http",
"url": "https://www.roomza.com/api/mcp"
}
}
}{
"mcpServers": {
"roomza": {
"httpUrl": "https://www.roomza.com/api/mcp"
}
}
}extensions:
"roomza":
enabled: true
name: "roomza"
type: streamable_http
uri: "https://www.roomza.com/api/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations12 of 12 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 2,224 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+website +reachable +uptime-100% ~updated-64d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://www.roomza.com/api/mcp streamable-http | none | yes | 100% | 722 ms | 2025-11-25 | 2026-10-20 |
add_special_request | Add a special request to one of your bookings (e.g. extra pillows, late checkout, anniversary celebration). Requires connecting your Roomza account. |
ask_about_hotelread-only | Ask a specific question about a hotel that standard data may not answer. Uses AI with web search to find the answer. Examples: 'Does this hotel have Eiffel Tower views?', 'Is there a rooftop bar?', 'How far is it from the airport?'. Try get_hotel first; use this only when that data doesn't answer the question. |
get_hotelread-only | Get full details for a hotel including: Roomza Truth summary, score breakdown, top strengths, hotel character (type, vibes, best-for), nearby landmarks with distances, neighborhood, awards, amenities, and review highlights from the open web. Use hotel name, slug, or UUID as the identifier. This is the FIRST call when the user names a specific hotel ('Wynn Las Vegas') — no search_hotels needed; the name resolves directly. |
get_hotel_pricingread-only | Get public room rates for a hotel (the hotel's own public rate; booking on Roomza never costs more). Pass check_in and check_out dates (YYYY-MM-DD) to get nightly from-prices per room type. Without dates, returns the hotel's typical nightly from-price. No booking links; to price and book an exact room, use secure_room. |
get_hotel_roomsread-only | List rooms for a hotel with individual Roomza scores, bed type, view, and floor. Pass room_number to look up a specific room. |
get_my_preferencesread-only | Get your saved room preferences, standing requests, and loyalty accounts on Roomza. Requires connecting your Roomza account. |
get_my_tripsread-only | Look up your upcoming and past hotel bookings/trips on Roomza. Requires connecting your Roomza account. |
get_nearbyread-only | Get nearby places (restaurants, bars, attractions, parks) and upcoming events near a hotel. Optionally filter events to a travel window with start_date / end_date. |
get_recent_reviewsread-only | Get verified guest reviews for a hotel, including comments and insider tips. Pass room_number to get reviews for a specific room. |
search_hotelsread-only | DISCOVERY ONLY: search Roomza's hotel database by city, keyword, or natural language query when the user has NOT named a specific hotel. Understands hotel types (boutique, resort, luxury), vibes (romantic, trendy, quiet), traveler types (couples, families, solo), neighborhoods, and nearby landmarks. Example queries: 'boutique hotels in SoHo', 'romantic resort near the Eiffel Tower', 'pet-friendly hotel in Seattle'. Renders for the user as a full map with a multi-hotel list (so do not repeat the list in prose). NEVER use this when the user names one specific hotel (e.g. 'Wynn Las Vegas'): the map of many hotels is wrong for that. Call get_hotel with the hotel name instead, then get_hotel_rooms and show_rooms. |
secure_room | Price and lock an exact room for specific dates with Room Lock. Returns the live price, cancellation policy, and a secure booking link with the room preselected. Requires connecting your Roomza account. |
show_roomsread-only | REQUIRED whenever you present rooms. Whenever you are about to mention, recommend, or describe one or more specific rooms to the user, you MUST call this tool with those room UUIDs INSTEAD of writing the rooms in text. This is mandatory even when there is only ONE matching room — show it as a single hero card, never describe a lone room in prose. Call this BEFORE writing any prose about the rooms; the cards must appear first, then a brief summary. Pass room UUIDs (from get_hotel_rooms or search results) in ranked order, best first, 1 to 8 rooms. ALWAYS pass check_in and check_out when you know the user's dates: card prices are then for those exact dates. Without dates, cards show a typical from-price that can differ a lot from any specific dates. Each card shows photo, Roomza score, view, bed, and price. NEVER ask the user whether they want to see cards or images — just call this tool. |
Schemas: list_tools.
{
"name": "io.github.roomza-inc/roomza",
"title": "Roomza Hotel Intelligence",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://www.roomza.com/api/mcp",
"type": "streamable-http"
}
],
"version": "1.1.0",
"websiteUrl": "https://www.roomza.com",
"description": "The room-level truth layer of hospitality. Verified scores for exact hotel rooms, not just hotels."
}