vibebook

endpoint

https://vibebook.vibebooking.ai/mcp

protocol

streamable-http ·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 vibebook live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is vibebook free to use?

Yes — the hub reached it with no key and no payment.

What tools does vibebook have?

5 tools: book_link, search_hotels, get_hotel, get_rates, resolve_hotel.

Is vibebook 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.

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.

• book_link unknown never probed

  The link that hands the traveller to the hotel's own booking page for a stay, optionally for one offer from get_rates (its id, and total.minor and total.currency as get_rates gave them, so the price is re-checked when they click). Nothing is booked, held or paid here: the traveller books and pays on the hotel's page. Never call it a confirmed booking.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940

  {
    "type": "object",
    "required": [
      "hotel",
      "checkin",
      "nights",
      "guests"
    ],
    "properties": {
      "hotel": {
        "type": "string",
        "description": "The hotel id from search_hotels or resolve_hotel, or the hotel's website domain."
      },
      "offer": {
        "type": "string",
        "description": "The offer's id from get_rates; leave out to open the hotel's booking page for the stay."
      },
      "total": {
        "type": "integer",
        "description": "With offer: total.minor from get_rates, the whole-stay total in minor units."
      },
      "guests": {
        "type": "integer",
        "description": "Number of adult guests."
      },
      "nights": {
        "type": "integer",
        "description": "Number of nights, 1 or more."
      },
      "checkin": {
        "type": "string",
        "description": "Check-in date, YYYY-MM-DD."
      },
      "currency": {
        "type": "string",
        "description": "With offer: total.currency from get_rates, such as JPY."
      }
    },
    "additionalProperties": false
  }

  arguments 40 lines copy
• search_hotels unknown never probed

  Search VibeBooking's registry of independent hotels and inns in Japan by destination area: a city, ward, district or station name as it appears in a hotel's address (日本語 or English, e.g. 京都市東山区, Gion, 河原町). This is where the traveller wants to stay, not where they are. The registry is small and growing: when it has no match, use your own web search to find hotels' websites, then call resolve_hotel with each domain. Each hit carries the hotel id to pass to get_hotel (its facts and room types) or get_rates. other_hotels lists hotels in the same prefecture that are not VibeBooking's, from our agent-readiness index: each one's own site and how far an agent can get there (level 0 invisible, 1 discoverable, 2 priceable, 3 machine-readable, 4 transactable), at min_level or above. There are no rates for them here, but they are real places to stay: list them to the traveller by their site, beside any hit, so they can check dates and book there.

  mcp-tool

  1234567891011121314151617181920212223242526272829

  {
    "type": "object",
    "required": [
      "area"
    ],
    "properties": {
      "area": {
        "type": "string",
        "description": "Where the traveller wants to stay: a city, ward, district or station name."
      },
      "guests": {
        "type": "integer",
        "description": "Number of adult guests."
      },
      "nights": {
        "type": "integer",
        "description": "Number of nights, 1 or more."
      },
      "checkin": {
        "type": "string",
        "description": "Check-in date, YYYY-MM-DD."
      },
      "min_level": {
        "type": "integer",
        "description": "Lowest agent-readiness level to list in other_hotels, 0 to 4; default 1."
      }
    },
    "additionalProperties": false
  }

  arguments 29 lines copy
• get_hotel unknown 1h ago

  A VibeBooking hotel's published facts, with no dates needed: name, address, check-in and cancellation terms, images and its room types (rooms[].ref, name, max_occupancy, size_m2 and each room's own facts). With room, a ref from rooms[].ref, one room type's page instead. hotel is the id from search_hotels or resolve_hotel, or the hotel's domain. For a hotel that is not ours the answer is its own site's address.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "hotel"
    ],
    "properties": {
      "room": {
        "type": "string",
        "description": "A room type's ref, from get_hotel's rooms[].ref; leave out for the whole hotel."
      },
      "hotel": {
        "type": "string",
        "description": "The hotel id from search_hotels or resolve_hotel, or the hotel's website domain."
      }
    },
    "additionalProperties": false
  }

  arguments 17 lines copy
• get_rates unknown 1h ago

  Live rates for a stay at a VibeBooking hotel: each room and plan's whole-stay total with its currency, tax and cancellation terms, when the rate was read (observed_at), and book: the link to give the traveller for the cheapest offer. For another offer, call book_link with its id and total. hotel is the id from search_hotels or resolve_hotel, or the hotel's domain. For a hotel that is not ours there are no rates here: the answer is its own site's address.

  mcp-tool

  12345678910111213141516171819202122232425262728

  {
    "type": "object",
    "required": [
      "hotel",
      "checkin",
      "nights",
      "guests"
    ],
    "properties": {
      "hotel": {
        "type": "string",
        "description": "The hotel id from search_hotels or resolve_hotel, or the hotel's website domain."
      },
      "guests": {
        "type": "integer",
        "description": "Number of adult guests."
      },
      "nights": {
        "type": "integer",
        "description": "Number of nights, 1 or more."
      },
      "checkin": {
        "type": "string",
        "description": "Check-in date, YYYY-MM-DD."
      }
    },
    "additionalProperties": false
  }

  arguments 28 lines copy
• resolve_hotel unknown 1h ago

  Call this whenever the user gives you, or your web search finds, a hotel's website. Pass its domain or URL. For a VibeBooking hotel it answers the hotel id and its agent page, which get_hotel, get_rates and book_link take; for any other hotel, its own site to send the traveller to and, when we have probed it, its agent-readiness level and the surfaces an agent can use there. A hotel name alone cannot be resolved: find its website first.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "domain_or_name"
    ],
    "properties": {
      "domain_or_name": {
        "type": "string",
        "description": "The hotel's website domain or URL, such as inn.example.jp. A name alone is not enough."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy

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

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.