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.

CielStay

REMOTE · MCP.CIELSTAY.COM

The free AI index for direct booking homes. Any channel, or straight to the host.

Available components

0 this week 85 Trust /100

Last scanned (20 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security74
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability72
  • 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 2925 tokens (~325/item across 9 items; 8 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

  • 13 Nov 26 0
    • Tool “contact_host” rewrote its description, which is the text the model reads security
    • Tool “search_vacation_rentals” rewrote its description, which is the text the model reads security
  • 12 Nov 26 0
    • Tool “contact_host” rewrote its description, which is the text the model reads security
    • Tool “get_listing_details” rewrote its description, which is the text the model reads security
    • Tool “search_vacation_rentals” rewrote its description, which is the text the model reads security
    • Schema quality: 2510 → 2919 ▼ functional
    • New tool “book_stay” functional
    • “contact_host” reworded the description of “guestEmail” cosmetic
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Tool “search_vacation_rentals” rewrote its description, which is the text the model reads security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://mcp.cielstay.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cielstay.com CN=WE1,O=Google Trust Services,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA256 6060d9604c3de88e0e3f7868605eb507
SANs: cielstay.com, *.cielstay.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.cielstay.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
cielstay.com. 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
www-authenticate Bearer realm="https://mcp.cielstay.com/mcp", resource_metadata="https://mcp.cielstay.com/.well-known/oauth-protected-resource/mcp"

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.cielstay.com/mcp Verified 200
http (plaintext) http://mcp.cielstay.com/mcp HTTPS enforced 301 https://mcp.cielstay.com/mcp
MCP tools · 8 exposed · ~2,911 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
book_stay ~329

Holds dates for the traveller at a home whose host offers "Book now" on CielStay (bookNow.available in get_listing_details): a Pro host whose calendar CielStay keeps in sync, within the host's limits (nights, lead time, guests, pets). guestEmail must be the traveller's own address: CielStay emails it a confirmation link, and the booking holds the dates for 30 minutes until the traveller confirms. On confirmation the dates are blocked on the host's calendar and the traveller receives the host's payment instructions. The booking and the payment are between the traveller and the host: CielStay is not a party to it and takes no payment. status "awaiting_guest_confirmation" on success; otherwise error explains why (dates taken, over the host's limits, calendar not confirmable just now) and contact_host remains available for a request instead. The reply's next describes what the traveller receives.

NameTypeReqDescription
checkInstringyesArrival date, YYYY-MM-DD
checkOutstringyesDeparture date, YYYY-MM-DD
guestEmailstringyesThe traveller's own email address: the confirmation link and the host's payment instructions go there
guestsinteger–Number of guests
listingIdstringyesThe home's CielStay id (or slug)
messagestring–A note to the host from the traveller (arrival time, who is coming)
namestring–The traveller's name, as the host will see it
petsinteger–Number of pets
NameTypeReqDescription
errorstring––
expiresAtstring––
messagestring––
nextstring––
statusstring––
successboolean––
totalnumber|null––

No examples provided.

contact_host ~371

Sends a traveller's first message to a home's host through CielStay: questions, dates and party, a request to book, or a monthly or long-stay inquiry. Free. guestEmail must be the traveller's own address: the host's reply goes there. Usually the message is sent at once (status "sent") and the traveller gets a "Sent" email with a link to the conversation; if the address already has a CielStay account, status is "awaiting_guest_confirmation" and the traveller confirms from an email link. The reply's `next` says what happens next. Available for homes that carry messageHostUrl: hostReach in the reply is "host" (the host manages the home on CielStay) or "possible_contact" (the message is emailed to the contact published on this home's booking site, who may not be the host and may not answer). For any other home it is refused with hostReach "none", and bookUrl is the way to the host. CielStay never takes bookings or payments; the host replies with their terms. Takes the id from search_vacation_rentals or get_listing_details. messageHostUrl is the same form for the traveller to send.

NameTypeReqDescription
checkInstring–Arrival date, YYYY-MM-DD
checkOutstring–Departure date, YYYY-MM-DD
guestEmailstringyesThe traveller's own email address: the host's reply comes there
guestsinteger–Number of guests
listingIdstringyesThe home's CielStay id (or slug)
messagestringyesThe message to the host, in the traveller's words: who is coming, why, and any questions
petsinteger–Number of pets
NameTypeReqDescription
errorstring––
hostOnCielStayboolean––
hostReachstring––
listingUrlstring––
nextstring––
statusstring––
successboolean––

No examples provided.

find_direct_booking ~456

Look up one named property and every way it can be booked, including the host's or manager's own site. Takes propertyName plus city (most reliable), or a listing URL from a booking platform, which is matched on its listing id. The response has answerType "lookup": a lookup about one property, not a ranked search. `confidence` describes the match: `exact-ota-id`, CielStay holds that exact listing; `exact-title`, the name matched but it is not confirmed to be the same property; `discovered-match`, CielStay does not hold it, but after reading the pasted link (title and location only) it found a booking-site page that agrees on name and place, which is likely but not certain; `none`, CielStay has no record, which does not show that no direct option exists. Every booking URL in the response is one CielStay holds or found; none is constructed. For a pasted link CielStay does not hold, the lookup reads that one page and searches live (up to about 20 seconds); `otaListing` shows what was read. When the answer is none, `alternatives` lists different, direct-bookable homes near `place` (matchType "alternative"), and `possibleMatches` lists the closest unconfirmed candidates by name and meaning (matchType "possible", no booking link, `matchScore` 0-1 is closeness, not proof). Readable version: https://www.cielstay.com/lookup?q=<name or link>.

NameTypeReqDescription
citystring–The city, to disambiguate a property name. Names repeat across towns.
otaUrlstring–The Airbnb or Vrbo URL the traveller is looking at. Paste it exactly as they gave it — tracking parameters and locale prefixes are fine. This is the most reliable input.
placestring–The town or area the traveller says the property is in. Only used to list direct-bookable alternatives near it when we do not hold the property; it never changes whether it matched.
propertyNamestring–The property name, if you have no URL. Exact spelling as shown on the OTA listing.
NameTypeReqDescription
answerTypestring––
confidencestring–exact-ota-id, exact-title, discovered-match or none
foundboolean––

No examples provided.

get_listing_details ~247

Full details for one CielStay listing: description, photos, amenities, house rules, location, and every booking link CielStay holds, including the host's own booking site; hostTrust says what CielStay checked about the host and carries the host's own statements (how they take bookings, payment, cancellation). With checkIn and checkOut, the response also carries liveQuote where the host's booking engine supports it: the total on the host's own site for those dates (room, fees and taxes), read live. Each live quote is a real request to the host's booking engine. Accepts the listing id, the slug from a listing URL, or a short code (the "1zwf" in cielstay.com/l/1zwf).

NameTypeReqDescription
checkInstring–Arrival date, YYYY-MM-DD. With checkOut, returns the live total from the host's own booking site.
checkOutstring–Departure date, YYYY-MM-DD.
guestsinteger–Number of guests, for the live quote. Defaults to 2.
idstringyesThe listing ID from a previous search result (result.id).
NameTypeReqDescription
amenities–––
bookNowobject–Present when the host offers Book now (book_stay): the host's limits for it
bookUrlstring––
bookingOptionsarray––
cielstayUrlstring––
descriptionstring|null––
foundboolean––
hostTrust––What CielStay checked about the host, and statements in the host's own words (fromHost; not checked by CielStay)
idstring––
imagesarray––
liveQuote––The total on the host's own site for the dates asked, read live; null when it couldn't be read
messagestring––
messageHostUrlstring––
priceobject––
priceNotestring––
titlestring|null––

No examples provided.

get_property ~185

Every unit at one multi-unit property: a hotel, glamping site or building whose units share a booking site and a location. Search results carry readyToBook.property.id when a home is one of several such units. Returns the property (name only where the operator's own unit titles share it), and each unit with its label, bedrooms, guests, CielStay page and readyToBook. With checkIn and checkOut, each unit's readyToBook also carries availability and the total on the host's site for those dates (up to 30 units).

NameTypeReqDescription
checkInstring–Arrival date, YYYY-MM-DD.
checkOutstring–Departure date, YYYY-MM-DD.
guestsinteger–Number of guests. Defaults to 2.
idstringyesThe property id (readyToBook.property.id from a search result).
NameTypeReqDescription
foundboolean––
messagestring––
propertyobject––
unitsarray––

No examples provided.

health_check ~24

Check that the CielStay MCP server is reachable and the API is healthy.

Input schema present but exposes no named parameters.

NameTypeReqDescription
statusstring––

No examples provided.

refine_search ~256

Refine a previous CielStay search in natural language, such as "more rustic", "closer to the park", "better views", "bigger place" or "with ping pong". For any follow-up that adds to or changes an earlier search in the conversation; keeps that search's place and dates. Takes the original query plus the refinement, and the earlier `currentIntent` as previousIntent; no session or token is needed.

NameTypeReqDescription
personastring–Carry the same persona through from the original search, if you sent one.
previousIntentobject–The `currentIntent` object from the previous response, if you still have it. Preserves location and dates across the refinement. Optional — omit it and the refinement still works.
querystringyesThe original search query you want to refine, exactly as you sent it before.
refinementstringyesNatural language refinement instruction. Examples: "more rustic and less modern", "closer to the water", "something with better views", "bigger — needs 3+ bedrooms".
travellerobject–The traveller fields from the original search, with anything the traveller has added since. Used for ranking and never stored.
NameTypeReqDescription
currentIntent––Pass to refine_search as previousIntent to keep place and dates
hasMoreboolean|null––
noticestring|null––
rankedForobject–What these results were ranked for: place, guests, dates, amenities, traveller
rankingQuestionstring–Present when nothing is known about the traveller: the question whose answer would most change this ranking. An answer can be sent as `traveller`
resultsarrayyes–
totalFoundnumber|null––

No examples provided.

search_vacation_rentals ~1,043

Search about 100,000 vacation rentals and longer-stay homes from independent hosts and property managers in 100 countries and territories. Each result lists the ways it can be booked that CielStay holds: the host's own booking site or engine (directUrl / referenceUrl), bookUrl (the same booking page opened through CielStay, which lets CielStay count the referral) and a CielStay listing page (cielstayUrl). CielStay does not take bookings or payments. Results are ranked by fit to the request, with a photo, a price (the average per night of a 3-night stay including the host's fees, before taxes; or per month for monthly homes) and a match score. Suited to finding a place to stay, or to checking whether a home seen on another site can be booked with its host. Follow-ups to a search ("with ping pong", "cheaper", "bigger") are handled by refine_search, or here with previousIntent; without either, a follow-up that names no place is searched everywhere. Each result carries bookUrl (the host's booking page) and, where someone can receive a message about the home, messageHostUrl and messageHost; for those, contact_host sends the traveller's message at once, free: the quickest way to ask about dates, pets or a monthly stay.

NameTypeReqDescription
checkinstring–Check-in date in YYYY-MM-DD format. Omit if flexible or unknown.
checkoutstring–Check-out date in YYYY-MM-DD format. Omit if flexible or unknown.
guestsinteger–Number of guests. Defaults to 2 if omitted.
intentobject–OPTIONAL FAST PATH. If you have already parsed the traveller's request, send it here and CielStay skips its own parse — measured 2.3s to 0.06s with identical results. Shape: {"vibePrefs":["quiet","ru…
limitinteger–Number of results to return (1–20). Default 5.
maxPricePerNightnumber–Maximum nightly price in USD.
minBedroomsinteger–Minimum number of bedrooms required.
mustHaveAmenitiesarray–Amenities the listing must have, in plain English. Filterable: hot tub, pool, kitchen, washer/dryer, air conditioning, parking, workspace, waterfront, EV charger, pet friendly. Anything else is repor…
personastring–Who the guest is, in a few sentences of plain prose — what they like, what the trip is for, and what they want to avoid. CielStay embeds this and ranks on it, so it changes which homes come back rath…
previousIntentobject–The `currentIntent` from the previous CielStay search in this conversation, when this request follows on from it ("with a pool", "cheaper", "that area but bigger"). Keeps its place, party and dates;…
querystringyesNatural language search query: location, dates, group, and what the stay is for. Examples: "cozy cabin near Zion National Park for a couple", "pet-friendly beachfront with a hot tub in Hawaii", "mode…
sourcestring–Limit results to homes from one booking source we hold: a booking-engine or host-site name ("guesty", "hospitable", "escapia", a host brand such as "haven") or its domain; a comma list for several. T…
travellerobject–What the traveller has said about who is going and what they want, in short fields (any subset). Preferences only, not names, contact details or health information. Used for ranking and never stored;…
NameTypeReqDescription
currentIntent––Pass to refine_search as previousIntent to keep place and dates
hasMoreboolean|null––
noticestring|null––
rankedForobject–What these results were ranked for: place, guests, dates, amenities, traveller
rankingQuestionstring–Present when nothing is known about the traveller: the question whose answer would most change this ranking. An answer can be sent as `traveller`
resultsarrayyes–
totalFoundnumber|null––

No examples provided.

Install

How do I install the CielStay MCP server?

CielStay is a hosted endpoint at https://mcp.cielstay.com/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 · mcp.cielstay.com

# add to Claude Code
claude mcp add --transport http com-cielstay-cielstay 'https://mcp.cielstay.com/mcp'
Common questions

What is the CielStay MCP server?

CielStay is an MCP server listed in the public MCP registry as com.cielstay/cielstay. The free AI index for direct booking homes. Any channel, or straight to the host. This page covers its hosted endpoint (https://mcp.cielstay.com/mcp).

Is the CielStay MCP server safe to use?

CielStay scores 85 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 CielStay MCP server expose?

CielStay exposes 8 tools: search_vacation_rentals, refine_search, get_listing_details, contact_host, book_stay, and 3 more. Their descriptions and schemas cost roughly 2,911 tokens of context every time the server is loaded.

Does the CielStay MCP server require authentication?

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

Is the CielStay MCP server still maintained?

CielStay 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 CielStay MCP server?

VerifyMCP ran 14 checks on CielStay, 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.