_ registry / mcp http-sse · checked 11h ago

yasha-hotel

https://yashahotel.com

Registry code: 627840bb4cc5a511

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://yashahotel.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is yasha-hotel live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is yasha-hotel free to use?
Yes — the hub reached it with no key and no payment.
What tools does yasha-hotel have?
8 tools: get_booking_status, hotel_info, check_availability, get_price_calendar, validate_promo_code, create_booking, list_rooms, list_extras.
Is yasha-hotel safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
267ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_rooms open 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_extras open 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_booking_status unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "booking_id"
      ],
      "properties": {
        "booking_id": {
          "type": "string",
          "minLength": 1,
          "description": "Booking reference returned by create_booking"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • hotel_info unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • check_availability unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "checkin",
        "checkout"
      ],
      "properties": {
        "checkin": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Arrival date YYYY-MM-DD (check-in from 13:00, front desk 24/7)"
        },
        "checkout": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Departure date YYYY-MM-DD (check-out before 11:30)"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • get_price_calendar unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "month"
      ],
      "properties": {
        "month": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}$",
          "description": "Month to inspect, format YYYY-MM"
        },
        "room_id": {
          "type": "integer",
          "description": "Room id from list_rooms; defaults to the first room type"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • validate_promo_code unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "minLength": 1,
          "description": "Promo code to validate"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • create_booking unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "room_id",
        "checkin",
        "checkout",
        "guest_name",
        "guest_email"
      ],
      "properties": {
        "extras": {
          "type": "array",
          "items": {
            "type": "integer"
          },
          "description": "Extra ids from list_extras"
        },
        "guests": {
          "type": "integer",
          "minimum": 1,
          "description": "Number of guests, defaults to 1"
        },
        "checkin": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Arrival date YYYY-MM-DD"
        },
        "room_id": {
          "type": "integer",
          "description": "Room id from list_rooms / check_availability"
        },
        "checkout": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Departure date YYYY-MM-DD"
        },
        "breakfast": {
          "type": "boolean",
          "description": "Buffet breakfast for all guests, all nights"
        },
        "guest_name": {
          "type": "string",
          "minLength": 2,
          "description": "Traveler full name"
        },
        "promo_code": {
          "type": "string",
          "description": "Promo code (validate first with validate_promo_code)"
        },
        "guest_email": {
          "type": "string",
          "format": "email",
          "description": "Traveler email (booking confirmation is sent here)"
        },
        "guest_phone": {
          "type": "string",
          "description": "Traveler phone, optional"
        },
        "special_requests": {
          "type": "string",
          "description": "Free-text requests for the front desk"
        }
      },
      "additionalProperties": false
    }
    arguments 66 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 627840bb4cc5a511.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/627840bb4cc5a511/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/627840bb4cc5a511/badge.svg)](https://brick.blue/agent/627840bb4cc5a511?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.