Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

wemake.holiday

REMOTE · WEMAKE.HOLIDAY

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

Available components

+4 this week 80 Trust /100

Last scanned (22 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 12 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 75

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://wemake.holiday/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wemake.holiday CN=YE1,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA384 522e7b9bfec5b9512a70582c79fdda2f688
SANs: wemake.holiday
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 insecure

Validation of wemake.holiday. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
holiday. DS published 9971 8 Verified
wemake.holiday. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(self), microphone=(), geolocation=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://wemake.holiday/mcp Verified 200
http (plaintext) http://wemake.holiday/mcp HTTPS enforced 308 https://wemake.holiday/mcp
MCP tools · 12 exposed · ~1,507 tokens

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 →

Tool Tokens
browse_hotels ~173

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.

NameTypeReqDescription
countrystringyescountry slug or ISO code, e.g. thailand
languagestring–answer language, ISO code (default en)
min_ratingnumber–optional minimum guest rating (0-10)
min_starsnumber–optional minimum stars (1-5)
pageinteger–page (50 hotels each), default 1
placestringyesplace slug from list_destinations, e.g. bangkok
NameTypeReqDescription
hotelsnull|arrayyes–
pageintegeryes–
pagesintegeryes–
placestringyes–
totalintegeryes–
urlstringyes–

No examples provided.

country_guide ~121

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.

NameTypeReqDescription
languagestring–answer language; de uses German Wikivoyage, all others English (default en)
placestringyescountry, region or city as its Wikivoyage article is called, e.g. Thailand, Tuscany, Lisbon
NameTypeReqDescription
guidestringyes–
history_urlstring––
imagenull|object––
introstring––
licensestringyes–
sectionsnull|array––
sourcestringyes–
source_urlstringyes–
travel_warningstring––
urlstringyes–

No examples provided.

find_hotel ~144

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.

NameTypeReqDescription
countrystring–optional ISO country code, e.g. TH — faster and more precise
languagestring–answer language, ISO code (default en)
namestringyeshotel name (typos are fine)
placestring–optional city or district, e.g. Bangkok
NameTypeReqDescription
hotelsnull|arrayyes–
notestring––

No examples provided.

get_hotel ~70

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

NameTypeReqDescription
idstringyeshotel id from search_hotels
languagestring–answer language, ISO code (default en)
NameTypeReqDescription
addressstring––
checkin_timestring––
checkout_timestring––
citystring––
countrystring––
descriptionstring––
facilitiesnull|array––
idstringyes–
latnumber––
lonnumber––
namestringyes–
ratingnumber––
reviewsinteger––
starsnumber––
urlstringyes–

No examples provided.

get_route_idea ~67

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

NameTypeReqDescription
idintegeryesroute id from list_route_ideas
languagestring–answer language, ISO code (default en)
NameTypeReqDescription
best_monthsstring––
budgetstring––
daysinteger––
highlightsnull|array––
idintegeryes–
pacestring––
stationsnull|array––
summarystring––
titlestringyes–
urlstringyes–

No examples provided.

list_destinations ~121

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.

NameTypeReqDescription
countrystring–optional: country slug or ISO code (e.g. thailand or TH) — then the places of that country are listed
languagestring–answer language, ISO code (default en)
limitinteger–how many (1-200), default 50
NameTypeReqDescription
countrystring––
destinationsnull|arrayyes–
notestring––
totalintegeryes–

No examples provided.

list_route_ideas ~127

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.

NameTypeReqDescription
countrystring–optional ISO country code, e.g. TH or IT
languagestring–answer language, ISO code (default en)
limitinteger–how many (1-30), default 12
topicstring–optional topic keyword as used by wemake.holiday, e.g. wandern, kultur, strand
NameTypeReqDescription
routesnull|arrayyes–
totalintegeryes–

No examples provided.

plan_trip ~161

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.

NameTypeReqDescription
countrystringyesISO country code of the destination, e.g. TH, IT, PT
daysinteger–optional wished trip length in days; the closest existing route is chosen
languagestring–answer language, ISO code like en, de, fr (default en)
topicstring–optional interest as used by wemake.holiday, e.g. strand, kultur, wandern, essen
NameTypeReqDescription
alternativesnull|array––
best_monthsstring––
budgetstring––
daysinteger––
highlightsnull|array––
notestring––
pacestring––
planstringyes–
route_idintegeryes–
stationsnull|arrayyes–
summarystring––
urlstringyes–

No examples provided.

public_travel_diaries ~92

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

NameTypeReqDescription
countrystring–optional ISO country code, e.g. TH
languagestring–language of the links, ISO code (default en)
limitinteger–how many (1-20), default 8
NameTypeReqDescription
diariesnull|arrayyes–
notestring––
totalintegeryes–

No examples provided.

search_experiences ~79

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

NameTypeReqDescription
languagestring–answer language, ISO code (default en)
placestringyescity or region, e.g. Rome or Koh Samui
NameTypeReqDescription
experiencesnull|arrayyes–
placestring––

No examples provided.

search_flights ~153

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.

NameTypeReqDescription
adultsinteger–number of adults (1-9), default 1
depart_datestringyesoutbound date YYYY-MM-DD
fromstringyesdeparture airport IATA code, e.g. FRA
languagestring–answer language, ISO code (default en)
return_datestring–optional return date YYYY-MM-DD (round trip)
tostringyesarrival airport IATA code, e.g. BKK
NameTypeReqDescription
flightsnull|arrayyes–
notestring––

No examples provided.

search_hotels ~199

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.

NameTypeReqDescription
adultsinteger–number of adults (1-9), default 2
checkinstringyesarrival date YYYY-MM-DD
checkoutstringyesdeparture date YYYY-MM-DD
hotel_namestring–optional: name of a specific hotel to find (typos are fine)
languagestring–answer language, ISO code like en, de, fr (default en)
placestringyescity, region, district or landmark, e.g. 'Bangkok Sukhumvit' or 'Koh Samui'
NameTypeReqDescription
hotelsnull|arrayyes–
nightsinteger––
notestring––
placestringyes–

No examples provided.

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.

remote · wemake.holiday

# add to Claude Code
claude mcp add --transport http holiday-wemake-wemake-holiday 'https://wemake.holiday/mcp'
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.