Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Hotelumo is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
11
tools declared
remote
at its publisher
—
calls last 7d
What it does
See your hotel's room availability, rates, housekeeping and upcoming arrivals and departures.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http hotelumo-mcp https://mcp.hotelumo.com/mcp
# 2 — ask your agent for something these tools do
# list_hotels, get_hotel, get_hotel_availability and 8 more
Hotelumo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HOAll 1 server
hotelumo1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http hotelumo-mcp https://mcp.hotelumo.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Hotels per page, from 1 to 100; defaults to 20 |
| offset | integer | no | Hotels to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| 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 |
| adults | integer | no | Adults staying, from 1 to 20; defaults to 2 |
| children | integer | no | Children staying, from 0 to 20; defaults to 0 |
| infants | integer | no | Infants staying, from 0 to 20; defaults to 0 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| dateFrom | string | no | First day as YYYY-MM-DD (inclusive); defaults to today in UTC |
| dateTo | string | no | Last day as YYYY-MM-DD (inclusive), at most 31 days in total; defaults to six days after dateFrom |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotelId | string | no | Only this hotel (24 lowercase hexadecimal characters); every hotel when absent |
| limit | integer | no | Room types per page, from 1 to 100; defaults to 20 |
| offset | integer | no | Room types to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| roomTypeId | string | yes | Room type id: 24 lowercase hexadecimal characters |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotelId | string | no | Only this hotel (24 lowercase hexadecimal characters); every hotel when absent |
| roomTypeId | string | no | Only this room type (24 lowercase hexadecimal characters) |
| limit | integer | no | Rooms per page, from 1 to 100; defaults to 20 |
| offset | integer | no | Rooms to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| roomTypeId | string | no | Only this room type (24 lowercase hexadecimal characters) |
| limit | integer | no | Rate plans per page, from 1 to 100; defaults to 20 |
| offset | integer | no | Rate plans to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
| ratePlanId | string | yes | Rate plan id, belonging to hotelId: 24 lowercase hexadecimal characters |
| 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 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotelId | string | no | Only this hotel (24 lowercase hexadecimal characters); every hotel when absent |
| limit | integer | no | Extras per page, from 1 to 100; defaults to 20 |
| offset | integer | no | Extras to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotelId | string | yes | Hotel id: 24 lowercase hexadecimal characters |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Hotelumo or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.1.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest3887b52bf2e311fa383e5f8e58119961f058933d1f1c4f870bac0c3bd320a5e1
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_hotels | no tags | |
| get_hotel | no tags | |
| get_hotel_availability | no tags | |
| get_hotel_schedule_summary | no tags | |
| list_room_types | no tags | |
| get_room_type | no tags | |
| list_rooms | no tags | |
| list_rate_plans | no tags | |
| list_daily_rates | no tags | |
| list_extras | no tags | |
| show_hotel_overview | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest3887b52bf2e311fa
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Hotelumo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.