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.

travel.kismet/mcp-server

REMOTE · MCP.KISMET.TRAVEL · 2 COMPONENTS

Semantic hotel search with real-time availability and price comparison for Kismet Travel

0 this week 84 Trust /100

Last scanned (19 hours ago)

Scores higher than 84% 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 Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6256 tokens (~297/item across 21 items; 15 tools + 6 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
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
  • 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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 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
  • 2 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 29 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “sign_in_agent” functional
    • New tool “verify_agent_inbox” functional
  • 28 Sept 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
  • 25 Sept 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
  • 26 Aug 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.kismet.travel/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kismet.travel CN=WE1,O=Google Trust Services,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA256 d0895524474e61f113a2d54c23452c35
SANs: kismet.travel, *.kismet.travel
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.kismet.travel. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
travel. DS published 589 8 Verified
kismet.travel. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.kismet.travel/mcp Verified 200
http (plaintext) http://mcp.kismet.travel/mcp HTTPS enforced 301 https://mcp.kismet.travel/mcp
MCP tools · 15 exposed · ~4,961 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
build_bookable_carousel ~412

Present a curated set of specific properties as an interactive visual carousel. Pass `propertySlugs` in your chosen order, plus the collection_id(s) those properties belong to in `collections` — you get each candidate's collectionSlug from search_bookables. The picks MAY span multiple managers: pass ALL their collection_ids and the carousel renders them together with manager filter cards. Never fall back to a plain text list for a cross-manager set — this tool handles it. Call AFTER search_bookables.

NameTypeReqDescription
checkInstring–Check-in date for live pricing
checkOutstring–Check-out date for live pricing
collectionsarray–Collection slug(s) — each a `collection_id` from list_collections. For search_bookables and discover_collections: OMIT to span the whole network, pass one to scope to a single manager, or several to…
contextstring–Optional: the guest's needs/criteria behind these picks (e.g., "Best options for a family of 6 with dogs in Vermont"). Used by the backend as a search/personalization hint — recorded on the guest's j…
guestsnumber–Number of guests
propertySlugsarrayyesOrdered array of property slugs to present. The carousel preserves this order. Max 10.
semanticFiltersobject–Reserved optional evidence-backed semantic criteria that complement the explicit location, date, capacity, pet, property-type, and budget filters. Put true must-haves in `required`; put preferences t…
NameTypeReqDescription
appliedSearchParamsobject–Optional echo of the structured and semantic search criteria used to produce these picks, for widget refresh continuity.
bookingBaseUrlstring–Base URL for booking redirects.
collectionobjectyes–
collectionsarray–Manager branding and aggregate context for collection filter cards.
datesobject––
guestsnumber–Echo of the applied party size (widget header seed).
llmContextstring–Echo of the input `context` (search/personalization hint). Carried in widget state for refresh continuity; not rendered to the guest.
multiCollectionboolean–True when the carousel contains properties from multiple managers.
propertyPicksobjectyes–
reviewsobject|null––
semanticFilteringobject–Optional semantic-filtering summary. Omitted until semantic matching is enabled and the criteria have actually been evaluated.
successbooleanyes–
suggestedFollowUpsarray––
typestringyesWidget type discriminator (discoverVrm).

No examples provided.

discover_collections ~1,124

Visually discover bookable-stay managers (collections) and their properties as an interactive carousel. OMIT `collections` to discover across the whole network (the widget shows manager filter cards plus an interleaved property carousel), pass one to feature a single manager, or several to compare. Each property card opens full details. Use this for browsing/visual presentation; use search_bookables when the guest has specific filters and you want ranked text candidates.

NameTypeReqDescription
bedroomsnumber–Minimum bedrooms needed
budgetMaxPerNightnumber–Max nightly budget in major currency units
checkInstring–Check-in date (YYYY-MM-DD)
checkOutstring–Check-out date (YYYY-MM-DD)
collectionsarray–Collection slug(s) — each a `collection_id` from list_collections. For search_bookables and discover_collections: OMIT to span the whole network, pass one to scope to a single manager, or several to…
countrystring–Filter by ISO 3166-1 alpha-2 country code (e.g., "US"). Rarely needed since collections are typically in one country.
featurestring–Soft ranking signal — boost properties with a guest-confirmed feature. Does NOT hard-filter. Example values: "mountain_views", "spotless_clean", "amazing_host", "cozy", "beachfront", "stocked_kitchen…
guestsnumber–Number of guests
localityarray–Filter by city or town name (e.g., ["Stowe"], ["Seaside", "Cannon Beach"]). Case-insensitive. Use instead of geo when a guest asks for a specific town.
maxPropertiesnumber–Max property picks to return. Default 5.
neLatnumber–BOUNDS MODE: Northeast corner latitude. Required with swLat.
neLngnumber–BOUNDS MODE: Northeast corner longitude. Required with swLat.
nearLatnumber–POINT MODE: Latitude to search near (e.g. 35.789). Use for specific places like a town, address, or landmark. Resolve place names to coordinates before calling. For broad areas (coastlines, mountain…
nearLngnumber–POINT MODE: Longitude to search near (e.g. -83.534). Required when nearLat is provided.
nearRadiusnumber–POINT MODE: Max distance from the nearLat/nearLng point in nearUnit. Default 25 miles. Use 50+ for broad areas.
nearUnitstring–Unit for nearRadius and distance values. Default "miles".
offsetnumber–Skip this many results (for pagination / load-more). Default 0.
personastring–Soft ranking signal — boost properties popular with a guest persona. Does NOT hard-filter. Example values: "hiking", "young_family", "romantic", "pet_owners", "fishing", "honeymoon", "luxury", "foodi…
petsRequiredboolean–Whether guest needs pet-friendly property
preferencesstring–Free text preferences (e.g., "hot tub, mountain view")
propertySlugsarray–REPRICE / REHYDRATE mode (the carousel widget's date-change refresh). When set, return EXACTLY these properties re-priced for the dates, in this order — dropping any now unavailable for the dates and…
propertyTypesarray–Property type(s). The coarse family (house vs apartment) is the only hard filter; a specific subtype (e.g. "cabin", "a-frame") returns its whole family with that subtype boosted — cross-manager inter…
regionarray–Filter by state or region name (e.g., ["Vermont"], ["Vermont", "New Hampshire"]). Case-insensitive. Use this instead of bounding box when a guest asks for a specific state.
semanticFiltersobject–Reserved optional evidence-backed semantic criteria that complement the explicit location, date, capacity, pet, property-type, and budget filters. Put true must-haves in `required`; put preferences t…
sleepsnumber–Minimum sleeping capacity required (filters properties that sleep at least this many)
swLatnumber–BOUNDS MODE: Southwest corner latitude. Use bounding box for geographic regions like coastlines, mountain ranges, lake shores, or any area that is not a single point. Example: Oregon coast → swLat=42…
swLngnumber–BOUNDS MODE: Southwest corner longitude. Required with swLat.
NameTypeReqDescription
appliedSearchParamsobject–Echo of the search filters that were applied for widget round-trips.
bookingBaseUrlstring––
collectionobjectyes–
collectionsarray–Manager branding and aggregate context for collection filter cards.
datesobject––
guestsnumber–Echo of the applied party size (widget header seed).
multiCollectionboolean–True when the carousel contains properties from multiple managers.
propertyPicksobjectyes–
reviewsobject|null––
semanticFilteringobject–Optional semantic-filtering summary. Omitted until semantic matching is enabled and the criteria have actually been evaluated.
successbooleanyes–
suggestedFollowUpsarrayyes–
typestringyesWidget type discriminator (discoverVrm).

No examples provided.

get_bookable_detail ~189

Returns full details for a specific vacation rental property: description, bedrooms, bathrooms, kitchen, outdoor spaces, features, policies, and recent reviews. Use when a guest wants to know more about a specific property.

NameTypeReqDescription
checkInstring–Check-in date for pricing
checkOutstring–Check-out date for pricing
collectionsarray–Collection slug(s) — each a `collection_id` from list_collections. For search_bookables and discover_collections: OMIT to span the whole network, pass one to scope to a single manager, or several to…
propertySlugstringyesSlug of the vacation rental property
NameTypeReqDescription
alternateDateWindowsarray–Nearest bookable windows for THIS property when the requested dates are unavailable.
detailUrlstring––
membershipobject–Optional collection membership metadata. Anonymous responses may expose availability, but member pricing is populated only for authenticated guests.
propertyobjectyes–
reviewsobject––
similarAvailablearray–Nearest collection siblings that ARE available for the requested dates.
typestringyesAlways "vrDetail".

No examples provided.

get_bookable_reviews ~259

Get guest reviews for a specific vacation rental property or for the entire collection. Returns a summary and individual review texts that can be used to answer questions about guest experiences.

NameTypeReqDescription
collectionsarray–Collection slug(s) — each a `collection_id` from list_collections. For search_bookables and discover_collections: OMIT to span the whole network, pass one to scope to a single manager, or several to…
limitnumber–Number of reviews to return (default 5, max 20).
offsetnumber–Number of reviews to skip for pagination (default 0).
personastring–Filter to reviews from a guest persona type (e.g. "family", "couples", "solo").
propertySlugstring–Slug of the specific property to get reviews for. If omitted, returns collection-level reviews.
seasonstring–Filter to reviews from a specific season.
sortstring–How to sort reviews (default newest).
NameTypeReqDescription
collectionobject––
paginationobjectyes–
reviewsarrayyes–
scopestringyes–
scopeSlugstring––
successbooleanyes–
summaryobjectyes–
typestringyesAlways "vrReviews".

No examples provided.

get_booking_link ~236

Returns a booking link for a specific vacation rental property. Use when a guest is ready to book. When dates are provided they are validated against the property's booking rules (availability, minimum/maximum stay, arrival/departure restrictions); if the stay is not bookable, the result carries datesRejected with the reason and up to three alternate date windows — offer those to the guest instead.

NameTypeReqDescription
checkInstring–Check-in date (YYYY-MM-DD)
checkOutstring–Check-out date (YYYY-MM-DD)
collectionsarray–Collection slug(s) — each a `collection_id` from list_collections. For search_bookables and discover_collections: OMIT to span the whole network, pass one to scope to a single manager, or several to…
guestsnumber–Number of guests
propertySlugstringyesSlug of the vacation rental
NameTypeReqDescription
alternateDateWindowsarray–Up to three nearest bookable windows of the same length (only when datesRejected).
bookingUrlstringyesURL the guest can follow to book.
datesRejectedboolean–True when the requested dates violate the property's booking rules; bookingUrl is then the undated property page.
propertySlugstringyes–
rejectionReasonstring–Why the requested stay is not bookable (only when datesRejected).
typestringyesAlways "bookingLinkVrm".

No examples provided.

get_collection_content ~179

Returns collection-level content for a VRM. Sections: "about" (collection info), "reviews" (guest reviews with ratings). Use for guest questions about the company, area, or review quality.

NameTypeReqDescription
collectionsarray–Collection slug(s) — each a `collection_id` from list_collections. For search_bookables and discover_collections: OMIT to span the whole network, pass one to scope to a single manager, or several to…
limitnumber–Max items for reviews. Default 10.
offsetnumber–Pagination offset
sectionstringyesContent section
NameTypeReqDescription
dataobject–Collection metadata for the "about" section.
limitnumber––
membershipobject–Optional collection membership metadata. Anonymous responses may expose availability, but member pricing is populated only for authenticated guests.
offsetnumber––
reviewsarray––
sectionstringyes–
summaryobject–Review aggregates for the "reviews" section.
totalnumber––
typestringyesAlways "vrmContent".

No examples provided.

get_guest_profile ~319

Get the signed-in user / guest Kismet account profile, identity, preferences, and account-level signals. Returns the currently authenticated user's (the logged-in guest's) Kismet profile: identity (first name), contact-channel status (whether an email / phone is on file and verified — never the raw values), account-level signals (linked property managers and collections the user has transacted with, plus membership status — which collections the user is an Insider member of), per-collection stay history (past and upcoming bookings with property names and dates), and a cross-collection activity summary (booking counts, last active, last booked across the Kismet network). Use this whenever the user wants to see their account, profile, or saved preferences, or whenever you need to personalize search results and recommendations for the signed-in user — common queries: "what does my profile look like", "who am I logged in as", "show my Kismet account", "check my preferences", "am I signed in", "personalize this for me". Returns an explicit anonymous state when no user is signed in. Anonymous browsing, search, and shortlisting are fully supported, so sign-in is not required for those flows. When `auth_state` is "anonymous", personal-account data (profile and identity, past stays and bookings, Insider memberships) is unavailable until the user signs in; the separate `sign_in` tool initiates the OAuth flow when the user wants to access it. This tool only READS the current auth state and never signs the user in.

Input schema present but exposes no named parameters.

NameTypeReqDescription
account_statusobjectyes–
activity_summaryobjectyes–
assistant_guidancestring–Behavioral hints for the assistant (greeting, anonymous don't-prompt-sign-in rules, how to read collections[]). Not guest PII.
auth_statestringyesWhen 'anonymous', identity flags are false/null. If the user is asking about THEIR personal data, offer to call sign_in.
collectionsarray–Per-collection itemized stay history. Each entry's `stays` array lists the guest's bookings at that collection (property name + slug, check-in/out, nights, status). Use to answer 'my past stays with…
communicationobject––
identityobjectyes–
membershipsarray–The guest's Insider memberships — the collections they belong to (with status, tier, and member-since). Empty when anonymous or not a member of any. Use it to tell the guest which collections they're…
preferencesobject––
shortlist_countnumber|null––

No examples provided.

get_shortlist ~154

Show the guest's saved/shortlisted vacation rental properties for this collection. Call this when the user wants to see their saved properties or review their shortlist.

NameTypeReqDescription
collectionsarray–Collection slug(s) — each a `collection_id` from list_collections. For search_bookables and discover_collections: OMIT to span the whole network, pass one to scope to a single manager, or several to…
limitnumber–Maximum number of saved properties to return (default 20).
NameTypeReqDescription
collectionobject––
emptyMessagestring––
isEmptybooleanyes–
itemsarrayyes–
successbooleanyes–
totalSavednumber––
typestringyesAlways "shortlistVrm".

No examples provided.

list_collections ~183

Search the Kismet network for vacation-rental collections (property managers). Returns ranked collections with their slug (`collection_id`), regions, property count, and supported tools. Use this when the guest asks which managers operate in a place or wants to choose a manager. It is not required before network-wide search: search_bookables and discover_collections span every collection when `collections` is omitted. Searchable via free-text `query` plus optional `region`/`category` filters — not a full dump.

NameTypeReqDescription
categorystring–Filter by category, e.g. "vacation_rental".
limitnumber–Max results (default 20).
querystring–Free-text search across name, region, and description.
regionstring–Filter by region, state, or country (e.g. "Oregon").
NameTypeReqDescription
collectionsarrayyesRanked collections matching the query / filters.
successbooleanyes–
totalnumber––

No examples provided.

search_bookables ~822

Primary search tool — use this whenever the guest specifies ANY filter: location, dates, budget, bedrooms, pets, or persona. Returns a ranked list of candidate properties as plain text with each property's slug, name, location, dated or anchor pricing, top personas/features, and tagline — formatted so the LLM can read and reason over them directly. After picking your top candidates from the returned list, pass their slugs to build_bookable_carousel to render them visually for the guest. Supports up to 5 date windows in a single call (e.g. compare March 15-18 vs March 22-25) and all location modes (region, point+radius, bounding box).

NameTypeReqDescription
bedroomsnumber–Minimum bedrooms needed
budgetMaxPerNightnumber–Max nightly budget in major currency units
collectionsarray–Collection slug(s) — each a `collection_id` from list_collections. For search_bookables and discover_collections: OMIT to span the whole network, pass one to scope to a single manager, or several to…
countrystring–Filter by ISO alpha-2 country code (e.g., "US")
dateWindowsarray–Up to 5 date windows to check availability and pricing across. Each window returns per-property availability. Omit for browse mode — browse results carry the nightly anchor "from" price only, never a…
featurestring–Soft ranking signal — boost properties with a guest-confirmed feature (e.g., "mountain_views", "spotless_clean", "hot_tub", "cozy", "beachfront"). Does NOT hard-filter.
guestsnumber–Number of guests
localityarray–Filter by city/town name (e.g., ["Stowe"], ["Seaside", "Cannon Beach"]). Case-insensitive.
maxPropertiesnumber–Max results. Default 20.
neLatnumber–BOUNDS MODE: Northeast latitude
neLngnumber–BOUNDS MODE: Northeast longitude
nearLatnumber–POINT MODE: Latitude to search near
nearLngnumber–POINT MODE: Longitude
nearRadiusnumber–POINT MODE: Max distance. Default 25.
nearUnitstring–Default "miles".
offsetnumber–Pagination offset. Default 0.
personastring–Soft ranking signal — boost properties popular with a guest persona (e.g., "hiking", "romantic", "young_family", "pet_owners", "fishing", "luxury"). Does NOT hard-filter.
petsRequiredboolean–Pet-friendly only
propertyTypesarray–Property type(s). The coarse family (house vs apartment) is the only hard filter; a specific subtype (e.g. "cabin", "a-frame") returns its whole family with that subtype boosted — cross-manager inter…
regionarray–Filter by state/region (e.g., ["Vermont"]). Case-insensitive.
semanticFiltersobject–Reserved optional evidence-backed semantic criteria that complement the explicit location, date, capacity, pet, property-type, and budget filters. Put true must-haves in `required`; put preferences t…
sleepsnumber–Minimum sleeping capacity
sortstring–Sort order. Default "relevance".
swLatnumber–BOUNDS MODE: Southwest latitude
swLngnumber–BOUNDS MODE: Southwest longitude
NameTypeReqDescription
collectionobject––
propertiesarrayyes–
semanticFilteringobject–Optional semantic-filtering summary. Omitted until semantic matching is enabled and the criteria have actually been evaluated.
suggestedFollowUpsarray––
totalMatchingnumberyes–
typestringyesAlways "searchProperties".

No examples provided.

shortlist_bookable ~346

Save or remove a vacation rental property from the guest's shortlist. Reversible. Anonymous guests are tracked via the MCP session ID; signed-in guests via their guest ID — the tool reads the current identity from session context, so no auth fields need to be passed.

NameTypeReqDescription
actionstring–Whether to save or remove the property from the shortlist. Optional — defaults to 'save'; pass 'remove' to take a property off the shortlist.
checkInstring–Check-in date (ISO 8601).
checkOutstring–Check-out date (ISO 8601).
collectionSlugstring–Optional. The parent collection slug. If omitted it is derived from the globally-unique propertySlug, so you can save with propertySlug alone.
collectionsarray–Collection slug(s) — each a `collection_id` from list_collections. For search_bookables and discover_collections: OMIT to span the whole network, pass one to scope to a single manager, or several to…
pricingSnapshotobject–Pricing snapshot at the time of shortlisting.
propertyNamestring–Display name of the property. Strongly recommended (you have it from search_bookables); if omitted, a readable name is derived from the slug.
propertySlugstringyesSlug of the property being shortlisted (required).
quoteTokenstring–Quote token for the selected rate.
NameTypeReqDescription
actionstring––
anonymousboolean––
checkInstring––
checkOutstring––
messagestring––
optionIdstring––
persistedbooleanyes–
propertyNamestring––
propertySlugstring––
reasonstring––

No examples provided.

sign_in ~204

Trigger the Kismet OAuth sign-in flow for the current guest. Call this whenever the user explicitly asks to sign in, log in, authenticate, or connect their Kismet account — common queries: "sign me in", "log me in", "log me into Kismet", "sign me into Kismet", "connect my Kismet account", "authenticate me", "I want to log in". The host will open its OAuth WebView and run the standard PKCE handshake; after successful authentication this tool returns a privacy-minimized confirmation snapshot (first name and verified-email flag only) and every subsequent tool call (get_guest_profile, get_shortlist, shortlist_bookable, etc.) will see the authenticated guest. Do NOT call this tool unless the user explicitly asked to sign in — anonymous browsing, search, and shortlisting all work fully without sign-in. After a successful sign-in, call get_guest_profile to surface the guest's full Kismet profile to the conversation.

Input schema present but exposes no named parameters.

NameTypeReqDescription
auth_statestringyes'authenticated' on a successful sign-in (bearer attached, session.oauth populated). 'anonymous' only on the defense-in-depth path where session.oauth somehow isn't set after the gate — surface that t…
identityobject––
successboolean––

No examples provided.

sign_in_agent ~134

Sign this agent back in through its own verified email inbox, with no bearer and no action from the person. Two steps with the same call: without `code`, Kismet mails a six-digit code to the inbox; with `code`, Kismet returns the agent bearer (access and refresh token) that acts for the linked person. Only a verified inbox on an agent the person already linked works; anything else is told to link first.

NameTypeReqDescription
codestring–The six-digit code from the mail Kismet sent; omit on the first call.
emailstringyesThe agent's own verified inbox address.
NameTypeReqDescription
access_tokenstring––
agent_idstring––
email_maskedstring––
expires_innumber––
expires_in_minutesnumber––
refresh_tokenstring––
scopestring––
statusstringyes–
token_typestring––

No examples provided.

use_guest_token ~260

Load READ-ONLY context from a Kismet guest token — e.g. a "continue in your AI assistant" link a property manager handed the guest. Returns the manager and the draft/considered itinerary the token carries (plus any current offer, when one applies), so you can have an informed conversation. This is CONTEXT ONLY: it grants NO account access and is never required for browsing. To actually claim an offer, save itinerary changes, message the manager, or book, the guest must sign in — call `sign_in` (the standard OAuth flow). Call this when the user pastes or references a Kismet guest/booking token or a kismet.travel/continue?kgt=… handoff link — pass it straight to this tool rather than browsing the URL; the token is extracted from the link. An unrecognized or expired token returns a clean invalid state (never an error) — then offer to sign them in.

NameTypeReqDescription
tokenstringyesThe Kismet guest token, OR the "continue in your AI assistant" handoff link that carries it (e.g. https://kismet.travel/continue?kgt=…). Pass the pasted link verbatim — the token is extracted from it…
NameTypeReqDescription
itineraryobject|null––
managerobject|null––
offerobject|null––
requires_sign_in_forarrayyesActions that require a real OAuth sign_in — this tool grants none of them.
sourcestring––
token_statusstringyes–

No examples provided.

verify_agent_inbox ~140

Record and verify the email inbox that belongs to THIS agent (not to the person it acts for), so the agent can later sign back in on its own with sign_in_agent. Two steps with the same call: without `code`, Kismet mails a six-digit code to the address; with `code`, the inbox is marked verified. Requires the agent bearer from the device flow or a connector sign-in. An agent address is never used to create a guest account.

NameTypeReqDescription
codestring–The six-digit code from the mail Kismet sent; omit on the first call.
emailstringyesThe agent's own inbox address.
NameTypeReqDescription
email_maskedstringyes–
expires_in_minutesnumber––
statusstringyes–

No examples provided.

Install

How do I install the travel.kismet/mcp-server server?

travel.kismet/mcp-server is a hosted endpoint at https://mcp.kismet.travel/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.kismet.travel

# add to Claude Code
claude mcp add --transport http travel-kismet-mcp-server 'https://mcp.kismet.travel/mcp'
Common questions

What is the travel.kismet/mcp-server server?

travel.kismet/mcp-server is listed in the public MCP registry as travel.kismet/mcp-server. Semantic hotel search with real-time availability and price comparison for Kismet Travel. This page covers its hosted endpoint (https://mcp.kismet.travel/mcp).

Is the travel.kismet/mcp-server server safe to use?

travel.kismet/mcp-server scores 84 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 travel.kismet/mcp-server server expose?

travel.kismet/mcp-server exposes 15 tools: list_collections, get_guest_profile, sign_in, use_guest_token, verify_agent_inbox, and 10 more. Their descriptions and schemas cost roughly 4,961 tokens of context every time the server is loaded.

Does the travel.kismet/mcp-server server require authentication?

No. We connected to travel.kismet/mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the travel.kismet/mcp-server server still maintained?

travel.kismet/mcp-server 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 travel.kismet/mcp-server server?

VerifyMCP ran 14 checks on travel.kismet/mcp-server, 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.