Skip to main content
Glama
HemmaBo-se

HemmaBo

by HemmaBo-se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to HemmaBo

  • stripe by stripe

    stripeofficial

    stripe
    A
    license
    Not graded
    quality
    C
    maintenance
    The 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.
    21,341 npm
    1,865
    -

Related Servers

  • AirROI Airbnb MCP Server by airroi

    AirROI Airbnb MCP Serverofficial

    airroi
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants to query short-term rental market data—occupancy, ADR, RevPAR, revenue estimates, comparables, live calendars, search rank, and pricing recommendations—for 20M+ listings across 190+ countries via a remote Streamable HTTP API.
    MIT

  • Hostex MCP Server

    keithah
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables management of vacation rental properties through the Hostex API, including reservations, guest communications, availability calendars, reviews, and channel listings.
    1
    MIT
  • Tell & Go by tell-and-go

    Tell & Goofficial

    tell-and-go
    A
    license
    Not graded
    quality
    B
    maintenance
    Lets any MCP-compatible AI agent search live resort inventory, request exact all-in quotes including transfers, and start real hotel bookings that the traveler completes on a hosted Stripe checkout.
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have distinct roles: guest discovery, availability confirmation, host fit check, onboarding handoff, node verification, and offer fetching. The main risk is hemmabo_search_properties vs hemmabo_search_availability, but the descriptions explicitly separate browsing from confirming a selected property. verify_vacation_rental_node vs get_verified_stay_offer are also well delineated by their 'trust check' vs 'fetch offer' framing.

Naming Consistency3/5

Four tools use a hemmabo_ prefix (search_properties, search_availability, host_readiness_check, host_onboarding_link) while two do not (verify_vacation_rental_node, get_verified_stay_offer). The verb_noun shape is roughly consistent but the prefix scheme is split, which breaks predictability.

Tool Count5/5

Six tools is well-scoped for a two-sided guest/host flow with a verification step. Each tool earns its place, and nothing appears redundant or padding.

Completeness4/5

The guest lifecycle (search → availability → verify domain → verified offer) and host lifecycle (readiness → onboarding) are covered, with booking deliberately routed to the host's signed direct_booking_url. The absence of any booking/checkout tool is intentional, but agents expecting an in-server booking step have no direct handle for it.

Maintenance

ActivityActive
ResponsivenessSlow

Resources