Hotelumo Hotel Operations
REMOTE · MCP.HOTELUMO.COM
See your hotel's room availability, rates, housekeeping and upcoming arrivals and departures.
Available components
Last scanned (2 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 17 Oct 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3160 tokens (~210/item across 15 items; 11 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 50. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 43. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://mcp.hotelumo.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hotelumo.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 1 Aug 2026 | 14 Feb 2027 | RSA 2048 | SHA256-RSA | 4974cb9d90c78d8d3b3f0b949b88703 |
| SANs: hotelumo.com, *.migration.hotelumo.com, *.hotelumo.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.hotelumo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hotelumo.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="hotelumo", resource_metadata="https://mcp.hotelumo.com/.well-known/oauth-protected-resource", scope="hotelumo:read", error="invalid_token", error_description="missing Bearer token"
Bearer realm="hotelumo", resource_metadata="https://mcp.hotelumo.com/.well-known/oauth-protected-resource", scope="hotelumo:read", error="invalid_token", error_description="missing Bearer token"Protected resource metadata
| Document | https://mcp.hotelumo.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.hotelumo.com |
| Authorisation server | https://api.authrice.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.hotelumo.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.hotelumo.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_hotel Get hotel details ~85
Use this when someone asks about one hotel's setup, such as its default check-in and check-out times, currency, country or timezone. Returns the hotel's name, currency, language, timezone, country code and default check-in and check-out times, or not-found. Not for room availability or prices.
| Name | Type | Req | Description |
|---|---|---|---|
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| Name | Type | Req | Description |
|---|---|---|---|
| hotel | – | yes | Operational hotel metadata; null when not found. Contact details, addresses, integrations, credentials, payment configuration, reminders and guest data are never returned. |
| status | string | yes | – |
No examples provided.
get_hotel_availability Check room availability and prices ~215
Use this when someone asks if rooms are free for certain dates or what a stay would cost. Returns the room types and rate plans with a free room every night for the party, with rooms left and nightly and total prices in minor currency units. Stays of 1–30 nights, check-in within 365 days. Not for making a booking.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Adults staying, from 1 to 20; defaults to 2 |
| checkInDate | string | yes | Arrival date as YYYY-MM-DD, from today to 365 days ahead in the hotel's timezone |
| checkOutDate | string | yes | Departure date as YYYY-MM-DD, 1 to 30 nights after checkInDate |
| children | integer | – | Children staying, from 0 to 20; defaults to 0 |
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| infants | integer | – | Infants staying, from 0 to 20; defaults to 0 |
| Name | Type | Req | Description |
|---|---|---|---|
| offers | array | yes | One row per bookable room type and rate plan with a free room every night. Amounts are integer minor currency units (12000 is 120.00 in a two-decimal currency). Guest records, reservations, room assi… |
| offersAreTruncated | boolean | yes | True when more than 100 offers matched the search |
| search | object | yes | – |
No examples provided.
get_hotel_schedule_summary Count arrivals, departures and stays ~155
Use this when someone asks how busy the hotel is, or how many arrivals, departures or in-house stays fall on each day. Returns daily counts of confirmed, checked-in and checked-out stays plus reservation totals by status, for 7 days from today by default and at most 31 days; counting stops at 500. Not for looking up a guest or reservation.
| Name | Type | Req | Description |
|---|---|---|---|
| dateFrom | string | – | First day as YYYY-MM-DD (inclusive); defaults to today in UTC |
| dateTo | string | – | Last day as YYYY-MM-DD (inclusive), at most 31 days in total; defaults to six days after dateFrom |
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | yes | One row per day. arrivals, departures and inHouseReservations count confirmed, checked-in and checked-out stays; a stay is not in-house on its checkout day. Reservation or allocation identifiers, ind… |
| hotel | object | yes | – |
| range | object | yes | – |
| reservationCount | integer | yes | – |
| reservationCountIsLowerBound | boolean | yes | True when more than 500 reservations overlap the range |
| statusCounts | object | yes | Reservations overlapping the range by status, inquiries, requests, no-shows and cancellations included |
No examples provided.
get_room_type Get room type details ~72
Use this when someone asks about one room type, such as its name or how many guests it sleeps. Returns the room type's name, hotel and maximum guests, or not-found. Not for its prices or free dates.
| Name | Type | Req | Description |
|---|---|---|---|
| roomTypeId | string | yes | Room type id: 24 lowercase hexadecimal characters |
| Name | Type | Req | Description |
|---|---|---|---|
| roomType | – | yes | Null when not found. Free-text descriptions, facilities, photos, channel mappings, integrations, credentials and arbitrary metadata are never returned. |
| status | string | yes | – |
No examples provided.
list_daily_rates Show daily prices and restrictions ~154
Use this when someone asks what a rate costs on specific nights, or about minimum stays, stop-sell or closed-to-arrival dates. Returns the stored per-day price and restrictions of one rate plan over up to 90 days; days without a row use the plan's base price. Not for whether rooms are free.
| Name | Type | Req | Description |
|---|---|---|---|
| dateFrom | string | yes | First night as YYYY-MM-DD (inclusive) |
| dateTo | string | yes | Last night as YYYY-MM-DD (inclusive); the range covers at most 90 days |
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| ratePlanId | string | yes | Rate plan id, belonging to hotelId: 24 lowercase hexadecimal characters |
| Name | Type | Req | Description |
|---|---|---|---|
| dailyRates | array | yes | Stored per-day rows sorted by date; a date without a row sells at the plan's base price. price is in integer minor currency units. Guest, payment, channel, credential and arbitrary metadata are exclu… |
| status | string | yes | – |
No examples provided.
list_extras List extras and add-ons ~149
Use this when someone asks what extras a hotel sells, such as breakfast, parking, spa, transfers or fees, and what they cost. Returns each active extra's name, price in minor currency units, currency, category and taxable flag, 20 per page by default. Not for what a guest bought or was charged.
| Name | Type | Req | Description |
|---|---|---|---|
| hotelId | string | – | Only this hotel (24 lowercase hexadecimal characters); every hotel when absent |
| limit | integer | – | Extras per page, from 1 to 100; defaults to 20 |
| offset | integer | – | Extras to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
| Name | Type | Req | Description |
|---|---|---|---|
| extras | array | yes | Active extras; price is in integer minor currency units. Guest charges, folio data, display colors and credentials are excluded. |
| page | object | yes | hasMore is true when another page exists; request it with offset + limit |
No examples provided.
list_hotels List your hotels ~116
Use this when someone asks which hotels or properties they manage in Hotelumo, or a hotel's id is needed. Returns each hotel's id, name, currency, language and timezone, 20 per page by default (no addresses or guest data). Not for room availability.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Hotels per page, from 1 to 100; defaults to 20 |
| offset | integer | – | Hotels to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
| Name | Type | Req | Description |
|---|---|---|---|
| hotels | array | yes | Hotels in the signed-in organization. Addresses, phone numbers, channel credentials, payment configuration, reminder configuration and guest data are excluded. |
| page | object | yes | hasMore is true when another page exists; request it with offset + limit |
No examples provided.
list_rate_plans List rate plans and base prices ~170
Use this when someone asks what rate plans a hotel sells, such as room-only or breakfast-included rates, and their base prices. Returns each plan's title, room type, base price in minor currency units, meal plan, per-room or per-person pricing and default flag, 20 per page by default. Not for prices on specific dates.
| Name | Type | Req | Description |
|---|---|---|---|
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| limit | integer | – | Rate plans per page, from 1 to 100; defaults to 20 |
| offset | integer | – | Rate plans to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
| roomTypeId | string | – | Only this room type (24 lowercase hexadecimal characters) |
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | yes | hasMore is true when another page exists; request it with offset + limit |
| ratePlans | array | yes | basePrice is in integer minor currency units. Channel-manager mappings, integration metadata and credentials are excluded. |
No examples provided.
list_room_types List room types ~144
Use this when someone asks what kinds of rooms a hotel offers or how many guests each room type sleeps. Returns each room type's id, hotel, name and maximum guests, sorted by name, 20 per page by default. Not for whether a room type is free on given dates.
| Name | Type | Req | Description |
|---|---|---|---|
| hotelId | string | – | Only this hotel (24 lowercase hexadecimal characters); every hotel when absent |
| limit | integer | – | Room types per page, from 1 to 100; defaults to 20 |
| offset | integer | – | Room types to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | yes | hasMore is true when another page exists; request it with offset + limit |
| roomTypes | array | yes | Room types sorted by name. Photos, public descriptions, rate-plan internals, channel mappings and credentials are excluded. |
No examples provided.
list_rooms Check room and housekeeping status ~169
Use this when someone asks which rooms are clean, dirty or inspected, or which are out of order or out of service. Returns each physical room's name or number, room type and hotel with its room and housekeeping status, 20 per page by default (no guest or occupant data). Not for which rooms are free on given dates.
| Name | Type | Req | Description |
|---|---|---|---|
| hotelId | string | – | Only this hotel (24 lowercase hexadecimal characters); every hotel when absent |
| limit | integer | – | Rooms per page, from 1 to 100; defaults to 20 |
| offset | integer | – | Rooms to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
| roomTypeId | string | – | Only this room type (24 lowercase hexadecimal characters) |
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | yes | hasMore is true when another page exists; request it with offset + limit |
| rooms | array | yes | Physical rooms sorted by name. Internal room ids, reservation, occupant, guest, access-control and channel data are excluded. |
No examples provided.
show_hotel_overview Show hotel operations overview ~90
Use this when someone wants a quick overview or dashboard of one hotel's operations. Returns an overview card with the hotel's details, reservation status counts for the next 7 days, and room, room-type, room-status and housekeeping counts from bounded samples (no guest, stay or payment data). Not for a single reservation.
| Name | Type | Req | Description |
|---|---|---|---|
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| Name | Type | Req | Description |
|---|---|---|---|
| hotel | – | yes | Null when not found. Guest identities, contact details, reservation or allocation identifiers, individual stay records, notes, documents, occupant ids, payments, access data, integration configuratio… |
| housekeepingStatusCounts | object | yes | – |
| reservationStatusCounts | object | yes | – |
| reservations | object | yes | Reservations overlapping the next seven UTC days, any status, sampled up to 50; hasMore marks a lower bound |
| roomStatusCounts | object | yes | – |
| roomTypes | object | yes | Room types, sampled up to 50; hasMore marks a lower bound |
| rooms | object | yes | Physical rooms, sampled up to 100; hasMore marks a lower bound |
| scheduleRange | object | yes | – |
No examples provided.
How do I install the Hotelumo Hotel Operations MCP server?
Hotelumo Hotel Operations is a hosted endpoint at https://mcp.hotelumo.com/mcp, 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.
remote · mcp.hotelumo.com
claude mcp add --transport http com-hotelumo-hotelumo 'https://mcp.hotelumo.com/mcp'
What is the Hotelumo Hotel Operations MCP server?
Hotelumo Hotel Operations is an MCP server listed in the public MCP registry as com.hotelumo/hotelumo. See your hotel's room availability, rates, housekeeping and upcoming arrivals and departures. This page covers its hosted endpoint (https://mcp.hotelumo.com/mcp).
Is the Hotelumo Hotel Operations MCP server safe to use?
Hotelumo Hotel Operations scores 90 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 Hotelumo Hotel Operations MCP server expose?
Hotelumo Hotel Operations exposes 11 tools: list_hotels, get_hotel, get_hotel_availability, get_hotel_schedule_summary, list_room_types, and 6 more. Their descriptions and schemas cost roughly 1,519 tokens of context every time the server is loaded.
Does the Hotelumo Hotel Operations MCP server require authentication?
Yes. Hotelumo Hotel Operations asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Hotelumo Hotel Operations MCP server still maintained?
Hotelumo Hotel Operations is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.