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.

OpenStays Property Passports

REMOTE · OPENSTAYS.AI

Search short-term rentals worldwide and book directly with the owner. Free and read-only, no key.

Available components

69 Trust /100

Last scanned (12 hours ago)

Scores higher than 53% 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 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 Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1370 tokens (~685/item across 2 items; 2 tools + 0 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 Management0
  • Stability check failed: schema churn in the 4 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
  • 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

Checks we ran (13)

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

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.

  • 20 Nov 26 −10
    • Authorization: pass → partial ▼ security
    • Stability: 0.07 → fail ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_property_passport” rewrote its description, which is the text the model reads security
    • Tool “search_stays” rewrote its description, which is the text the model reads security
    • Schema quality: 166 → 685 ▼ functional
    • Schema quality: 166 → 797 ▼ functional
    • “get_property_passport” added a required parameter “passportId”, so existing callers break ▼ functional
    • “get_property_passport” dropped the required parameter “profileUrl” ▼ functional
    • Tool coverage: 50% → 89% ▲ functional
    • Tool “get_property_passport” now declares an output schema ▲ functional
    • Tool “search_stays” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Schema quality: good → excellent functional
    • Server version: 2.0.0 → 2.0.1 functional
    • Server version: 1.0.0 → 2.0.0 functional
    • “search_stays” added an optional parameter “amenities” cosmetic
    • “search_stays” added an optional parameter “bedrooms” cosmetic
    • “search_stays” added an optional parameter “bookingConfirmation” cosmetic
    • “search_stays” added an optional parameter “businessTravel” cosmetic
    • “search_stays” added an optional parameter “cancellationCategory” cosmetic
    • “search_stays” added an optional parameter “checkIn” cosmetic
    • “search_stays” added an optional parameter “checkOut” cosmetic
    • “search_stays” added an optional parameter “children” cosmetic
    • “search_stays” added an optional parameter “currency” cosmetic
    • “search_stays” added an optional parameter “events” cosmetic
    • “search_stays” added an optional parameter “families” cosmetic
    • “search_stays” added an optional parameter “longStays” cosmetic
    • “search_stays” added an optional parameter “maxMinimumStayNights” cosmetic
    • “search_stays” added an optional parameter “maxPricePerNight” cosmetic
    • “search_stays” added an optional parameter “minBathrooms” cosmetic
    • “search_stays” added an optional parameter “minBeds” cosmetic
    • “search_stays” added an optional parameter “name” cosmetic
    • “search_stays” added an optional parameter “page” cosmetic
    • “search_stays” added an optional parameter “pets” cosmetic
    • “search_stays” added an optional parameter “smoking” cosmetic
    • “search_stays” added an optional parameter “weddings” cosmetic
    • “get_property_passport” reworded the description of “passportId” cosmetic
    • “search_stays” reworded the description of “country” cosmetic
    • “search_stays” reworded the description of “minBedrooms” cosmetic
  • 19 Nov 26 +1

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

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 78

    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://openstays.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=openstays.ai CN=YR1,O=Let's Encrypt,C=US 1 Nov 2026 30 Jan 2027 RSA 2048 SHA256-RSA 573afe4c2e7ae9be5ba1b63c13f309c3b88
SANs: openstays.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of openstays.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
openstays.ai. 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=63072000
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://openstays.ai/api/mcp Verified 200
http (plaintext) http://openstays.ai/api/mcp HTTPS enforced 308 https://openstays.ai/api/mcp
MCP tools · 2 exposed · ~1,158 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
get_property_passport ~113

Retrieve one Property Passport in full by the passportId of a search_stays result: every fact the owner states, the photos, and the owner's own booking channels in contact_routes, where the guest books. The Passport follows the schema at https://openstays.ai/passport-schema/latest/passport.schema.json, without the addresses of its own pages.

NameTypeReqDescription
passportIdstringyesThe passportId of a search_stays result, exactly as returned, or the link of a Passport page that the user gave.
NameTypeReqDescription
amenity_codes––The amenities the owner states.
availability––Booked dates from the owner's own calendar, when the owner shares one.
cancellation_policy––The owner's cancellation terms, when published.
contact_routes––The owner's own booking channels, where the guest books, in the owner's order.
information––The owner's own notes on amenities, spaces, prices and fees, booking rules and policies.
key_facts––Check-in and check-out times, house rules, minimum stay, lowest published price and cancellation category.
location––Country, region and town.
passport––Name, scope, number of units and where the facts come from.
photos––The property's photos.
rates––The owner's published rates. Not a live quote.
schema_versionstring––
units––Each accommodation unit: type, bedrooms, beds, bathrooms and guests.

No examples provided.

search_stays ~1,045

Search public OpenStays Property Passports: short-term rentals that guests book directly with the owner. It searches the whole world or one country, region or town, by a property's name, and by any fact a Passport states: bedrooms, bathrooms, beds, guests, property type, amenities such as a pool or a sea view, house rules such as pets, and booking terms. Every argument is optional and each one narrows the search. A property's name alone finds it. bedrooms is an exact number and minBedrooms is a minimum. A fact matches only when the owner's Passport states it, so a filter can miss a home whose Passport does not mention that fact. It returns only the accommodation units that match everything asked for, at most 10 at a time and often fewer, preferring different Property Passports, and it never adds results to reach 10. nextPage is the number of the next page, or null when there are no more. There is no catalogue export or total count. With checkIn and checkOut it returns only homes whose owner's calendar shows those nights free, and with maxPricePerNight and currency only homes whose published nightly price is within that budget, in any currency. Many Passports do not share a calendar or publish a price yet, so a search by dates or by budget leaves those homes out, and for them the guest asks the owner. A price is the owner's published rate, not a live quote: the owner confirms the price and the booking. Guests book with the owner: each result's bookingUrl is the owner's own website, and when it is null, contactRoutes has the owner's other booking channels. Each result's passportId names its full Passport.

NameTypeReqDescription
amenitiesarray–Amenities the home must have, all of them, for example ["pool", "wifi"].
bedroomsinteger–Exactly this many bedrooms. For a five-bedroom house, send 5.
bookingConfirmationstring–instant: a booking is confirmed at once. on_request: the owner confirms it.
businessTravelboolean–Only homes whose Passport says they suit business travel.
cancellationCategoryarray–The cancellation terms you accept, for example ["flexible", "moderate"].
checkInstring–The arrival day, as YYYY-MM-DD. Send it with checkOut.
checkOutstring–The departure day, as YYYY-MM-DD, at most 90 nights after checkIn.
childrenarray–The owner's rule on children. List every answer you accept, for example ["allowed", "by_request"]. by_request means the owner decides case by case.
countrystring–One country or territory name or supported exact alias, for example New Zealand or NZ. Leave it out to search every country.
currencystring–The currency of maxPricePerNight, as a three-letter code such as USD. It can differ from the owner's currency: the budget is converted with the day's reference rates.
destinationstring–A country, locality or region. Without country, this must identify one country among public Passport locations. With country, use this for an optional locality or region.
eventsarray–The owner's rule on events and parties. List every answer you accept, for example ["allowed", "by_request"]. by_request means the owner decides case by case.
familiesboolean–Only homes whose Passport says they suit families.
longStaysboolean–Only homes whose Passport says they suit long stays.
maxMinimumStayNightsinteger–The longest minimum stay the guest accepts, in nights. For a three-night trip, send 3.
maxPricePerNightnumber–The most the guest wants to pay for one night. Send it with currency. With dates it is compared with the published price for those nights, otherwise with the lowest published nightly price.
minBathroomsnumber––
minBedroomsinteger–At least this many bedrooms. Never send it together with bedrooms.
minBedsinteger––
minGuestsinteger––
namestring–The name of one property, or part of it, for example Hinterland Harmony. You can search by name alone, without giving a country.
pageinteger–The page of results, starting at 1. Send the nextPage value of the previous answer. Needs at least one other argument.
petsarray–The owner's rule on pets. List every answer you accept, for example ["allowed", "by_request"]. by_request means the owner decides case by case.
propertyTypestring–Public accommodation type, for example villa or cottage.
smokingarray–The owner's rule on smoking. List every answer you accept, for example ["allowed", "by_request"]. by_request means the owner decides case by case.
weddingsarray–The owner's rule on weddings. List every answer you accept, for example ["allowed", "by_request"]. by_request means the owner decides case by case.
NameTypeReqDescription
nextPage––Send as page to see more. Null when there are no more.
noticesarray–What a search by dates or by price could not check.
refineSearchboolean–True when more homes matched than one answer holds.
resultsarrayyesThe accommodation units that match everything asked for, at most 10 at a time.

No examples provided.

Install

How do I install the OpenStays Property Passports MCP server?

OpenStays Property Passports is a hosted endpoint at https://openstays.ai/api/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 · openstays.ai

# add to Claude Code
claude mcp add --transport http ai-openstays-property-passports 'https://openstays.ai/api/mcp'
Common questions

What is the OpenStays Property Passports MCP server?

OpenStays Property Passports is an MCP server listed in the public MCP registry as ai.openstays/property-passports. Search short-term rentals worldwide and book directly with the owner. Free and read-only, no key. This page covers its hosted endpoint (https://openstays.ai/api/mcp).

Is the OpenStays Property Passports MCP server safe to use?

OpenStays Property Passports scores 69 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 OpenStays Property Passports MCP server expose?

OpenStays Property Passports exposes 2 tools: search_stays, get_property_passport. Their descriptions and schemas cost roughly 1,158 tokens of context every time the server is loaded.

Does the OpenStays Property Passports MCP server require authentication?

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

Is the OpenStays Property Passports MCP server still maintained?

OpenStays Property Passports 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 OpenStays Property Passports MCP server?

VerifyMCP ran 13 checks on OpenStays Property Passports, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.