Skip to main content
Glama
MeruLocal

hemmiles-mcp-server

by MeruLocal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hemmiles-mcp-server

No user-submitted related servers found.

    Related Servers

    • HitKeep

      PascaleBeier
      A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server for aggregate HitKeep analytics and official documentation, including traffic, events, goals, funnels, ecommerce, Search Console, and AI visibility reporting.
      16
      98
      MIT
    • aureum-website-mcp by aureum-technology

      aureum-website-mcpofficial

      aureum-technology
      F
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server of Aureum Technology GmbH (IT service provider, Rodewisch/Vogtland, Germany): company and contact data, service catalogue, current prices and full-text search across aureum-tech.com for AI assistants. Streamable HTTP at https://aureum-tech.com/mcp, read-only, no authentication.
      -
    • XTend hosted MCP by konnilabs

      XTend hosted MCPofficial

      konnilabs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables XTend developers and agents to search and retrieve canonical XTend documentation, recipes, and kit resources through read-only MCP tools, resources, and prompts served over stateless HTTP.
      Apache 2.0
    • easyhire-jobs by easyhireme

      easyhire-jobsofficial

      easyhireme
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for the public EasyHire job board. Enables searching job openings, retrieving full postings, filtering by criteria, and listing countries with open roles.
      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.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool maps to a distinct slice of the site (pages, search, features, pricing, resources, FAQs, policies, contact, company info), and descriptions explicitly cross-reference each other (e.g. get_page points to get_pricing/get_faqs). The only residual overlap is that get_page can return much of what get_pricing, get_faqs, and get_policies would, and get_company_info vs get_contact_options both surface contact data, but the guidance is clear enough that an agent can choose correctly.

    Naming Consistency5/5

    All ten tools use the same prefixed verb_noun snake_case pattern (hemmiles_get_*, hemmiles_list_*, hemmiles_search_*), with get_ for single-resource fetch, list_ for collections, and search_ for queries used consistently and semantically. No mixed conventions or casing deviations.

    Tool Count5/5

    Ten tools is well within the ideal 3-15 range and each corresponds to a real, non-redundant surface of a marketing/docs site. Nothing feels padded; each tool earns its place.

    Completeness4/5

    The surface covers discovery (list_pages, list_resources), retrieval (get_page), search, and the key content verticals (features, pricing, FAQs, policies, contact, company info), which is essentially full lifecycle for a read-only site server. Minor gaps: no way to enumerate integrations or teams/use-case pages as first-class lists, and no direct docs/help retrieval beyond get_page.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources