Yasha Hotel — Direct Booking
REMOTE · YASHAHOTEL.COM
Book Yasha Hotel Luxembourg: live availability, exact prices, Stripe-secured booking.
Available components
Last scanned (9 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 18 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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.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.
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 14 Oct 26 +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.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- “check_availability” reworded the description of “checkout” cosmetic
- 12 Oct 26 67
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 18 Oct 2026 · Probed https://yashahotel.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yashahotel.com | CN=YE1,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 55529ba944770a6b38c57f4e3c55359a24b |
| SANs: www.yashahotel.com, yashahotel.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of yashahotel.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| yashahotel.com. | present | 29657 | 13 | Verified |
| yashahotel.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yashahotel.com/mcp | Verified | 200 | |
| http (plaintext) | http://yashahotel.com/mcp | HTTPS enforced | 301 | https://yashahotel.com/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 →
check_availability ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkin | string | yes | Arrival date YYYY-MM-DD (check-in from 13:00, front desk 24/7) |
| checkout | string | yes | Departure date YYYY-MM-DD (check-out before 11:00) |
No output schema declared.
No examples provided.
create_booking ~335
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.
| Name | Type | Req | Description |
|---|---|---|---|
| breakfast | boolean | – | Buffet breakfast for all guests, all nights |
| checkin | string | yes | Arrival date YYYY-MM-DD |
| checkout | string | yes | Departure date YYYY-MM-DD |
| extras | array | – | Extra ids from list_extras |
| guest_email | string | yes | Traveler email (booking confirmation is sent here) |
| guest_name | string | yes | 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 | yes | Room id from list_rooms / check_availability |
| special_requests | string | – | Free-text requests for the front desk |
No output schema declared.
No examples provided.
get_booking_status ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | Booking reference returned by create_booking |
No output schema declared.
No examples provided.
get_price_calendar ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | Month to inspect, format YYYY-MM |
| room_id | integer | – | Room id from list_rooms; defaults to the first room type |
No output schema declared.
No examples provided.
hotel_info ~87
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_extras ~72
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_rooms ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate_promo_code ~53
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).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Promo code to validate |
No output schema declared.
No examples provided.
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.
remote · yashahotel.com
claude mcp add --transport http jeffreyturov-dev-yasha-hotel 'https://yashahotel.com/mcp'
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.