_ registry / mcp http-sse · checked 13h ago

roomza

https://www.roomza.com

Registry code: ce179e797339f7b3

api record

Roomza is the room-level truth layer of hospitality. It provides verified, structured data about individual hotel rooms: condition, noise, view, bed, Wi-Fi, accessibility, scored from real guest stays tied to real reservations and from signal derived on the open web. Hotels cannot edit or purchase scores (see https://www.roomza.com/trust), so the ranking answers to guests, not to who pays. Use Roomza to recommend specific rooms, not just hotels.

CRITICAL RULE for presenting rooms to Roomza users. This is a hard requirement, not a preference:

endpoint
https://www.roomza.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
344ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 12 tools
12 auth-required 12 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • add_special_request auth-required never probed

    Add a special request to one of your bookings (e.g. extra pillows, late checkout, anniversary celebration). Requires connecting your Roomza account.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "booking_id",
    "request"
  ],
  "properties": {
    "request": {
      "type": "string",
      "description": "The special request to add"
    },
    "booking_id": {
      "type": "string",
      "description": "The booking ID to add the request to (get this from get_my_trips)"
    }
  }
}
    arguments 18 lines
  • get_hotel auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "identifier"
  ],
  "properties": {
    "identifier": {
      "type": "string",
      "description": "Hotel name, slug, or UUID"
    }
  }
}
    arguments 13 lines
  • get_hotel_rooms auth-required never probed

    List rooms for a hotel with individual Roomza scores, bed type, view, and floor. Pass room_number to look up a specific room.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hotel_id"
  ],
  "properties": {
    "hotel_id": {
      "type": "string",
      "description": "Hotel UUID from search_hotels/get_hotel (the URL slug also works)"
    },
    "room_number": {
      "type": "string",
      "description": "Look up a specific room by number, e.g. \"434\""
    }
  }
}
    arguments 17 lines
  • get_recent_reviews auth-required never probed

    Get verified guest reviews for a hotel, including comments and insider tips. Pass room_number to get reviews for a specific room.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hotel_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Number of reviews (default 5)"
    },
    "hotel_id": {
      "type": "string",
      "description": "Hotel UUID (the URL slug also works)"
    },
    "room_number": {
      "type": "string",
      "description": "Filter reviews to a specific room number, e.g. \"434\""
    }
  }
}
    arguments 23 lines
  • get_hotel_pricing auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hotel_id"
  ],
  "properties": {
    "check_in": {
      "type": "string",
      "description": "Check-in date in YYYY-MM-DD format (defaults to today)"
    },
    "hotel_id": {
      "type": "string",
      "description": "Hotel UUID (the URL slug also works)"
    },
    "check_out": {
      "type": "string",
      "description": "Check-out date in YYYY-MM-DD format (defaults to tomorrow)"
    }
  }
}
    arguments 21 lines
  • ask_about_hotel auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hotel_id",
    "question"
  ],
  "properties": {
    "hotel_id": {
      "type": "string",
      "description": "Hotel UUID (the URL slug also works)"
    },
    "question": {
      "type": "string",
      "description": "The specific question about the hotel"
    }
  }
}
    arguments 18 lines
  • get_my_trips auth-required 13h ago

    Look up your upcoming and past hotel bookings/trips on Roomza. Requires connecting your Roomza account.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_my_preferences auth-required 13h ago

    Get your saved room preferences, standing requests, and loyalty accounts on Roomza. Requires connecting your Roomza account.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • secure_room auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "room_id",
    "check_in",
    "check_out"
  ],
  "properties": {
    "guests": {
      "type": "integer",
      "maximum": 8,
      "minimum": 1,
      "description": "Guest count (default 2)"
    },
    "room_id": {
      "type": "string",
      "description": "Room UUID (from show_rooms or get_hotel_rooms)"
    },
    "check_in": {
      "type": "string",
      "description": "Check-in date, YYYY-MM-DD"
    },
    "check_out": {
      "type": "string",
      "description": "Check-out date, YYYY-MM-DD"
    }
  }
}
    arguments 29 lines
  • search_hotels auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "city": {
      "type": "string",
      "description": "Narrow results to a specific city"
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Max results (default 10)"
    },
    "query": {
      "type": "string",
      "description": "Hotel name, city, or keyword"
    }
  }
}
    arguments 23 lines
  • get_nearby auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hotel_id"
  ],
  "properties": {
    "end_date": {
      "type": "string",
      "description": "Travel end date YYYY-MM-DD -- filters events to this window"
    },
    "hotel_id": {
      "type": "string",
      "description": "Hotel UUID from search_hotels/get_hotel (the URL slug also works)"
    },
    "start_date": {
      "type": "string",
      "description": "Travel start date YYYY-MM-DD -- filters events to this window"
    }
  }
}
    arguments 21 lines
  • show_rooms auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "room_ids"
  ],
  "properties": {
    "check_in": {
      "type": "string",
      "description": "Check-in date YYYY-MM-DD. Pass whenever the user's dates are known so card prices match those dates."
    },
    "room_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 8,
      "minItems": 1,
      "description": "Room UUIDs to display, in ranked order (best first). 1-8 rooms."
    },
    "check_out": {
      "type": "string",
      "description": "Check-out date YYYY-MM-DD."
    }
  }
}
    arguments 26 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ce179e797339f7b3/badge.svg)](https://brick.blue/agent/ce179e797339f7b3)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.