Is com.hemmabo/hemmabo-mcp-server up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://www.hemmabo.com/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: `supportedInterfaces` is required and must name at least one interface (ยง5.7). neither the 1.0 nor the 0.3 shape; 3 skills./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://www.hemmabo.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, does not validate: `$schema` is required (and 4 more). SEP-1649 shape; hemmabo-mcp-server 5.0.1./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://www.hemmabo.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 6 tools: get_verified_stay_offer, hemmabo_host_onboarding_link, hemmabo_host_readiness_check, hemmabo_search_availability, hemmabo_search_properties, verify_vacation_rental_node.
Its tools changed between 2026-09 and 2026-10:
- Removed (7):
hemmabo_booking_cancel,hemmabo_booking_checkout,hemmabo_booking_create,hemmabo_booking_negotiate,hemmabo_booking_quote,hemmabo_booking_reschedule,hemmabo_booking_status get_verified_stay_offer: description changedhemmabo_host_onboarding_link: description, output schema changedhemmabo_host_readiness_check: description, output schema changedhemmabo_search_availability: description, output schema changedhemmabo_search_properties: description, input schema, output schema changedverify_vacation_rental_node: description changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.hemmabo/hemmabo-mcp-server |
|---|---|
| Endpoint | https://www.hemmabo.com/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt