Anyone can list a rental. What this checks is whether the offer an agent is about to repeat was signed by the host's own domain, is still fresh, and carries the exact price it claims — and when it passes, the booking path is the host's own URL rather than a marketplace. When it does not pass, the agent has nothing it can quote as official, which is the intended outcome.
A hosted MCP server for direct booking on vacation-rental hosts' own websites. Verification is the point of it: an offer is signed on the host's domain with Ed25519 and JWKS under the Vacation Rental Protocol, and the server checks that signature, its freshness and its exact price before an agent may quote it as official.
- Search published rentals by location, dates and guest count, then check one property's availability for the dates you want — `hemmabo_search_properties`, `hemmabo_search_availability`
- A live quote with a per-night breakdown for one property and stay request — `hemmabo_booking_quote`
- VRP verification: check a host domain's discovery document and Ed25519 JWKS, then fetch and verify a fresh signed stay offer — `verify_vacation_rental_node`, `get_verified_stay_offer`
- Host-side reads: a fit check for a host asking about their own booking website, and an onboarding handoff URL that creates nothing on their behalf — `hemmabo_host_readiness_check`, `hemmabo_host_onboarding_link`
- Fallback booking helpers for configured non-VRP deployments — pending host-review bookings, short-lived quote snapshots, a host-configured Stripe checkout URL, cancel, reschedule, and lookup by reservation ID — `hemmabo_booking_create`, `hemmabo_booking_negotiate`, `hemmabo_booking_checkout`, `hemmabo_booking_cancel`, `hemmabo_booking_reschedule`, `hemmabo_booking_status`
Remote only — there is no local or stdio install, and clients never supply Supabase or Stripe credentials. Point an MCP client at `https://www.hemmabo.com/mcp` over Streamable HTTP, or let Smithery do it with `npx -y @smithery/cli install @info-00wt/hemmabo-mcp-server --client claude`. Anonymous calls get read-only discovery and quote helpers that return no guest personal data; mutating booking tools and booking-status reads need `Authorization: Bearer <token>`, either the configured `MCP_API_KEY` or OAuth client credentials issued by the server. Rate limits apply per source IP anonymously and per token hash when authenticated.
One command — npx -y @smithery/cli install @info-00wt/hemmabo-mcp-server --client claude