hemmabo-mcp-server.vercel.app
https://hemmabo-mcp-server.vercel.app/api/mcp
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://hemmabo-mcp-server.vercel.app/api/mcp |
|---|---|
| Source | https://hemmabo-mcp-server.vercel.app/mcp |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-05-23 14:24:14 |
| Last checked | 2026-11-17 21:48:30 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 323 / 681 ms |
| Last successful check | 2026-11-17 21:48:30 |
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:30 | ✓ | ✓ | 213 ms | 94 | active |
| 2026-11-17 21:33:25 | ✓ | ✓ | 408 ms | 91 | active |
| 2026-11-17 21:18:16 | ✓ | ✓ | 337 ms | 91 | active |
| 2026-11-17 21:03:12 | ✓ | ✓ | 386 ms | 91 | active |
| 2026-11-17 20:47:53 | ✓ | ✓ | 224 ms | 94 | active |
| 2026-11-17 20:32:47 | ✓ | ✓ | 233 ms | 94 | active |
| 2026-11-17 20:17:43 | ✓ | ✓ | 211 ms | 94 | active |
| 2026-11-17 20:02:09 | ✓ | ✓ | 215 ms | 94 | active |
| 2026-11-17 19:46:50 | ✓ | ✓ | 239 ms | 94 | active |
| 2026-11-17 19:31:47 | ✓ | ✓ | 387 ms | 91 | active |
| 2026-11-17 19:16:39 | ✓ | ✓ | 324 ms | 91 | active |
| 2026-11-17 19:00:59 | ✓ | ✓ | 230 ms | 94 | active |
| 2026-11-17 18:45:58 | ✓ | ✓ | 329 ms | 91 | active |
| 2026-11-17 18:30:57 | ✓ | ✓ | 603 ms | 91 | active |
| 2026-11-17 18:15:54 | ✓ | ✓ | 214 ms | 94 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://hemmabo-mcp-server.vercel.app/api/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/hemmabo-mcp-server-vercel-app-api-mcp # JSON