HemmaBo + VRP MCP server. 13 tools for host-domain signed verified stay offers.
HemmaBo + VRP MCP server. 13 tools for host-domain signed verified stay offers. Ed25519 JWKS verification. Not an OTA.
active Production-safe Score 93/100 http no auth
At a glance
| Endpoint | https://www.hemmabo.com/mcp |
|---|---|
| Source | https://github.com/HemmaBo-se/hemmabo-mcp-server |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-06-05 19:56:06 |
| Last checked | 2026-11-17 21:53:39 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 469 / 767 ms |
| Last successful check | 2026-11-17 21:53:39 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
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. Discoverhemmabo_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 finalhemmabo_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 andhemmabo_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 — ivrp_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/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 availabili
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:53:39 | ✓ | ✓ | 541 ms | 90 | active |
| 2026-11-17 21:38:32 | ✓ | ✓ | 475 ms | 90 | active |
| 2026-11-17 21:23:15 | ✓ | ✓ | 323 ms | 90 | active |
| 2026-11-17 21:08:02 | ✓ | ✓ | 501 ms | 90 | active |
| 2026-11-17 20:52:59 | ✓ | ✓ | 625 ms | 90 | active |
| 2026-11-17 20:37:57 | ✓ | ✓ | 411 ms | 90 | active |
| 2026-11-17 20:22:53 | ✓ | ✓ | 486 ms | 90 | active |
| 2026-11-17 20:07:43 | ✓ | ✓ | 799 ms | 90 | active |
| 2026-11-17 19:51:55 | ✓ | ✓ | 473 ms | 90 | active |
| 2026-11-17 19:36:48 | ✓ | ✓ | 471 ms | 90 | active |
| 2026-11-17 19:21:36 | ✓ | ✓ | 506 ms | 90 | active |
| 2026-11-17 19:06:23 | ✓ | ✓ | 462 ms | 90 | active |
| 2026-11-17 18:51:09 | ✓ | ✓ | 508 ms | 90 | active |
| 2026-11-17 18:36:01 | ✓ | ✓ | 569 ms | 90 | active |
| 2026-11-17 18:20:59 | ✓ | ✓ | 320 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://www.hemmabo.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/www-hemmabo-com-mcp # JSON