Home Servers com.hemmabo/hemmabo-mcp-server ASSESSMENT #AIM-2026-000422
com.hemmabo/hemmabo-mcp-server Automated only com.hemmabo/hemmabo-mcp-server
Host-owned vacation-rental direct booking via VRP. Signed offers, 0% commission. Not an OTA.
Remote server — connect via: https://www.hemmabo.com/mcp Running any third-party MCP server executes its code with the permissions you grant it. A grade reflects our findings at the “last verified” date below — verify independently before installing in a sensitive environment.
Should you install this?
Freshness (good, 85/100), Maintenance (weak, 68/100), Provenance (fair, 70/100) so far. Safety hasn't been assessed yet — this is a partial picture, not a complete grade.
Last verified 2026-08-14
Dispute this grade Last commit: 2026-08-13T17:32:54Z 2026-08-14 · GitHub Last release: 2026-08-13T17:32:55Z 2026-08-14 · GitHub Endpoint status: unknown (No scan data yet) 2026-08-14 · Security scan 3 human contributor(s). 2026-08-14 · GitHub Last release: 2026-08-13T17:32:55Z 2026-08-14 · GitHub Issue close rate: 73% 2026-08-14 · GitHub Registry namespace verified. 2026-08-14 · MCP Registry Not from a known official vendor. 2026-08-14 · MCP Registry No installable package — this server is remote-hosted, so package attestation doesn't apply. 2026-08-14 · MCP Registry io.github.RAHULTRIPGAIN/tripgain-mcp-server
Corporate travel booking and expense management for TripGain, exposed as an MCP server.
Pending eu.departi/travel-compliance
Travel-compliance intelligence and curated booking for digital nomads and long-stay travellers.
Pending com.shaq-log/freight-mcp
Real-time ocean freight rates, LCL pricing, and booking management for global logistics.
io.github.xsronhou/scrapio-mcp
Fetch, crawl, and search the web: Google, Amazon, Walmart, Booking.com, Agoda, and YouTube data.
Pending io.github.NORTHTEKDevs/lossless-context-mcp
Agent context flight recorder: restore after compaction, fan-out packs, signed git-bound receipts.
Pending Historical grade tracking becomes available once this server has been through at least two sync cycles — the longitudinal dataset is what answers “is this server getting worse?”
Maintainer of this server? Dispute a finding or trigger a re-scan after a fix.