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 95/100 http no auth
At a glance
| Endpoint | https://hemmabo-mcp-server.vercel.app/mcp |
|---|---|
| Source | https://github.com/HemmaBo-se/hemmabo-mcp-server |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-05-23 10:09:43 |
| Last checked | 2026-11-17 21:48:16 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 305 / 704 ms |
| Last successful check | 2026-11-17 21:48:16 |
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:48:16 | ✓ | ✓ | 435 ms | 91 | active |
| 2026-11-17 21:33:11 | ✓ | ✓ | 413 ms | 91 | active |
| 2026-11-17 21:18:02 | ✓ | ✓ | 435 ms | 91 | active |
| 2026-11-17 21:02:59 | ✓ | ✓ | 401 ms | 91 | active |
| 2026-11-17 20:47:38 | ✓ | ✓ | 470 ms | 91 | active |
| 2026-11-17 20:32:32 | ✓ | ✓ | 356 ms | 91 | active |
| 2026-11-17 20:17:29 | ✓ | ✓ | 252 ms | 94 | active |
| 2026-11-17 20:01:55 | ✓ | ✓ | 285 ms | 94 | active |
| 2026-11-17 19:46:35 | ✓ | ✓ | 371 ms | 91 | active |
| 2026-11-17 19:31:32 | ✓ | ✓ | 309 ms | 91 | active |
| 2026-11-17 19:16:26 | ✓ | ✓ | 228 ms | 94 | active |
| 2026-11-17 19:00:47 | ✓ | ✓ | 400 ms | 91 | active |
| 2026-11-17 18:45:45 | ✓ | ✓ | 418 ms | 91 | active |
| 2026-11-17 18:30:44 | ✓ | ✓ | 218 ms | 94 | active |
| 2026-11-17 18:15:42 | ✓ | ✓ | 376 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://hemmabo-mcp-server.vercel.app/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/hemmabo-mcp-server-vercel-app-mcp # JSON