# wemake.holiday (remote · wemake.holiday)

Hotels (2.8M directory + live prices), flights, tours, route ideas, travel guides – read-only.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `wemake.holiday`: 80/100 (this document), [markdown](https://verifymcp.io/servers/holiday-wemake-wemake-holiday/wemake.md), [page](https://verifymcp.io/servers/holiday-wemake-wemake-holiday/wemake)

## Channel facts

- Endpoint: `https://wemake.holiday/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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1698 tokens (~130/item across 13 items; 12 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the wemake.holiday MCP server?

wemake.holiday is a hosted endpoint at https://wemake.holiday/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 holiday-wemake-wemake-holiday 'https://wemake.holiday/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "holiday-wemake-wemake-holiday": {
      "url": "https://wemake.holiday/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "holiday-wemake-wemake-holiday": {
      "type": "http",
      "url": "https://wemake.holiday/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.holiday-wemake-wemake-holiday]
url = "https://wemake.holiday/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "holiday-wemake-wemake-holiday": {
      "type": "remote",
      "url": "https://wemake.holiday/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add holiday-wemake-wemake-holiday --url 'https://wemake.holiday/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  holiday-wemake-wemake-holiday:
    url: "https://wemake.holiday/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "holiday-wemake-wemake-holiday": {
      "Transport": "http",
      "Url": "https://wemake.holiday/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add holiday-wemake-wemake-holiday -t streamable-http -u 'https://wemake.holiday/mcp'
```

### Other

```json
{
  "mcpServers": {
    "holiday-wemake-wemake-holiday": {
      "type": "http",
      "url": "https://wemake.holiday/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-11-21 (score 80, +1)

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

### 2026-11-19 (score 79, +1)

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

### 2026-11-17 (score 78, +1)

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

### 2026-11-15 (score 77, +1)

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

### 2026-11-12 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-11 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 75)

First indexed and scored.

## MCP tools (12)

### `browse_hotels` (~173 tokens)

All hotels in a place

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.

Input parameters:

- `country` (string, required): country slug or ISO code, e.g. thailand
- `language` (string): answer language, ISO code (default en)
- `min_rating` (number): optional minimum guest rating (0-10)
- `min_stars` (number): optional minimum stars (1-5)
- `page` (integer): page (50 hotels each), default 1
- `place` (string, required): place slug from list_destinations, e.g. bangkok

Output parameters:

- `hotels` (null|array)
- `page` (integer)
- `pages` (integer)
- `place` (string)
- `total` (integer)
- `url` (string)

### `country_guide` (~121 tokens)

Travel guide for a country or place

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.

Input parameters:

- `language` (string): answer language; de uses German Wikivoyage, all others English (default en)
- `place` (string, required): country, region or city as its Wikivoyage article is called, e.g. Thailand, Tuscany, Lisbon

Output parameters:

- `guide` (string)
- `history_url` (string)
- `image` (null|object)
- `intro` (string)
- `license` (string)
- `sections` (null|array)
- `source` (string)
- `source_url` (string)
- `travel_warning` (string)
- `url` (string)

### `find_hotel` (~144 tokens)

Find a hotel by name

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.

Input parameters:

- `country` (string): optional ISO country code, e.g. TH — faster and more precise
- `language` (string): answer language, ISO code (default en)
- `name` (string, required): hotel name (typos are fine)
- `place` (string): optional city or district, e.g. Bangkok

Output parameters:

- `hotels` (null|array)
- `note` (string)

### `get_hotel` (~70 tokens)

Hotel details

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

Input parameters:

- `id` (string, required): hotel id from search_hotels
- `language` (string): answer language, ISO code (default en)

Output parameters:

- `address` (string)
- `checkin_time` (string)
- `checkout_time` (string)
- `city` (string)
- `country` (string)
- `description` (string)
- `facilities` (null|array)
- `id` (string)
- `lat` (number)
- `lon` (number)
- `name` (string)
- `rating` (number)
- `reviews` (integer)
- `stars` (number)
- `url` (string)

### `get_route_idea` (~67 tokens)

One travel route idea

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

Input parameters:

- `id` (integer, required): route id from list_route_ideas
- `language` (string): answer language, ISO code (default en)

Output parameters:

- `best_months` (string)
- `budget` (string)
- `days` (integer)
- `highlights` (null|array)
- `id` (integer)
- `pace` (string)
- `stations` (null|array)
- `summary` (string)
- `title` (string)
- `url` (string)

### `list_destinations` (~121 tokens)

Destinations with hotels

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.

Input parameters:

- `country` (string): optional: country slug or ISO code (e.g. thailand or TH) — then the places of that country are listed
- `language` (string): answer language, ISO code (default en)
- `limit` (integer): how many (1-200), default 50

Output parameters:

- `country` (string)
- `destinations` (null|array)
- `note` (string)
- `total` (integer)

### `list_route_ideas` (~127 tokens)

Travel route ideas

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.

Input parameters:

- `country` (string): optional ISO country code, e.g. TH or IT
- `language` (string): answer language, ISO code (default en)
- `limit` (integer): how many (1-30), default 12
- `topic` (string): optional topic keyword as used by wemake.holiday, e.g. wandern, kultur, strand

Output parameters:

- `routes` (null|array)
- `total` (integer)

### `plan_trip` (~161 tokens)

Plan a trip from existing route ideas

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.

Input parameters:

- `country` (string, required): ISO country code of the destination, e.g. TH, IT, PT
- `days` (integer): optional wished trip length in days; the closest existing route is chosen
- `language` (string): answer language, ISO code like en, de, fr (default en)
- `topic` (string): optional interest as used by wemake.holiday, e.g. strand, kultur, wandern, essen

Output parameters:

- `alternatives` (null|array)
- `best_months` (string)
- `budget` (string)
- `days` (integer)
- `highlights` (null|array)
- `note` (string)
- `pace` (string)
- `plan` (string)
- `route_id` (integer)
- `stations` (null|array)
- `summary` (string)
- `url` (string)

### `public_travel_diaries` (~92 tokens)

Public travel diaries

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

Input parameters:

- `country` (string): optional ISO country code, e.g. TH
- `language` (string): language of the links, ISO code (default en)
- `limit` (integer): how many (1-20), default 8

Output parameters:

- `diaries` (null|array)
- `note` (string)
- `total` (integer)

### `search_experiences` (~79 tokens)

Search tours and experiences

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

Input parameters:

- `language` (string): answer language, ISO code (default en)
- `place` (string, required): city or region, e.g. Rome or Koh Samui

Output parameters:

- `experiences` (null|array)
- `place` (string)

### `search_flights` (~153 tokens)

Search flights

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.

Input parameters:

- `adults` (integer): number of adults (1-9), default 1
- `depart_date` (string, required): outbound date YYYY-MM-DD
- `from` (string, required): departure airport IATA code, e.g. FRA
- `language` (string): answer language, ISO code (default en)
- `return_date` (string): optional return date YYYY-MM-DD (round trip)
- `to` (string, required): arrival airport IATA code, e.g. BKK

Output parameters:

- `flights` (null|array)
- `note` (string)

### `search_hotels` (~199 tokens)

Search hotels with live prices

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.

Input parameters:

- `adults` (integer): number of adults (1-9), default 2
- `checkin` (string, required): arrival date YYYY-MM-DD
- `checkout` (string, required): departure date YYYY-MM-DD
- `hotel_name` (string): optional: name of a specific hotel to find (typos are fine)
- `language` (string): answer language, ISO code like en, de, fr (default en)
- `place` (string, required): city, region, district or landmark, e.g. 'Bangkok Sukhumvit' or 'Koh Samui'

Output parameters:

- `hotels` (null|array)
- `nights` (integer)
- `note` (string)
- `place` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/holiday-wemake-wemake-holiday/wemake#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 77
- 2026-11-15: 77
- 2026-11-14: 76
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 75
- 2026-11-10: 75

## Common questions

### What is the wemake.holiday MCP server?

wemake.holiday is an MCP server listed in the public MCP registry as holiday.wemake/wemake-holiday. Hotels (2.8M directory + live prices), flights, tours, route ideas, travel guides – read-only. This page covers its hosted endpoint (https://wemake.holiday/mcp).

### Is the wemake.holiday MCP server safe to use?

wemake.holiday scores 80 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 wemake.holiday MCP server expose?

wemake.holiday exposes 12 tools: browse_hotels, country_guide, find_hotel, get_hotel, get_route_idea, and 7 more. Their descriptions and schemas cost roughly 1,507 tokens of context every time the server is loaded.

### Does the wemake.holiday MCP server require authentication?

No. We connected to wemake.holiday without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the wemake.holiday MCP server still maintained?

wemake.holiday is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the wemake.holiday MCP server?

VerifyMCP ran 14 checks on wemake.holiday, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://wemake.holiday/mcp
- Website: https://wemake.holiday/
- Changelog RSS feed: https://verifymcp.io/servers/holiday-wemake-wemake-holiday/wemake.xml
- Changelog JSON feed: https://verifymcp.io/servers/holiday-wemake-wemake-holiday/wemake/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/holiday-wemake-wemake-holiday/wemake.json
- HTML version of this page: https://verifymcp.io/servers/holiday-wemake-wemake-holiday/wemake
