# HotelRunner MCP by usefulapi (remote · hotelrunner.usefulapi.io)

Read HotelRunner reservations, rooms, channels; update availability and prices; confirm or cancel.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `hotelrunner.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-hotelrunner/hotelrunner.md), [page](https://verifymcp.io/servers/io-usefulapi-hotelrunner/hotelrunner)

## Channel facts

- Endpoint: `https://hotelrunner.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-hotelrunner 'https://hotelrunner.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-hotelrunner": {
      "url": "https://hotelrunner.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-hotelrunner": {
      "type": "http",
      "url": "https://hotelrunner.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-hotelrunner]
url = "https://hotelrunner.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-hotelrunner": {
      "type": "remote",
      "url": "https://hotelrunner.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-hotelrunner --url 'https://hotelrunner.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-hotelrunner:
    url: "https://hotelrunner.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-hotelrunner": {
      "Transport": "http",
      "Url": "https://hotelrunner.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-hotelrunner -t streamable-http -u 'https://hotelrunner.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-hotelrunner": {
      "type": "http",
      "url": "https://hotelrunner.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.3

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (8)

### `hotelrunner_list_rooms` (~86 tokens)

List rooms and rates

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.

### `hotelrunner_list_reservations` (~332 tokens)

List reservations

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.

Input parameters:

- `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).

### `hotelrunner_get_reservation` (~165 tokens)

Get reservation

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=.

Input parameters:

- `from_date` (string): Creation-date window start, yyyy-mm-dd (HotelRunner keeps at most 30 days back).
- `reservation_number` (string, required): HotelRunner reservation code (hr_number, e.g. R377873409) or the sales channel's reservation code.

### `hotelrunner_list_channels` (~75 tokens)

List sales channels

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.

### `hotelrunner_list_connected_channels` (~61 tokens)

List connected channels

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.

### `hotelrunner_get_transaction_details` (~90 tokens)

Get calendar update status

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.

Input parameters:

- `transaction_id` (string, required): transaction_id from an update reply.

### `hotelrunner_update_room_calendar` (~426 tokens)

Update room availability, prices and restrictions

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.

Input parameters:

- `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, required): Last date to change (inclusive), yyyy-mm-dd.
- `inv_code` (string, required): 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, required): First date to change, yyyy-mm-dd.
- `stop_sale` (boolean): true = close the room for sale on these dates, false = reopen.

### `hotelrunner_update_reservation_state` (~244 tokens)

Confirm or cancel a reservation

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.

Input parameters:

- `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, required): 'confirm' or 'cancel'.
- `hr_number` (string, required): HotelRunner reservation code (hr_number).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-hotelrunner/hotelrunner#diagnostics

## Score history

- 2026-10-25: 62
- 2026-10-24: 62

## Common questions

### 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.

## Links

- Remote endpoint: https://hotelrunner.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/hotelrunner/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-hotelrunner/hotelrunner.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-hotelrunner/hotelrunner.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-hotelrunner/hotelrunner