_ registry / mcp streamable-http · checked 13h ago

wemake.holiday

https://wemake.holiday

Registry code: 9ef8d32f00c04a10

api record

wemake.holiday is a travel platform (hotels with live prices, flights, experiences, ready-made travel route ideas) in 26 languages. Hotel directory (about 2.8 million hotels, no dates needed): list_destinations for countries and places, browse_hotels for all hotels of a place, find_hotel to find a hotel by name. Use search_hotels for live hotel prices in a place and period, get_hotel for details of one hotel, search_flights for flights between airports, search_experiences for tours and activities, list_route_ideas / get_route_idea for existing travel routes. Always show the returned url to…

endpoint
https://wemake.holiday/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 it live, free and safe measured by this hub
Is wemake.holiday live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is wemake.holiday free to use?
Yes — the hub reached it with no key and no payment.
What tools does wemake.holiday have?
12 tools: country_guide, search_flights, browse_hotels, get_hotel, plan_trip, search_experiences, search_hotels, find_hotel, ….
Is wemake.holiday 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
125ms

last good check

priced tools
0

of 12 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 12 tools
3 open 9 never probed 3 of 12 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_route_ideas open 13h ago

    Ready-made multi-stop travel routes (stations, nights, best months, highlights) that already exist on wemake.holiday — optionally filtered by country (ISO code) and topic. Nothing is generated.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "how many (1-30), default 12"
        },
        "topic": {
          "type": "string",
          "description": "optional topic keyword as used by wemake.holiday, e.g. wandern, kultur, strand"
        },
        "country": {
          "type": "string",
          "description": "optional ISO country code, e.g. TH or IT"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code (default en)"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • list_destinations open 13h ago

    Countries with their number of hotels, or — with a country — the places in that country with their number of hotels. Covers about 2.8 million hotels worldwide. Use the returned slugs with browse_hotels. No travel dates needed.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "how many (1-200), default 50"
        },
        "country": {
          "type": "string",
          "description": "optional: country slug or ISO code (e.g. thailand or TH) — then the places of that country are listed"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code (default en)"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • public_travel_diaries open 13h ago

    Travel diaries that travellers have shared publicly on wemake.holiday, optionally for one country (ISO code). Only public diaries; nothing private is ever returned.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "how many (1-20), default 8"
        },
        "country": {
          "type": "string",
          "description": "optional ISO country code, e.g. TH"
        },
        "language": {
          "type": "string",
          "description": "language of the links, ISO code (default en)"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • country_guide unknown never probed

    Short travel guide for a country, region or city (introduction, getting there, climate, safety …) from Wikivoyage, with a photo of the place. Always mention the source Wikivoyage and its licence CC BY-SA 4.0 with the source link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "place"
      ],
      "properties": {
        "place": {
          "type": "string",
          "description": "country, region or city as its Wikivoyage article is called, e.g. Thailand, Tuscany, Lisbon"
        },
        "language": {
          "type": "string",
          "description": "answer language; de uses German Wikivoyage, all others English (default en)"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • search_flights unknown never probed

    Live flight offers between two airports (IATA codes such as FRA, BKK). Round trip if return_date is given. Takes 10–25 seconds. Returns the cheapest offers with times, stops, baggage and a link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to",
        "depart_date"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "arrival airport IATA code, e.g. BKK"
        },
        "from": {
          "type": "string",
          "description": "departure airport IATA code, e.g. FRA"
        },
        "adults": {
          "type": "integer",
          "description": "number of adults (1-9), default 1"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code (default en)"
        },
        "depart_date": {
          "type": "string",
          "description": "outbound date YYYY-MM-DD"
        },
        "return_date": {
          "type": "string",
          "description": "optional return date YYYY-MM-DD (round trip)"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • browse_hotels unknown never probed

    All hotels in a place (from list_destinations), sorted by guest rating, 50 per page — with stars, guest rating, number of reviews, address, location and a link. Optional filters: minimum stars, minimum guest rating (0–10). No travel dates needed; for live prices use search_hotels.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country",
        "place"
      ],
      "properties": {
        "page": {
          "type": "integer",
          "description": "page (50 hotels each), default 1"
        },
        "place": {
          "type": "string",
          "description": "place slug from list_destinations, e.g. bangkok"
        },
        "country": {
          "type": "string",
          "description": "country slug or ISO code, e.g. thailand"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code (default en)"
        },
        "min_stars": {
          "type": "number",
          "description": "optional minimum stars (1-5)"
        },
        "min_rating": {
          "type": "number",
          "description": "optional minimum guest rating (0-10)"
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • get_hotel unknown never probed

    Details of one hotel by its id (from search_hotels): address, location, stars, rating, check-in/out times, facilities, description and a link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "hotel id from search_hotels"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code (default en)"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • plan_trip unknown never probed

    Put together a trip plan for a country from route ideas that already exist on wemake.holiday (stations, nights, best months) plus bookable experiences per station. Nothing is generated — if no route idea exists for the country/topic, say so and offer search_hotels or search_experiences instead.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "description": "optional wished trip length in days; the closest existing route is chosen"
        },
        "topic": {
          "type": "string",
          "description": "optional interest as used by wemake.holiday, e.g. strand, kultur, wandern, essen"
        },
        "country": {
          "type": "string",
          "description": "ISO country code of the destination, e.g. TH, IT, PT"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code like en, de, fr (default en)"
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • search_experiences unknown never probed

    Tours, tickets and activities in a city or region (e.g. 'Rome', 'Koh Samui'), with rating, duration, price from, and a link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "place"
      ],
      "properties": {
        "place": {
          "type": "string",
          "description": "city or region, e.g. Rome or Koh Samui"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code (default en)"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • search_hotels unknown never probed

    Find hotels in a city, region, district or near a landmark for a stay, with live prices (total for the stay, per room). Optionally look for a specific hotel by name — typos and run-together names are fine. Returns up to 15 hotels with stars, guest rating, price and a link to book on wemake.holiday.

    mcp-tool

    {
      "type": "object",
      "required": [
        "place",
        "checkin",
        "checkout"
      ],
      "properties": {
        "place": {
          "type": "string",
          "description": "city, region, district or landmark, e.g. 'Bangkok Sukhumvit' or 'Koh Samui'"
        },
        "adults": {
          "type": "integer",
          "description": "number of adults (1-9), default 2"
        },
        "checkin": {
          "type": "string",
          "description": "arrival date YYYY-MM-DD"
        },
        "checkout": {
          "type": "string",
          "description": "departure date YYYY-MM-DD"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code like en, de, fr (default en)"
        },
        "hotel_name": {
          "type": "string",
          "description": "optional: name of a specific hotel to find (typos are fine)"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • find_hotel unknown never probed

    Find a specific hotel by its name — typos and run-together names are fine (e.g. 'MeeStyleGarrage'). Optionally narrow by country (ISO code) and place. Returns the best matches with id, address, stars, rating and link; use the id with get_hotel, or search_hotels for prices.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "hotel name (typos are fine)"
        },
        "place": {
          "type": "string",
          "description": "optional city or district, e.g. Bangkok"
        },
        "country": {
          "type": "string",
          "description": "optional ISO country code, e.g. TH — faster and more precise"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code (default en)"
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • get_route_idea unknown never probed

    Full existing travel route by id (from list_route_ideas): summary, stations with nights and reasons, best months, highlights, link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "integer",
          "description": "route id from list_route_ideas"
        },
        "language": {
          "type": "string",
          "description": "answer language, ISO code (default en)"
        }
      },
      "additionalProperties": false
    }
    arguments 17 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 9ef8d32f00c04a10.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9ef8d32f00c04a10/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/9ef8d32f00c04a10/badge.svg)](https://brick.blue/agent/9ef8d32f00c04a10?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.