A
licenseNot graded
qualityNot graded
maintenanceAn MCP server that provides tools for interacting with Supabase databases, storage, and edge functions.
45
MIT
HemmaBo
by HemmaBo-se
Related Servers
Alternatives to HemmaBo
- AlicenseNot gradedqualityCmaintenanceThe Stripe Model Context Protocol server allows you to integrate with Stripe APIs through function calling. This protocol supports various tools to interact with different Stripe services.13,246 npm1,827-
Related Servers
- AlicenseCqualityDmaintenanceThe only MCP server with AI guest risk scoring and extortion detection. Search properties, book instantly, protect hosts. 41 tools across 5 layers. Instant API key, 10 free credits.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of vacation rental properties through the Hostex API, including reservations, guest communications, availability calendars, reviews, and channel listings.1MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to search stays by destination and dates with rich filters and read full property details as structured JSON, without needing a Booking.com account or self-hosting.42515 npm87 PyPI18MIT
- AlicenseAqualityFmaintenanceReal-time last-minute tour and activity booking across 18 suppliers in 15 countries via the OCTO open standard. Search available slots, create Stripe checkout sessions, and check booking status.41MIT
- AlicenseAqualityCmaintenanceMCP server for a temporary rental catalog that enables property search and browsing via an interactive UI resource, including detailed listings and a simulated booking flow.338 npmApache 2.0
- -
TDQS
A4.6/5.0
Scored across 13 tools
Disambiguation4/5
Most tools have clear boundaries: search vs. availability vs. offer vs. quote are distinct stages, and booking lifecycle tools (create/status/cancel/reschedule) are well-separated. The main ambiguity is between hemmabo_booking_checkout and hemmabo_booking_create, which both create pending bookings in the fallback flow, though checkout adds Stripe payment while create does not.
Naming Consistency4/5
The hemmabo_ prefix is consistent, and most tools follow verb_noun patterns (search_properties, booking_cancel, host_onboarding_link). Minor deviations: get_verified_stay_offer and verify_vacation_rental_node use different verb styles, and hemmabo_booking_negotiate is misleadingly named since it locks a price rather than negotiating.
Tool Count4/5
13 tools is within the well-scoped range and each tool covers a distinct stage of the guest/host journey. Slightly heavy due to the fallback booking flow requiring three tools (negotiate, create, checkout) that overlap in purpose, but the count is reasonable for the domain.
Completeness4/5
The guest booking lifecycle is well covered: search, availability, quote, offer, create/checkout, status, cancel, reschedule. Host-side coverage is thinner (readiness check and onboarding link only, no host management tools), and there is no explicit tool for updating a booking's guest details, but core workflows are complete.
Maintenance
ActivityActive
ResponsivenessSlow