mcp server

HemmaBo Host Booking Engine

Host-owned vacation-rental direct booking via VRP. Signed offers, 0% commission. Not an OTA.

Description as published by the maintainer. Source

• version 4.0.2
• active

active — Most recent push to the repository was 2026-08-06.

What this server can do

13 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

get_verified_stay_offer(domain, guests, checkIn, checkOut, language)

Fetch, verify, and render a live host-domain signed VRP stay offer for exact dates and guest count. Verifies Ed25519 JWS against domain JWKS. Call after hemmabo_search_properties returns a host domain, or after verify_vacation_rental_node confirms a domain from outside search, always before quoting final price or a booking link. Read-only: must not lock a quote, create a booking, collect guest details, or start checkout. Route booking only to the signed direct_booking_url; fall back to hemmabo_booking_negotiate/hemmabo_booking_checkout only when this call returns no signed offer, for a configured non-VRP deployment, after explicit user confirmation. The parameters work as a set: pass the same domain, checkIn, checkOut and guests the guest used at search; checkIn must be strictly before checkOut, and the resulting night count — not the dates themselves — drives the signed price and the host capacity check, so changing either date re-prices the offer. Always pass language as the guest's actual conversation language so the rendered widget matches the guest; it never affects the signed price or availability, only formatting. Required: domain, checkIn, checkOut, guests.

hemmabo_booking_cancel(reason, reservationId)

Cancel a confirmed booking and process the Stripe refund per host cancellation policy. Use when the guest explicitly requests cancellation — if the guest wants new dates instead of ending the stay, use hemmabo_booking_reschedule instead. Do not use for pending/unpaid bookings — those expire automatically. To preview the applicable policy first, read cancellationPolicy from hemmabo_booking_status. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Destructive and idempotent: cancelling an already-cancelled booking returns the same status. Rate-limited per token. reservationId must be the booking UUID from hemmabo_booking_checkout or hemmabo_booking_create — not a propertyId; reason is optional free text forwarded to the host. Required: reservationId.

hemmabo_booking_checkout(guests, channel, checkIn, quoteId, checkOut, guestName, guestEmail, guestPhone, propertyId, paymentMode)

Create a fallback non-VRP booking and return a host-configured Stripe checkout URL. Use only after explicit user confirmation when no signed VRP direct_booking_url is available. When get_verified_stay_offer returns a signed direct_booking_url, route the guest there instead; use hemmabo_booking_create instead when the deployment wants a pending booking recorded without collecting payment yet. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Creates a pending booking and Stripe session server-side; not idempotent — check hemmabo_booking_status before retrying. Rate-limited per token. Pass quoteId to honor a price locked by hemmabo_booking_negotiate for the same propertyId/dates/guests, or omit it to price fresh at checkout; paymentMode picks the Stripe flow, channel picks the pricing channel, and guestName/guestEmail identify the guest. Required: propertyId, checkIn, checkOut, guests, guestName, guestEmail.

hemmabo_booking_create(guests, checkIn, checkOut, guestName, guestEmail, guestPhone, propertyId)

Create a pending direct booking without online payment for configured non-VRP fallback deployments. Use only after explicit user confirmation, with a propertyId from search, and only when no signed VRP direct_booking_url is available. For signed VRP offers, route to the signed host-domain URL instead. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Writes a pending booking server-side; not idempotent — check hemmabo_booking_status before retrying on timeout. Rate-limited per token. The booking is identified by propertyId + the checkIn/checkOut range + guests; guestName and guestEmail are required for host confirmation, while guestPhone is optional for check-in coordination. Required: propertyId, checkIn, checkOut, guests, guestName, guestEmail.

hemmabo_booking_negotiate(guests, checkIn, checkOut, propertyId)

Create a binding price quote that locks the price for 15 minutes for configured non-VRP fallback checkout deployments. Use only when no signed direct_booking_url is available and the user explicitly asks to lock a price. Never use this for search, availability, VRP offers, rendering a stay-offer widget, or verified-offer display — use get_verified_stay_offer instead. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Writes a short-lived quote snapshot server-side. Rate-limited per token. The parameters form one locked combination: the returned quoteId is honored by hemmabo_booking_checkout only for the identical propertyId + checkIn/checkOut + guests, and only until validUntil — changing any of them requires a new quote. Night count and guest count together select the price tier that gets locked, same as hemmabo_booking_quote. Required: propertyId, checkIn, checkOut, guests.

hemmabo_booking_quote(guests, checkIn, checkOut, propertyId)

Get a detailed pricing quote for a specific property, dates, and guest count. Use this tool after confirming availability to show the user exact pricing before booking. Do NOT use before checking availability — the quote may be invalid if dates are unavailable. Returns the final host-source total for the booking flow, per-night breakdown, and package pricing context. All prices are integers in the property's local currency (e.g. SEK). The quote is the propertyId priced for the exact checkIn/checkOut range and guests; the night count and party size together select the price tier, so changing any of them re-quotes. Required: propertyId, checkIn, checkOut, guests.

hemmabo_booking_reschedule(reason, newCheckIn, newCheckOut, reservationId)

Reschedule a confirmed or pending booking to new dates with automatic repricing and Stripe charge/refund. Use when the guest wants to change dates on an existing booking — if the guest wants to end the stay entirely rather than move it, use hemmabo_booking_cancel instead. Do not use if cancelled or if a protocol compatibility client reports completed — check hemmabo_booking_status first. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Destructive write: the original dates are released back to the host calendar and the original price no longer applies — the booking keeps the same reservationId (updated in place, never recreated), and the price difference is charged or refunded via Stripe. Rate-limited per token. Identify the existing booking by reservationId, then give the new stay as newCheckIn/newCheckOut (newCheckIn strictly before newCheckOut); the new night count re-prices the stay exactly like a fresh quote. Required: reservationId, newCheckIn, newCheckOut.

hemmabo_booking_status(reservationId)

Retrieve current status and full details of an existing booking by reservationId. Use to confirm checkout/create succeeded or before cancel/reschedule. Do NOT use for property discovery, availability, or pricing — use hemmabo_search_properties, hemmabo_search_availability, or hemmabo_booking_quote for those. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Read-only against the database — never writes, so it is safe to poll after a checkout timeout — but returns guest PII (name, email). Rate-limited per token. The only input is the reservationId returned by hemmabo_booking_checkout or hemmabo_booking_create — never the propertyId; without a reservationId there is no booking to look up yet. Required: reservationId.

hemmabo_host_onboarding_link(city, domain, region, country, language, propertyName)

Return a safe HemmaBo onboarding handoff URL for a vacation-rental host who wants their own booking website or booking engine. Not for guests — a guest looking for a place to stay should use hemmabo_search_properties instead. Use after explaining the fit or when the host asks to start; if the host is still evaluating whether HemmaBo fits, run hemmabo_host_readiness_check first. This tool is read-only and does not create a HemmaBo account, buy a domain, configure Stripe, write to Supabase, or provision a booking site. It returns the URL, what the host gets, and what the host should prepare. All parameters are optional and only enrich the returned onboarding URL — propertyName, country/region/city, domain, and language are prefilled into it, so the host lands with their details already filled in; nothing is stored server-side.

hemmabo_host_readiness_check(city, domain, region, country, hasOwnDomain, propertyName, propertyType, currentChannels, preferredLanguage, wantsAiAgentBooking, wantsDirectPayments)

Read-only fit check for a vacation-rental host evaluating HemmaBo for their own booking website or booking engine. Use when the user is a host or property owner, not a guest booking a stay — guests searching for a place to stay should use hemmabo_search_properties instead. Returns a fit verdict, what the host gets, the setup inputs to prepare, and a safe onboarding next step. Does not create an account, buy a domain, configure Stripe, store host data, or provision a website. When the host is ready to start, follow up with hemmabo_host_onboarding_link. Every parameter is optional and additive — the more you pass (propertyType, country/region/city, domain, currentChannels, and the wants* booleans), the sharper the fit verdict; with none it returns a generic readiness summary.

hemmabo_search_availability(guests, checkIn, checkOut, propertyId)

Check whether a specific property is available for the requested dates. Use this tool after the user has selected a property from hemmabo_search_properties and wants to confirm availability before getting a quote. Do NOT use for general browsing — use hemmabo_search_properties instead. Read-only: checking availability never places a hold or reserves dates. Returns available=true/false with conflict details and same-month alternative date windows when unavailable. Use the propertyId from search with the exact checkIn/checkOut range; omit guests to check dates only, or pass it to get host-source totals for that party size in the returned alternative windows. Required: propertyId, checkIn, checkOut.

hemmabo_search_properties(guests, region, checkIn, country, checkOut)

Search available vacation rental properties by location and travel dates. Use when the user wants to find or browse places to stay. Discovery only — call get_verified_stay_offer with the host domain and same dates before the final answer so the client can render the verified stay offer widget; never quote a final price or booking link from search alone. Do NOT use when the user already has a propertyId or host domain. Returns propertyId, host domain, live availability, host-source pricing, and capacity. Parameters combine as one filter: give at least one of region or country to scope location, plus guests and the checkIn/checkOut range (checkIn strictly before checkOut) — results drop any property below the guest capacity or unavailable for that exact range. Required: guests, checkIn, checkOut.

verify_vacation_rental_node(domain)

Verify that a vacation-rental host domain is a valid Vacation Rental Protocol (VRP) node before trusting it. Reads the domain's .well-known/vacation-rental.json and JWKS. Read-only trust check: no availability, pricing, booking, or payment — do NOT use it to answer those questions. Use when a host domain arrives from outside search (user-typed or third-party); domains returned by hemmabo_search_properties can go straight to get_verified_stay_offer. On success, call get_verified_stay_offer with the same domain and stay dates. The single input is the host domain as a bare hostname (no scheme or path); verification reads that domain's own .well-known and JWKS, so the result is only as trustworthy as the exact domain you pass. Required: domain.

Last successful function declaration observed on 2026-08-13. Source: https://www.hemmabo.com/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on 2026-08-13. Source: https://www.hemmabo.com/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Where to get it

• Repository — https://github.com/HemmaBo-se/hemmabo-mcp-server
• Website — https://www.hemmabo.com
• Remote endpoint (streamable-http) — https://www.hemmabo.com/mcp

Related, by what their authors tagged them

• io.github.CSOAI-ORG/meok-stripe-acp-checkout-mcp — last commit 2026-06-26, shares ap2, stripe-acp
  MEOK Stripe ACP Checkout MCP — ChatGPT shopping bridge. Issues + verifies + signs Stripe Agentic
• LLM SEO MCP — Elephant Accountability — last commit 2026-05-05, shares a2a, ucp
  LLM SEO and Agent Discoverability for B2B SaaS. Pricing, fit assessment, audit requests.
• Guesty MCP Server — last commit 2026-08-06, shares short-term-rental
  Guesty property-management MCP. 23 free read-only tools live; 43 total (Pro+Enterprise) at v1.0.
• Chia Health MCP Server — last commit 2026-03-31, shares stripe-acp
  Licensed US telehealth — GLP-1 medications, intake, consents, Stripe ACP. HIPAA-compliant, 30 tools.
• Eveoy — Verified In-Store Foot Traffic ($24.99/customer) — last commit 2026-07-16, shares agentic-commerce, stripe
  Your Eveoy expert in any AI — learn how it works, get a price, and order real in-store visits.
• com.mnemopay/sdk — last commit 2026-06-26, shares agentic-commerce, stripe
  Memory + wallet for AI agents. Real payment rails, Agent FICO 300-850, Merkle audit, identity.
• JassWiki — Swiss Jass Authority (AMCP v0.1) — last commit 2026-07-06, shares ed25519
  First production Authority-MCP. W3C VC attested by Jassverband Schweiz.
• com.fidacy/ai-agent-firewall — last commit 2026-08-04, shares ed25519
  Every agent action watched, every money-moving one gated, every verdict independently verifiable.
• com.fidacy/mcp — last commit 2026-08-04, shares ed25519
  Payment firewall for AI agents: a signed, verifiable verdict on every money-moving action.
• com.scopeblind/protect-mcp — last commit 2026-07-09, shares ed25519
  Fail-closed Cedar policy gate + Ed25519 signed receipts for agent tool calls. Denies on any error.

These share tags the maintainers applied themselves, such as ap2, stripe-acp, a2a, ucp. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.

This is not a recommendation and not a test result. It is a map of what the authors said their work is about.

How the author describes it

Topics the maintainer set on GitHub: a2a, agent-traversal, agentic-commerce, ai-agents, ap2, direct-booking, ed25519, federation-infrastructure, host-domain-signature, jwks, mcp, mcp-server, short-term-rental, stripe, stripe-acp, ucp, vacation-rental-protocol, vacation-rentals, verified-stay-offer, vrp.