HemmaBo Host Booking Engine
REMOTE · WWW.HEMMABO.COM
6 runtime tools: 2 HemmaBo tools, 2 host onboarding tools, and 2 VRP verification tools. Not an OTA.
Available components
Last scanned (8 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 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 3842 tokens (~548/item across 7 items; 6 tools + 1 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 Management17
- Stability check failed: schema churn in the 30 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 5 additions. See how to fix → Fail
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 8 to 17.
- 30 Oct 26 0
- Server version: 7.0.10 → 7.0.12 functional
- 28 Oct 26 0
- Resource “HemmaBo verified stay offer widget” now points somewhere else: ui://hemmabo/verified-stay-offer-v10.html → ui://hemmabo/verified-stay-offer-v11.html security
- Server version: 7.0.9 → 7.0.10 functional
- Server version: 7.0.8 → 7.0.9 functional
- 27 Oct 26 0
- Resource “HemmaBo verified stay offer widget” now points somewhere else: ui://hemmabo/verified-stay-offer-v9.html → ui://hemmabo/verified-stay-offer-v10.html security
- Server version: 7.0.7 → 7.0.8 functional
- 26 Oct 26 0
- Server version: 7.0.5 → 7.0.7 functional
- 20 Oct 26 0
- Server version: 7.0.4 → 7.0.5 functional
- 14 Oct 26 +1
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 7.0.3 → 7.0.4 functional
- Server version: 7.0.2 → 7.0.3 functional
- Server version: 7.0.1 → 7.0.2 functional
- 13 Oct 26 +1
- MCP protocol version: 2025-03-26 → 2025-06-18 functional
- Server version: 7.0.0 → 7.0.1 functional
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 5 Nov 2026 · Probed https://www.hemmabo.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.hemmabo.com | CN=YR1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | RSA 2048 | SHA256-RSA | 6405292e36c8f77bf97c248aa1fa26035e8 |
| SANs: www.hemmabo.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.hemmabo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hemmabo.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="hemmabo-mcp", resource_metadata="https://www.hemmabo.com/.well-known/oauth-protected-resource", scope="mcp"
Bearer realm="hemmabo-mcp", resource_metadata="https://www.hemmabo.com/.well-known/oauth-protected-resource", scope="mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Protected resource metadata
| Document | https://www.hemmabo.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://www.hemmabo.com/mcp |
| Authorisation server | https://www.hemmabo.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.hemmabo.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.hemmabo.com/mcp | HTTPS enforced | 308 | https://www.hemmabo.com/mcp |
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 →
hemmabo_check_availability Check Availability ~552
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkIn | string | yes | Arrival date in ISO 8601 calendar format YYYY-MM-DD (e.g. '2026-07-15'). Must be today or later in the property's timezone. Must be strictly before checkOut; together they define the stay length used… |
| checkOut | string | yes | Departure date in ISO 8601 calendar format YYYY-MM-DD (e.g. '2026-07-22'). Must be strictly after checkIn on the same calendar. The guest does not stay the departure night. |
| guests | integer | – | Optional guest count (e.g. 4). Omit when only checking date availability without pricing. When provided, alternative date windows in the response include live host-source totals for that guest count. |
| propertyId | string | yes | Stable property UUID from hemmabo_search_properties (e.g. '550e8400-e29b-41d4-a716-446655440000'). Pass the exact UUID string — never a property name, host domain, or booking URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternativeDates | array | – | The host node's own next available window (at most one) to offer when the requested dates are unavailable — identical to the node's /api/availability nextAvailable. Empty when the node offers none. |
| available | boolean | yes | True if the property is bookable for the entire range. |
| calendar_freshness | object | – | Incoming OTA calendar-sync freshness at answer time. The same object is embedded in the error payload when a stale calendar blocks the call — declared here so agents can treat it as a first-class fie… |
| channel_mirror | object | – | Outbound channel-manager mirror heartbeat for the host's mapped external channel (status: current|stale|partial|error|not_connected). Informational only — it never affects `available`; the host node… |
| checkIn | string | – | – |
| checkOut | string | – | – |
| error | string | – | Present only when isError=true. |
| propertyId | string | – | – |
| reason | string | – | Reason when available=false. |
No examples provided.
hemmabo_check_host_readiness Host Readiness Check ~733
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City or municipality (e.g. 'Kävlinge', 'Florence'). Optional; used in onboarding URL prefill when provided. |
| country | string | – | Country where the property operates (e.g. 'Sweden', 'Italy', 'Morocco'). Optional; improves onboarding URL locale and fit assessment. |
| currentChannels | array | – | Optional list of channels the host uses today. Omit when unknown. Helps assess migration fit from OTAs to their own booking website. |
| domain | string | – | Host-owned domain without protocol or path (e.g. 'villaakerlyckan.se', 'myvilla.it'). Optional; omit when the host has not chosen a domain yet. Invalid: 'https://...', paths, ports, or booking URLs. |
| hasOwnDomain | boolean | – | True if the host already owns a domain or explicitly wants one (e.g. true for 'I have villaakerlyckan.se'). False or omit when still undecided. |
| preferredLanguage | string | – | ISO 639-1 language hint for onboarding copy (e.g. 'sv', 'en', 'de', 'fr'). Optional; omit to default to English. |
| propertyName | string | – | Property or business display name (e.g. 'Villa Åkerlyckan'). Optional; carried into onboarding URL when provided. |
| propertyType | string | – | Property category enum. Optional; omit when unknown. 'villa'/'holiday_home' fit best; 'hotel' may indicate a poor HemmaBo fit for large chains. |
| region | string | – | Region or area (e.g. 'Skåne', 'Toscana', 'Marrakech-Safi'). Optional; narrows onboarding handoff and proof examples. |
| wantsAiAgentBooking | boolean | – | True if the host wants AI agents (ChatGPT, Claude, Cursor) to discover and book via their own official website. False or omit when they only want a guest website. |
| wantsDirectPayments | boolean | – | True if the host wants Stripe Connect payouts direct to their account. False or omit when they expect HemmaBo to be merchant of record (not supported). |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_instruction | string | yes | How an AI agent should describe HemmaBo without overclaiming. |
| agent_role | string | yes | What a compatible agent does: discover the host domain, verify the signed stay offer, send the guest to that domain to book. The agent does not book. |
| next_step | object | yes | Safe handoff action for the host. |
| ok | boolean | yes | True when the fit check completed. |
| product | object | yes | HemmaBo: the category sentence, the host's subscription price atom, and the onboarding URL. |
| readiness | object | yes | Fit verdict and boundaries for the host's described need. |
| setup_items | array | yes | Inputs the host should prepare before onboarding. |
No examples provided.
hemmabo_get_host_onboarding_link Host Onboarding Link ~523
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City or municipality (e.g. 'Kävlinge', 'Florence'). Optional; used in onboarding URL prefill when provided. |
| country | string | – | Country where the property operates (e.g. 'Sweden', 'Italy', 'Morocco'). Optional; improves onboarding URL locale and fit assessment. |
| domain | string | – | Host-owned domain without protocol or path (e.g. 'villaakerlyckan.se', 'myvilla.it'). Optional; omit when the host has not chosen a domain yet. Invalid: 'https://...', paths, ports, or booking URLs. |
| language | string | – | ISO 639-1 language hint for onboarding copy (e.g. 'sv', 'en', 'de', 'fr'). Optional; omit to default to English. |
| propertyName | string | – | Property or business display name (e.g. 'Villa Åkerlyckan'). Optional; carried into onboarding URL when provided. |
| region | string | – | Region or area (e.g. 'Skåne', 'Toscana', 'Marrakech-Safi'). Optional; narrows onboarding handoff and proof examples. |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_role | string | yes | What a compatible agent does: discover the host domain, verify the signed stay offer, send the guest to that domain to book. The agent does not book. |
| next_step | object | yes | Safe handoff action for the host. |
| ok | boolean | yes | – |
| privacy_note | string | – | Clarifies that the call is read-only and does not store host data. |
| product | object | yes | HemmaBo: the category sentence, the host's subscription price atom ($39/month; the host pays it, a guest never does), and the onboarding URL. |
| setup_items | array | yes | Inputs the host should prepare before onboarding. |
No examples provided.
hemmabo_search_properties Search Properties ~500
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkIn | string | yes | Arrival date in ISO 8601 calendar format YYYY-MM-DD (e.g. '2026-07-15'). Must be today or later in the property's timezone. Must be strictly before checkOut; together they define the stay length used… |
| checkOut | string | yes | Departure date in ISO 8601 calendar format YYYY-MM-DD (e.g. '2026-07-22'). Must be strictly after checkIn on the same calendar. The guest does not stay the departure night. |
| country | string | – | Country name to filter by (e.g. 'Sweden', 'Italy', 'Morocco'). Partial case-insensitive match against the country field. Optional — omit both region and country and the search spans every published p… |
| guests | integer | yes | Total guest count as a positive integer (e.g. 2, 4, 6). Used for capacity filtering and staircase pricing tiers. Properties with maxGuests below this value are excluded from search results. |
| region | string | – | Region, area, or destination to search within (e.g. 'Skåne', 'Kävlinge', 'Toscana', 'Bavaria'). Partial case-insensitive match against region, city, and country. Optional — omit both region and count… |
| Name | Type | Req | Description |
|---|---|---|---|
| checkIn | string | – | Echoed check-in date (YYYY-MM-DD). |
| checkOut | string | – | Echoed check-out date (YYYY-MM-DD). |
| error | string | – | Present only when isError=true. |
| guests | integer | – | Echoed guest count. |
| properties | array | – | Available properties matching the search criteria: each host domain and its own booking URL, without a price. |
No examples provided.
vrp_get_verified_stay_offer Get Verified Stay Offer ~550
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkIn | string | yes | Requested arrival date in YYYY-MM-DD format (e.g. '2026-11-14'). Must be strictly before checkOut. Use the same dates the guest requested in search. |
| checkOut | string | yes | Requested departure date in YYYY-MM-DD format (e.g. '2026-11-17'). Must be strictly after checkIn. Guest does not stay the departure night. |
| domain | string | yes | Host-owned domain without protocol or path (e.g. 'villaakerlyckan.se', 'myvilla.it'). Invalid: 'https://...', paths, ports, or booking URLs. |
| guests | integer | yes | Total guest count as positive integer (e.g. 2, 4). Used by the host node for capacity validation and guest-tier pricing on the signed offer. |
| language | string | – | The guest's conversation language, as a BCP-47 tag (e.g. 'en', 'sv', 'de', 'sv-SE') — ALWAYS pass this, matching the language the guest is chatting in, so the rendered widget's labels, dates and curr… |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_citation | object | – | Citation permission and safe-to-quote status derived from the signed offer. |
| agent_guardrails | object | – | Rules the agent must follow when presenting or acting on this offer. |
| checkIn | string | – | Echoed requested arrival date. |
| checkOut | string | – | Echoed requested departure date. |
| domain | string | yes | Echoed host domain that issued the signed offer. |
| error | string | – | – |
| fresh | boolean | – | True when the signed offer is still within its validity/freshness window. |
| guests | integer | – | Echoed requested guest count. |
| official_offer_summary | object | – | Small signed-offer summary for agents to quote without inventing a price, a lower price, savings, availability, comparisons, or booking details. |
| payload_matches_offer | boolean | – | True when the signed payload matches the structured offer returned to the agent. |
| signature | object | – | Ed25519/JWS verification details, including key id and verification status. |
| verified | boolean | yes | True only when the host-domain offer signature and payload checks pass. |
| widget_media | object | – | Images and media hydrated from the verified host discovery document for the ChatGPT widget. |
No examples provided.
vrp_verify_node Verify Vacation Rental Node ~299
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Host-owned domain without protocol or path (e.g. 'villaakerlyckan.se', 'myvilla.it'). Invalid: 'https://...', paths, ports, or booking URLs. |
| Name | Type | Req | Description |
|---|---|---|---|
| discovery_url | string | – | The .well-known vacation-rental discovery URL read from the host domain. |
| domain | string | yes | Echoed canonical host domain that was checked. |
| error | string | – | Present when verified=false or the node cannot be checked. |
| jwks_url | string | – | Host-domain JWKS URL containing the Ed25519 public keys used to verify signed offers. |
| protocol | string | – | Protocol identifier discovered on the host domain. A valid node declares exactly 'vacation-rental-protocol' in its .well-known/vacation-rental.json protocol field, and that is the value returned here. |
| protocol_version | string | – | VRP version declared by the host discovery document. |
| signing | object | – | Summary of accepted signing algorithms, key ids, and signing-key checks. |
| verified | boolean | yes | True only when discovery, JWKS, signing metadata, and verified-offer endpoint checks pass. |
| verified_stay_offer_url | string | – | Host-domain endpoint template or URL used to request signed verified stay offers. |
No examples provided.
How do I install the HemmaBo Host Booking Engine MCP server?
HemmaBo Host Booking Engine is a hosted endpoint at https://www.hemmabo.com/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 · www.hemmabo.com
claude mcp add --transport http com-hemmabo-hemmabo-mcp-server 'https://www.hemmabo.com/mcp'
What is the HemmaBo Host Booking Engine MCP server?
HemmaBo Host Booking Engine is an MCP server listed in the public MCP registry as com.hemmabo/hemmabo-mcp-server. 6 runtime tools: 2 HemmaBo tools, 2 host onboarding tools, and 2 VRP verification tools. Not an OTA. This page covers its hosted endpoint (https://www.hemmabo.com/mcp).
Is the HemmaBo Host Booking Engine MCP server safe to use?
HemmaBo Host Booking Engine scores 81 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 HemmaBo Host Booking Engine MCP server expose?
HemmaBo Host Booking Engine exposes 6 tools: hemmabo_search_properties, hemmabo_check_availability, hemmabo_check_host_readiness, hemmabo_get_host_onboarding_link, vrp_verify_node, vrp_get_verified_stay_offer. Their descriptions and schemas cost roughly 3,157 tokens of context every time the server is loaded.
Does the HemmaBo Host Booking Engine MCP server require authentication?
Yes. HemmaBo Host Booking Engine asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the HemmaBo Host Booking Engine MCP server still maintained?
HemmaBo Host Booking Engine is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.