HotelRunner MCP by usefulapi
REMOTE · HOTELRUNNER.USEFULAPI.IO
Read HotelRunner reservations, rooms, channels; update availability and prices; confirm or cancel.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 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 Security78
- 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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability78
- 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 1742 tokens (~217/item across 8 items; 8 tools + 0 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 Management3
- Stability observed for 1 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.3 functional
- 24 Oct 26 62
First indexed and scored.
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 25 Oct 2026 · Probed https://hotelrunner.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hotelrunner.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | 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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://hotelrunner.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://hotelrunner.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://hotelrunner.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://hotelrunner.usefulapi.io/mcp |
| Authorisation server | https://hotelrunner.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hotelrunner.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/hotelrunner/ |
| http (plaintext) | http://hotelrunner.usefulapi.io/mcp | Inconclusive | 302 | http://hotelrunner.usefulapi.io/mcp |
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 →
hotelrunner_get_reservation Get reservation ~165
One reservation by its HotelRunner code (hr_number, e.g. R377873409) or the sales channel's own reservation code, with the full vendor record (rooms, daily prices, extras, payments, guest and billing details, next_states). If the reservation is older than HotelRunner's lookup window, pass from_date. Counts as one of the property's 250 requests per day (5 per minute). GET /api/v2/apps/reservations?reservation_number=.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Creation-date window start, yyyy-mm-dd (HotelRunner keeps at most 30 days back). |
| reservation_number | string | yes | HotelRunner reservation code (hr_number, e.g. R377873409) or the sales channel's reservation code. |
No output schema declared.
No examples provided.
hotelrunner_get_transaction_details Get calendar update status ~90
Per-channel status of a calendar update: pass the transaction_id returned by hotelrunner_update_room_calendar. Shows succeeded / failed / in-progress counts and each channel's state and error message. Counts as one of the property's 250 requests per day (5 per minute). GET /api/v2/apps/infos/transaction_details.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_id | string | yes | transaction_id from an update reply. |
No output schema declared.
No examples provided.
hotelrunner_list_channels List sales channels ~75
All sales channels HotelRunner supports (name and code, e.g. bookingcom, expedia, hrs, online). The code is what hotelrunner_update_room_calendar takes in channel_codes. Counts as one of the property's 250 requests per day (5 per minute). GET /api/v2/apps/infos/channels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hotelrunner_list_connected_channels List connected channels ~61
The channels this property is connected to, each with counts of calendar update processes in progress, succeeded and failed. Counts as one of the property's 250 requests per day (5 per minute). GET /api/v2/apps/infos/connected_channels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hotelrunner_list_reservations List reservations ~332
List reservations of the property (new, modified, canceled), newest data first as HotelRunner returns them, 1-50 per page. By default ALL reservations created in the window are returned (this tool sets undelivered=false, so reading does not depend on a PMS having fetched them). from_date is the creation date (HotelRunner keeps at most 30 days back; default 10 days); from_last_update_date finds reservations changed since a date. detail 'summary' (default) gives guest, dates, rooms, totals, payment state and contact; 'full' returns the whole vendor record including billing address, national id, daily prices and extras. Reply: items, count, page, pages, next_page. Counts as one of the property's 250 requests per day (5 per minute). GET /api/v2/apps/reservations.
| Name | Type | Req | Description |
|---|---|---|---|
| booked | boolean | – | true = only new (not modified) bookings. |
| detail | string | – | 'summary' (default) or 'full' vendor records (large). |
| from_date | string | – | Only reservations created on/after this date, yyyy-mm-dd (max 30 days back; default 10 days back). |
| from_last_update_date | string | – | Only reservations updated on/after this date, yyyy-mm-dd. |
| modified | boolean | – | true = only modified reservations. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Reservations per page, 1-50 (default 10). |
No output schema declared.
No examples provided.
hotelrunner_list_rooms List rooms and rates ~86
List the property's room types and rates with their inv_code and rate_code, capacity, pricing type, sales currency, connected channel codes and whether availability, restrictions and prices can be updated through the API. Use the inv_code with hotelrunner_update_room_calendar. Counts as one of the property's 250 requests per day (5 per minute). GET /api/v2/apps/rooms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hotelrunner_update_reservation_state Confirm or cancel a reservation ~244
WRITE: move ONE reservation to the next state: event 'confirm' (hotelier accepts it) or 'cancel' (cancels it; cancel_reason is required: customer, no_room, no_show or invalid_price). Cancel is not reversible through this API and releases the room; HotelRunner may notify the guest or the sales channel (Booking.com, Expedia, ...), so only cancel when the user clearly asked for it, and pass confirm=true for a cancel. Only possible when the reservation's requires_response is true and the event is in its next_states (see hotelrunner_get_reservation); otherwise HotelRunner answers state_change_is_not_available. Counts as one of the property's 250 requests per day (5 per minute). PUT /api/v2/apps/reservations/fire.
| Name | Type | Req | Description |
|---|---|---|---|
| cancel_reason | string | – | Required for cancel: customer, no_room, no_show or invalid_price. |
| confirm | boolean | – | Required true for event 'cancel': the user explicitly approved cancelling this reservation (not reversible). |
| event | string | yes | 'confirm' or 'cancel'. |
| hr_number | string | yes | HotelRunner reservation code (hr_number). |
No output schema declared.
No examples provided.
hotelrunner_update_room_calendar Update room availability, prices and restrictions ~426
WRITE: change availability, price, minimum/maximum stay, stop-sale, closed-to-arrival (cta) or closed-to-departure (ctd) for ONE room type (inv_code) over a date range of at most 90 days, optionally only on some weekdays and only on some channels. Only the fields you pass are changed. This is LIVE inventory: HotelRunner pushes it to every connected channel (Booking.com, Expedia, your own booking engine, ...) and it changes what guests can book and pay. The price is the base-rate price in the property's sales currency; guest-based prices derive from it. Only rooms whose availability_update / restrictions_update / price_update flag is true (hotelrunner_list_rooms) accept that kind of change. HotelRunner answers asynchronously: the reply has a transaction_id; check per-channel results with hotelrunner_get_transaction_details. Send one change per call, not a full refresh. Counts as one of the property's 250 requests per day (5 per minute). PUT /api/v2/apps/rooms/daily.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | integer | – | Rooms available to sell. |
| channel_codes | array | – | Only these channels (codes from hotelrunner_list_connected_channels); default: all connected channels of the room. |
| cta | boolean | – | Closed to arrival. |
| ctd | boolean | – | Closed to departure. |
| days | array | – | Only these weekdays, 0 = Sunday ... 6 = Saturday (default: every day). |
| end_date | string | yes | Last date to change (inclusive), yyyy-mm-dd. |
| inv_code | string | yes | An inventory code from hotelrunner_list_rooms, e.g. HR:1903. |
| max_stay | integer | – | Maximum nights. |
| min_stay | integer | – | Minimum nights. |
| price | number | – | Base nightly price in the property's sales currency. |
| start_date | string | yes | First date to change, yyyy-mm-dd. |
| stop_sale | boolean | – | true = close the room for sale on these dates, false = reopen. |
No output schema declared.
No examples provided.
How do I install the HotelRunner MCP by usefulapi server?
HotelRunner MCP by usefulapi is a hosted endpoint at https://hotelrunner.usefulapi.io/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 · hotelrunner.usefulapi.io
claude mcp add --transport http io-usefulapi-hotelrunner 'https://hotelrunner.usefulapi.io/mcp'
What is the HotelRunner MCP by usefulapi server?
HotelRunner MCP by usefulapi is listed in the public MCP registry as io.usefulapi/hotelrunner. Read HotelRunner reservations, rooms, channels; update availability and prices; confirm or cancel. This page covers its hosted endpoint (https://hotelrunner.usefulapi.io/mcp).
Is the HotelRunner MCP by usefulapi server safe to use?
HotelRunner MCP by usefulapi scores 62 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 HotelRunner MCP by usefulapi server expose?
HotelRunner MCP by usefulapi exposes 8 tools: hotelrunner_list_rooms, hotelrunner_list_reservations, hotelrunner_get_reservation, hotelrunner_list_channels, hotelrunner_list_connected_channels, and 3 more. Their descriptions and schemas cost roughly 1,479 tokens of context every time the server is loaded.
Does the HotelRunner MCP by usefulapi server require authentication?
Yes. HotelRunner MCP by usefulapi 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 HotelRunner MCP by usefulapi server still maintained?
HotelRunner MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.