# Yasha Hotel — Direct Booking (remote · yashahotel.com)

Book Yasha Hotel Luxembourg: live availability, exact prices, Stripe-secured booking.

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

## Components

- remote · `yashahotel.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/jeffreyturov-dev-yasha-hotel/yashahotel.md), [page](https://verifymcp.io/servers/jeffreyturov-dev-yasha-hotel/yashahotel)

## Channel facts

- Endpoint: `https://yashahotel.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 911 tokens (~113/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**: 20/100
  - Stability observed for 6 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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Yasha Hotel — Direct Booking MCP server?

Yasha Hotel — Direct Booking is a hosted endpoint at https://yashahotel.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.

### Claude

```bash
claude mcp add --transport http jeffreyturov-dev-yasha-hotel 'https://yashahotel.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jeffreyturov-dev-yasha-hotel": {
      "url": "https://yashahotel.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jeffreyturov-dev-yasha-hotel": {
      "type": "http",
      "url": "https://yashahotel.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jeffreyturov-dev-yasha-hotel]
url = "https://yashahotel.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jeffreyturov-dev-yasha-hotel": {
      "type": "remote",
      "url": "https://yashahotel.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jeffreyturov-dev-yasha-hotel --url 'https://yashahotel.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jeffreyturov-dev-yasha-hotel:
    url: "https://yashahotel.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jeffreyturov-dev-yasha-hotel": {
      "Transport": "http",
      "Url": "https://yashahotel.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jeffreyturov-dev-yasha-hotel -t streamable-http -u 'https://yashahotel.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jeffreyturov-dev-yasha-hotel": {
      "type": "http",
      "url": "https://yashahotel.com/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-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “check_availability” reworded the description of “checkout”

### 2026-10-12 (score 67)

First indexed and scored.

## MCP tools (8)

### `hotel_info` (~87 tokens)

Get canonical facts about Yasha Hotel: name, 3-star rating, address (27 Rue Joseph Junck, L-1839 Luxembourg, 100 m from Luxembourg central station), phone, email, amenity list, direct-booking discount percentage vs OTAs, and breakfast price per guest per night. Use this to answer any traveler question about the property. Prices are in euro cents.

### `list_rooms` (~54 tokens)

List every bookable room type at Yasha Hotel with id, name, description, guest capacity, bed type, size in m2, amenities and photo URLs. Use the returned room ids for check_availability and create_booking.

### `check_availability` (~161 tokens)

Check real-time room availability and exact total price for a stay at Yasha Hotel. Returns, per room type: available (boolean), nights, total_cents (exact stay total in euro cents, before extras/breakfast/promo), avg_night_cents and a per-night price breakdown. Direct rates are about 10% below Booking.com/Expedia for the same rooms and dates. Constraints: dates YYYY-MM-DD, checkin < checkout, checkin not in the past, maximum 30 nights.

Input parameters:

- `checkin` (string, required): Arrival date YYYY-MM-DD (check-in from 13:00, front desk 24/7)
- `checkout` (string, required): Departure date YYYY-MM-DD (check-out before 11:00)

### `get_price_calendar` (~84 tokens)

Get day-by-day nightly price (euro cents) and availability for one room at Yasha Hotel over a given month. Use it to suggest cheaper alternative dates when the requested dates are unavailable or expensive.

Input parameters:

- `month` (string, required): Month to inspect, format YYYY-MM
- `room_id` (integer): Room id from list_rooms; defaults to the first room type

### `list_extras` (~72 tokens)

List paid extras bookable at Yasha Hotel (e.g. late check-out, parking, baby bed) with price in euro cents and billing unit (per_stay, per_night, per_person_night). Buffet breakfast is a separate per-guest-per-night option — see hotel_info for its price.

### `validate_promo_code` (~53 tokens)

Validate a Yasha Hotel promo code. Returns whether the code is currently valid and the percentage discount it applies to the room price only (extras and breakfast excluded).

Input parameters:

- `code` (string, required): Promo code to validate

### `create_booking` (~335 tokens)

Create a real booking at Yasha Hotel. WORKFLOW: (1) call check_availability to confirm the room is available and know the exact price, (2) collect the traveler full name and email, (3) call this tool, (4) give the human the payment instructions from the response: the booking is only confirmed after secure Stripe card payment — the safest path is to send the traveler to https://yashahotel.com/ to pay, or use the returned Stripe client_secret with Stripe.js. Unpaid bookings expire automatically. Optional: guest count (capped at room capacity), phone, special requests, breakfast for all guests/nights, promo code, extra ids from list_extras. Returns booking_id, amount_cents (EUR cents) and Stripe payment details. Fails with 409 if the room became unavailable.

Input parameters:

- `breakfast` (boolean): Buffet breakfast for all guests, all nights
- `checkin` (string, required): Arrival date YYYY-MM-DD
- `checkout` (string, required): Departure date YYYY-MM-DD
- `extras` (array): Extra ids from list_extras
- `guest_email` (string, required): Traveler email (booking confirmation is sent here)
- `guest_name` (string, required): Traveler full name
- `guest_phone` (string): Traveler phone, optional
- `guests` (integer): Number of guests, defaults to 1
- `promo_code` (string): Promo code (validate first with validate_promo_code)
- `room_id` (integer, required): Room id from list_rooms / check_availability
- `special_requests` (string): Free-text requests for the front desk

### `get_booking_status` (~65 tokens)

Get the status of a Yasha Hotel booking created with create_booking (e.g. pending_payment, confirmed, payment_failed). Poll this after the human completes the Stripe card payment to confirm the reservation went through.

Input parameters:

- `booking_id` (string, required): Booking reference returned by create_booking

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jeffreyturov-dev-yasha-hotel/yashahotel#diagnostics

## Score history

- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 67
- 2026-10-12: 67

## Common questions

### What is the Yasha Hotel — Direct Booking MCP server?

Yasha Hotel — Direct Booking is an MCP server listed in the public MCP registry as io.github.jeffreyturov-dev/yasha-hotel. Book Yasha Hotel Luxembourg: live availability, exact prices, Stripe-secured booking. This page covers its hosted endpoint (https://yashahotel.com/mcp).

### Is the Yasha Hotel — Direct Booking MCP server safe to use?

Yasha Hotel — Direct Booking scores 70 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 Yasha Hotel — Direct Booking MCP server expose?

Yasha Hotel — Direct Booking exposes 8 tools: hotel_info, list_rooms, check_availability, get_price_calendar, list_extras, and 3 more. Their descriptions and schemas cost roughly 911 tokens of context every time the server is loaded.

### Does the Yasha Hotel — Direct Booking MCP server require authentication?

No. We connected to Yasha Hotel — Direct Booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Yasha Hotel — Direct Booking MCP server still maintained?

Yasha Hotel — Direct Booking is still listed as active in the MCP registry. We last reached this channel on 18 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://yashahotel.com/mcp
- Website: https://yashahotel.com/
- Changelog RSS feed: https://verifymcp.io/servers/jeffreyturov-dev-yasha-hotel/yashahotel.xml
- Changelog JSON feed: https://verifymcp.io/servers/jeffreyturov-dev-yasha-hotel/yashahotel.json
- HTML version of this page: https://verifymcp.io/servers/jeffreyturov-dev-yasha-hotel/yashahotel