accueil / serveurs / Recherche & Web / travel.kismet/mcp-server
travel.kismet/mcp-server
serveur MCP (Model Context Protocol) · kismet-catalog 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que travel.kismet/mcp-server est sûr ?
Au dernier audit MCP Hub, le serveur MCP « travel.kismet/mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 15 outils
- build_bookable_carousel≈ 1968 tokens
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.
Paramètres, retour & exemple (7)
Paramètresguests· number · optionnel
Number of guestscheckIn· string · optionnel
Check-in date for live pricingcontext· string · optionnel
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 journey so the property manager sees what the guest is looking for. Not displayed to the guest.checkOut· string · optionnel
Check-out date for live pricingcollections· array · optionnel
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 compare across managers. For build_bookable_carousel: pass the collection_id(s) your chosen properties belong to — one, or several when the picks span managers. Every other tool operates on a single collection — pass exactly ONE.propertySlugs· array · requis
Ordered array of property slugs to present. The carousel preserves this order. Max 10.semanticFilters· object · optionnel
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 that should improve ranking without excluding otherwise valid stays in `requested`. Until server instructions announce that semantic matching is enabled, omit this field.
Exemple d'appel{"name": "build_bookable_carousel", "arguments": {"propertySlugs": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "dates": {}, "guests": 1, "reviews": {}, "success": true, "collection": {}, "llmContext": "texte", "collections": [], "propertyPicks": {}, "bookingBaseUrl": "texte", "multiCollection": true, "semanticFiltering": {}}} - discover_collections≈ 2791 tokens
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.
Paramètres, retour & exemple (27)
ParamètresneLat· number · optionnel
BOUNDS MODE: Northeast corner latitude. Required with swLat.neLng· number · optionnel
BOUNDS MODE: Northeast corner longitude. Required with swLat.swLat· number · optionnel
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.0, swLng=-124.8, neLat=46.3, neLng=-123.5.swLng· number · optionnel
BOUNDS MODE: Southwest corner longitude. Required with swLat.guests· number · optionnel
Number of guestsoffset· number · optionnel
Skip this many results (for pagination / load-more). Default 0.region· array · optionnel
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.sleeps· number · optionnel
Minimum sleeping capacity required (filters properties that sleep at least this many)checkIn· string · optionnel
Check-in date (YYYY-MM-DD)country· string · optionnel
Filter by ISO 3166-1 alpha-2 country code (e.g., "US"). Rarely needed since collections are typically in one country.feature· string · optionnel
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", "quiet_peaceful".nearLat· number · optionnel
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 ranges), use bounding box (swLat/neLat) instead.nearLng· number · optionnel
POINT MODE: Longitude to search near (e.g. -83.534). Required when nearLat is provided.persona· string · optionnel
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", "foodie".bedrooms· number · optionnel
Minimum bedrooms neededcheckOut· string · optionnel
Check-out date (YYYY-MM-DD)locality· array · optionnel
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.nearUnit· string · optionnel · miles | kilometers
Unit for nearRadius and distance values. Default "miles".nearRadius· number · optionnel
POINT MODE: Max distance from the nearLat/nearLng point in nearUnit. Default 25 miles. Use 50+ for broad areas.collections· array · optionnel
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 compare across managers. For build_bookable_carousel: pass the collection_id(s) your chosen properties belong to — one, or several when the picks span managers. Every other tool operates on a single collection — pass exactly ONE.preferences· string · optionnel
Free text preferences (e.g., "hot tub, mountain view")petsRequired· boolean · optionnel
Whether guest needs pet-friendly propertymaxProperties· number · optionnel
Max property picks to return. Default 5.propertySlugs· array · optionnel
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 backfilling with the next-best similar available properties so the set keeps its size ("same or slightly expanded"). Lets a curated/merged carousel re-price across new dates without re-searching. Overrides offset/limit pagination.propertyTypes· array · optionnel
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 interleaving may still rank other family members above it; never zero results.semanticFilters· object · optionnel
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 that should improve ranking without excluding otherwise valid stays in `requested`. Until server instructions announce that semantic matching is enabled, omit this field.budgetMaxPerNight· number · optionnel
Max nightly budget in major currency units
Exemple d'appel{"name": "discover_collections", "arguments": {"neLat": 1, "neLng": 1, "swLat": 1, "swLng": 1, "guests": 1, "offset": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "dates": {}, "guests": 1, "reviews": {}, "success": true, "collection": {}, "collections": [], "propertyPicks": {}, "bookingBaseUrl": "texte", "multiCollection": true, "semanticFiltering": {}, "suggestedFollowUps": []}} - get_bookable_detail≈ 1359 tokens
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.
Paramètres, retour & exemple (4)
ParamètrescheckIn· string · optionnel
Check-in date for pricingcheckOut· string · optionnel
Check-out date for pricingcollections· array · optionnel
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 compare across managers. For build_bookable_carousel: pass the collection_id(s) your chosen properties belong to — one, or several when the picks span managers. Every other tool operates on a single collection — pass exactly ONE.propertySlug· string · requis
Slug of the vacation rental property
Exemple d'appel{"name": "get_bookable_detail", "arguments": {"propertySlug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "reviews": {}, "property": {}, "detailUrl": "texte", "membership": {}, "similarAvailable": [], "alternateDateWindows": []}} - get_bookable_reviews≈ 727 tokens
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.
Paramètres, retour & exemple (7)
Paramètressort· string · optionnel · newest | oldest | highest | lowest
How to sort reviews (default newest).limit· number · optionnel
Number of reviews to return (default 5, max 20).offset· number · optionnel
Number of reviews to skip for pagination (default 0).season· string · optionnel · winter | spring | summer | fall
Filter to reviews from a specific season.persona· string · optionnel
Filter to reviews from a guest persona type (e.g. "family", "couples", "solo").collections· array · optionnel
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 compare across managers. For build_bookable_carousel: pass the collection_id(s) your chosen properties belong to — one, or several when the picks span managers. Every other tool operates on a single collection — pass exactly ONE.propertySlug· string · optionnel
Slug of the specific property to get reviews for. If omitted, returns collection-level reviews.
Exemple d'appel{"name": "get_bookable_reviews", "arguments": {"sort": "newest", "limit": 1, "offset": 1, "season": "winter", "persona": "texte", "collections": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "scope": "property", "reviews": [], "success": true, "summary": {}, "scopeSlug": "texte", "collection": {}, "pagination": {}}} - get_booking_link≈ 603 tokens
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.
Paramètres, retour & exemple (5)
Paramètresguests· number · optionnel
Number of guestscheckIn· string · optionnel
Check-in date (YYYY-MM-DD)checkOut· string · optionnel
Check-out date (YYYY-MM-DD)collections· array · optionnel
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 compare across managers. For build_bookable_carousel: pass the collection_id(s) your chosen properties belong to — one, or several when the picks span managers. Every other tool operates on a single collection — pass exactly ONE.propertySlug· string · requis
Slug of the vacation rental
Exemple d'appel{"name": "get_booking_link", "arguments": {"propertySlug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "bookingUrl": "texte", "propertySlug": "texte", "datesRejected": true, "rejectionReason": "texte", "alternateDateWindows": []}} - get_collection_content≈ 736 tokens
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.
Paramètres, retour & exemple (4)
Paramètreslimit· number · optionnel
Max items for reviews. Default 10.offset· number · optionnel
Pagination offsetsection· string · requis · about | reviews
Content sectioncollections· array · optionnel
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 compare across managers. For build_bookable_carousel: pass the collection_id(s) your chosen properties belong to — one, or several when the picks span managers. Every other tool operates on a single collection — pass exactly ONE.
Exemple d'appel{"name": "get_collection_content", "arguments": {"section": "about"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "type": "texte", "limit": 1, "total": 1, "offset": 1, "reviews": [], "section": "about", "summary": {}, "membership": {}}} - get_guest_profile≈ 1375 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_guest_profile", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"identity": {}, "auth_state": "authenticated", "collections": [], "memberships": [], "preferences": {}, "communication": {}, "account_status": {}, "shortlist_count": 1, "activity_summary": {}, "assistant_guidance": "texte"}} - get_shortlist≈ 632 tokens
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.
Paramètres, retour & exemple (2)
Paramètreslimit· number · optionnel
Maximum number of saved properties to return (default 20).collections· array · optionnel
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 compare across managers. For build_bookable_carousel: pass the collection_id(s) your chosen properties belong to — one, or several when the picks span managers. Every other tool operates on a single collection — pass exactly ONE.
Exemple d'appel{"name": "get_shortlist", "arguments": {"limit": 1, "collections": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "items": [], "isEmpty": true, "success": true, "collection": {}, "totalSaved": 1, "emptyMessage": "texte"}} - list_collections≈ 528 tokens
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.
Paramètres, retour & exemple (4)
Paramètreslimit· number · optionnel
Max results (default 20).query· string · optionnel
Free-text search across name, region, and description.region· string · optionnel
Filter by region, state, or country (e.g. "Oregon").category· string · optionnel
Filter by category, e.g. "vacation_rental".
Exemple d'appel{"name": "list_collections", "arguments": {"limit": 1, "query": "texte", "region": "texte", "category": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "success": true, "collections": []}} - search_bookables≈ 2281 tokens
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).
Paramètres, retour & exemple (25)
Paramètressort· string · optionnel · relevance | price_asc | price_desc | beds_desc | name_asc
Sort order. Default "relevance".neLat· number · optionnel
BOUNDS MODE: Northeast latitudeneLng· number · optionnel
BOUNDS MODE: Northeast longitudeswLat· number · optionnel
BOUNDS MODE: Southwest latitudeswLng· number · optionnel
BOUNDS MODE: Southwest longitudeguests· number · optionnel
Number of guestsoffset· number · optionnel
Pagination offset. Default 0.region· array · optionnel
Filter by state/region (e.g., ["Vermont"]). Case-insensitive.sleeps· number · optionnel
Minimum sleeping capacitycountry· string · optionnel
Filter by ISO alpha-2 country code (e.g., "US")feature· string · optionnel
Soft ranking signal — boost properties with a guest-confirmed feature (e.g., "mountain_views", "spotless_clean", "hot_tub", "cozy", "beachfront"). Does NOT hard-filter.nearLat· number · optionnel
POINT MODE: Latitude to search nearnearLng· number · optionnel
POINT MODE: Longitudepersona· string · optionnel
Soft ranking signal — boost properties popular with a guest persona (e.g., "hiking", "romantic", "young_family", "pet_owners", "fishing", "luxury"). Does NOT hard-filter.bedrooms· number · optionnel
Minimum bedrooms neededlocality· array · optionnel
Filter by city/town name (e.g., ["Stowe"], ["Seaside", "Cannon Beach"]). Case-insensitive.nearUnit· string · optionnel · miles | kilometers
Default "miles".nearRadius· number · optionnel
POINT MODE: Max distance. Default 25.collections· array · optionnel
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 compare across managers. For build_bookable_carousel: pass the collection_id(s) your chosen properties belong to — one, or several when the picks span managers. Every other tool operates on a single collection — pass exactly ONE.dateWindows· array · optionnel
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 dated total.petsRequired· boolean · optionnel
Pet-friendly onlymaxProperties· number · optionnel
Max results. Default 20.propertyTypes· array · optionnel
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 interleaving may still rank other family members above it; never zero results.semanticFilters· object · optionnel
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 that should improve ranking without excluding otherwise valid stays in `requested`. Until server instructions announce that semantic matching is enabled, omit this field.budgetMaxPerNight· number · optionnel
Max nightly budget in major currency units
Exemple d'appel{"name": "search_bookables", "arguments": {"sort": "relevance", "neLat": 1, "neLng": 1, "swLat": 1, "swLng": 1, "guests": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "collection": {}, "properties": [], "totalMatching": 1, "semanticFiltering": {}, "suggestedFollowUps": []}} - shortlist_bookable≈ 762 tokens
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.
Paramètres, retour & exemple (9)
Paramètresaction· string · optionnel · save | remove
Whether to save or remove the property from the shortlist. Optional — defaults to 'save'; pass 'remove' to take a property off the shortlist.checkIn· string · optionnel
Check-in date (ISO 8601).checkOut· string · optionnel
Check-out date (ISO 8601).quoteToken· string · optionnel
Quote token for the selected rate.collections· array · optionnel
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 compare across managers. For build_bookable_carousel: pass the collection_id(s) your chosen properties belong to — one, or several when the picks span managers. Every other tool operates on a single collection — pass exactly ONE.propertyName· string · optionnel
Display name of the property. Strongly recommended (you have it from search_bookables); if omitted, a readable name is derived from the slug.propertySlug· string · requis
Slug of the property being shortlisted (required).collectionSlug· string · optionnel
Optional. The parent collection slug. If omitted it is derived from the globally-unique propertySlug, so you can save with propertySlug alone.pricingSnapshot· object · optionnel
Pricing snapshot at the time of shortlisting.
Exemple d'appel{"name": "shortlist_bookable", "arguments": {"propertySlug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"action": "save", "reason": "texte", "checkIn": "texte", "message": "texte", "checkOut": "texte", "optionId": "texte", "anonymous": true, "persisted": true, "propertyName": "texte", "propertySlug": "texte"}} - sign_in≈ 460 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "sign_in", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"success": true, "identity": {}, "auth_state": "authenticated"}} - sign_in_agent≈ 332 tokens
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.
Paramètres, retour & exemple (2)
Paramètrescode· string · optionnel
The six-digit code from the mail Kismet sent; omit on the first call.email· string · requis
The agent's own verified inbox address.
Exemple d'appel{"name": "sign_in_agent", "arguments": {"email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"scope": "texte", "status": "code_sent", "agent_id": "texte", "expires_in": 1, "token_type": "texte", "access_token": "texte", "email_masked": "texte", "refresh_token": "texte", "expires_in_minutes": 1}} - use_guest_token≈ 500 tokens
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.
Paramètres, retour & exemple (1)
Paramètrestoken· string · requis
The 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; do not fetch the URL.
Exemple d'appel{"name": "use_guest_token", "arguments": {"token": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"offer": {}, "source": "texte", "manager": {}, "itinerary": {}, "token_status": "loaded", "requires_sign_in_for": []}} - verify_agent_inbox≈ 288 tokens
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.
Paramètres, retour & exemple (2)
Paramètrescode· string · optionnel
The six-digit code from the mail Kismet sent; omit on the first call.email· string · requis
The agent's own inbox address.
Exemple d'appel{"name": "verify_agent_inbox", "arguments": {"email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "code_sent", "email_masked": "texte", "expires_in_minutes": 1}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».