Skip to main content
Glama

Related Servers

Alternatives to aukro-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      F
      maintenance
      Remote MCP server (Streamable HTTP) that reads and parses the public catalog website atcmarket.cz (AT Computers) to enable product search, category-filtered search, supported filter listing, product detail lookup, and cross-product comparison — without login or state.
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for interacting with Bazos.cz, Bazos.sk, Bazos.at, and Bazos.pl. Supports searching ads, retrieving ad details, and fetching user ratings.
      3
      86 npm
      4
      AGPL 3.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that provides Hugging Face Hub API and Search endpoints through multiple transport protocols (STDIO, SSE, StreamableHTTP, and StreamableHTTPJson), enabling integration with AI model capabilities.
      314
      MIT

    TDQS

    A3.7/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (search vs autocomplete, offer detail vs status batch vs bids, watchlist vs favourites, buyer vs seller views). A few pairs like get_offer_detail/get_offers_status_batch and my_bids_and_purchases/my_sales could be momentarily confused, but descriptions clarify the boundaries.

    Naming Consistency4/5

    All tools use the aukro_ prefix and snake_case, with mostly verb_noun patterns (search_offers, get_categories, place_bid, manage_offer). A handful of noun-only multi-action tools (watchlist, cart, messages, my_account, offer_templates) deviate slightly but follow a coherent convention.

    Tool Count3/5

    25 tools is heavy and sits at the upper boundary of the rubric's 'borderline' range. While each tool covers a distinct function across a full marketplace domain, the surface feels large and could likely be consolidated.

    Completeness4/5

    The set covers a broad marketplace lifecycle: browsing/search, offer detail, bidding, cart, seller offer management, messaging, and user info. Notable gaps remain (no checkout/order finalization, no feedback submission, no way to save a new search despite listing/removing saved searches), but core workflows are usable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues