Skip to main content
Glama
Sign In
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,738 npm
    2,032
    -

Related Servers

  • Google Hotels MCP

    huynhtanan
    A
    license
    A
    quality
    A
    maintenance
    Enables MCP clients to search live hotel and vacation-rental listings with the rate each booking site (Booking.com, Expedia, Agoda, Vrbo, Airbnb and others) is charging, and to pull a three-month daily price calendar for a single property. All results come back as JSON using a user-supplied Apify token, with no Google account or local scraping required.
    3
    1
    MIT
  • AirROI Airbnb MCP Server by airroi

    AirROI Airbnb MCP Serverofficial

    airroi
    A
    license
    Not graded
    quality
    C
    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
    C
    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

Each tool has a clearly distinct intent: search, single-property availability check, host-fit check, host onboarding link, node verification, and signed offer. The only friction points are hemmabo_check_availability vs. vrp_get_verified_stay_offer (yes/no vs. final price) and check_host_readiness vs. get_host_onboarding_link, but the descriptions explicitly draw these boundaries ('never call both in the same turn').

Naming Consistency4/5

Every name follows a predictable verb_noun pattern (check_availability, search_properties, verify_node, get_verified_stay_offer). The only deviation is the dual prefix (hemmabo_ vs. vrp_), which reflects two legitimate layers (platform vs. protocol) rather than arbitrary inconsistency.

Tool Count5/5

Six tools is well-scoped for a discovery-and-verification server: search, availability, offer, node verification, and two host-side entry points. Each tool earns its place with no redundancy.

Completeness4/5

The surface covers the full read-only guest journey (search → availability → verified offer) plus host onboarding and node trust, with booking intentionally excluded by design. Minor gap: no dedicated property/listing detail fetch, but search output largely covers that need.

Maintenance

ActivityActive
ResponsivenessSlow

Resources