mcpbeat Sign in

HemmaBo Host Booking Engine MCP Server

not responding

HemmaBo Host Booking Engine is listed as active in the registry but did not answer our last check. It exposes 6 tools. Last commit 3 Nov 2026.

6 runtime tools: 2 HemmaBo tools, 2 host onboarding tools, and 2 VRP verification tools. Not an OTA.

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
6
Tools
read from the server
109 ms
Response time
average over 24h
4
Stars
last commit 3 Nov 2026

What changed 49

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 August 2026. No other catalogue keeps this.

18 Oct 5 tools appeared hemmabo_check_availability, hemmabo_check_host_readiness, hemmabo_get_host_onboarding_link and 2 more
18 Oct 5 tools disappeared get_verified_stay_offer, hemmabo_host_onboarding_link, hemmabo_host_readiness_check and 2 more
18 Oct a tool description was rewritten hemmabo_search_properties
8 Oct 7 tools disappeared hemmabo_booking_cancel, hemmabo_booking_checkout, hemmabo_booking_create and 4 more
8 Oct 6 tool descriptions were rewritten get_verified_stay_offer, hemmabo_host_onboarding_link, hemmabo_host_readiness_check and 3 more
8 Oct a tool changed the parameters it asks for hemmabo_search_properties
16 Sep a tool description was rewritten hemmabo_search_availability
5 Sep a tool changed version
23 Aug 2 tools changed the parameters they ask for get_verified_stay_offer, verify_vacation_rental_node
22 Aug 10 tool descriptions were rewritten hemmabo_booking_cancel, hemmabo_booking_checkout, hemmabo_booking_create and 7 more
and 10 more, back to 13 August 2026

HemmaBo Host Booking Engine does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add hemmabo-mcp-server --transport http https://www.hemmabo.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://www.hemmabo.com/mcp
~/.codex/config.toml
[mcp_servers.hemmabo-mcp-server]
url = "https://www.hemmabo.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "hemmabo-mcp-server": {
      "url": "https://www.hemmabo.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "hemmabo-mcp-server": {
      "type": "http",
      "url": "https://www.hemmabo.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

hemmabo
hemmabo_check_availability
Use this tool to answer "is it free these dates?" for one known propertyId — a yes/no with conflict details, no signed price. For the final quoted price and booking link, use vrp_get_verified_stay_offer with the host domain instead. Never present this tool's numbers as the final price. 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, open to anonymous callers (no Bearer token), and rate-limited: checking availability never places a hold or reserves dates. Returns available=true/false with conflict details and, when unavailable, the host node's own next available window (alternativeDates, at most one entry — the same window the node's /api/availability reports, never a platform-invented date); a stale inbound calendar sync blocks an available answer (fails closed with calendar_freshness) instead of guessing. Omit guests to check dates only; pass it to price the alternative windows and to gate capacity — counts above the property's maximum return available=false (guests_exceed_max) with no alternatives. Stays shorter than the host's effective minimum nights return available=false with reasonCode min_nights_violation — extend the stay rather than shifting dates. The verdict always matches the host node's own availability API. Booking and payment happen only on the host's own domain, at the signed direct_booking_url. The agent never books, pays, cancels or changes a booking.
hemmabo_check_host_readiness
Use this tool when a host is still EVALUATING whether HemmaBo fits; use hemmabo_get_host_onboarding_link only when the host has decided and wants to start. Never call both in the same turn — this tool's next_step already contains the same onboarding URL. 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 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_get_host_onboarding_link. Only five inputs sharpen the fit verdict: a domain (hasOwnDomain or domain), currentChannels, one location signal (city/region/country), and the wants* booleans, which count unless explicitly false — omitting them never lowers the verdict; propertyName and preferredLanguage only prefill the onboarding URL, and with no inputs the summary is generic. Booking and payment happen only on the host's own domain, at the signed direct_booking_url. The agent never books, pays, cancels or changes a booking.
hemmabo_get_host_onboarding_link
Use this tool only when the host has already decided to start; if the host is still evaluating, use hemmabo_check_host_readiness instead — it returns the same onboarding URL in next_step. Never call both in the same turn. Return a safe HemmaBo onboarding handoff URL for a vacation-rental host who wants their own booking website or booking engine. Not for guests — guests 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_check_host_readiness first — it already returns the same prefilled URL in its next_step. 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, the category sentence, the host's price atom, the agent's role, and what the host should prepare. All parameters are optional prefill: they never change where the host lands — the URL always opens the same onboarding page with the passed details filled in; blank values are simply left out, and nothing is stored server-side. Booking and payment happen only on the host's own domain, at the signed direct_booking_url. The agent never books, pays, cancels or changes a booking.
hemmabo_search_properties
Search available vacation rental properties by location and travel dates. Use when the user wants to find or browse places to stay. Discovery only, and price-free: call vrp_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; the price and the signed booking link come only from that offer. Do NOT use when the user already has a propertyId or host domain. Returns propertyId, host domain, the host's booking_url, live availability and capacity. Parameters combine as one filter with guests and the checkIn/checkOut range (checkIn strictly before checkOut): region matches broadly against region, city, and country names, while country matches the country field alone — omit both and the search spans every published property. Capacity misses are excluded; date-unavailable matches return separately in unavailableMatches with up to three alternative windows. Booking and payment happen only on the host's own domain, at the signed direct_booking_url. The agent never books, pays, cancels or changes a booking.
vrp
vrp_get_verified_stay_offer
Use this tool for the final, host-signed price and booking link for exact dates — the only numbers an agent may quote. For a bare availability yes/no on a propertyId, hemmabo_check_availability is lighter and sufficient. 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 vrp_verify_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 or collect guest details. Route booking only to the signed direct_booking_url. 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. Booking and payment happen only on the host's own domain, at the signed direct_booking_url. The agent never books, pays, cancels or changes a booking.
vrp_verify_node
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 vrp_get_verified_stay_offer. On success, call vrp_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); public domains only — IPs, ports, and local/private hostnames are refused. Pass the node's canonical domain exactly — www and apex are distinct identities, and verification fails when the domain's declared canonical_domain differs from the one you passed. Verification reads that domain's own .well-known and JWKS, so the result is only as trustworthy as the exact domain you pass. Booking and payment happen only on the host's own domain, at the signed direct_booking_url. The agent never books, pays, cancels or changes a booking.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

hemmabo_booking_cancel
removed 8 Oct 2026
hemmabo_booking_checkout
removed 8 Oct 2026
hemmabo_booking_create
removed 8 Oct 2026
hemmabo_booking_negotiate
removed 8 Oct 2026
hemmabo_booking_quote
removed 8 Oct 2026
hemmabo_booking_reschedule
removed 8 Oct 2026
hemmabo_booking_status
removed 8 Oct 2026
get_verified_stay_offer
removed 18 Oct 2026
hemmabo_host_onboarding_link
removed 18 Oct 2026
hemmabo_host_readiness_check
removed 18 Oct 2026
hemmabo_search_availability
removed 18 Oct 2026
verify_vacation_rental_node
removed 18 Oct 2026

Endpoints

URLTransportStateLatencyChecked
https://www.hemmabo.com/mcp streamable-http answering 109 ms 13 min ago

Alternatives to HemmaBo Host Booking Engine

same job, measured the same way
Agent Broker
by hatchloop

23 MCP tools: compliance, verification, messaging, booking, US contracts. 15 need no key.

23 tools answering
Bounty Engineer Agent Commerce
by gatoprd

Remote MCP storefront for agent routing, verification, web extraction and x402-paid tools.

22 tools answering
Glamour
by gratise

Browser-measured visual debugging and verification tools for coding agents.

41 installs/wk local only
P
Python Package Runtime Test
by ligafew

Hosted Python sandbox for package runtime verification: pip install and usable-import evidence.

1 tools answering
A
AgentGraph Trust
by agentgraph-co

Security scanning and trust verification for AI agent tools.

390 installs/wk local only
Accuracite MCP
by accuracite

MCP server exposing AccuraCite's citation verification and finding API as tools

47 installs/wk local only
Heffl Free Tools
by heffl

Free email verification, business calculators, UAE estimates and drafts. No API key.

15 tools answering
Reality Graph Verification Tools
by realitygraph

Read-only AI coding tools for change verification, release readiness, capacity, and guidance.

10 tools answering

HemmaBo Host Booking Engine — questions

Answers built from our own checks of this server.

What can HemmaBo Host Booking Engine do?
It exposes 6 tools, read directly from the server on our last check. Among them: hemmabo_check_availability, hemmabo_check_host_readiness, hemmabo_get_host_onboarding_link, hemmabo_search_properties, vrp_get_verified_stay_offer, vrp_verify_node. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is HemmaBo Host Booking Engine mostly used for?
Its tools cluster around hemmabo and vrp. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is HemmaBo Host Booking Engine working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 109 ms. The bar chart above shows every period we have measured.
Did HemmaBo Host Booking Engine ever remove tools?
Yes. hemmabo_booking_cancel, hemmabo_booking_checkout, hemmabo_booking_create, hemmabo_booking_negotiate and 8 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
The registry lists HemmaBo Host Booking Engine as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect HemmaBo Host Booking Engine?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does HemmaBo Host Booking Engine need an API key?
No. HemmaBo Host Booking Engine completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
Is HemmaBo Host Booking Engine open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 4 stars on GitHub and 4 open issues. The licence covers the code in the repository, not the hosted service at hemmabo.com, which runs on its operator's own terms.