Skip to main content
Glama
toffguy77

winelab-mcp

by toffguy77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to winelab-mcp

No user-submitted related servers found.

    Related Servers

    • dns-customer-mcp

      Raleose
      A
      license
      A
      quality
      B
      maintenance
      Enables querying DNS Shop product data via MCP: search, product details, reviews, specifications, variants, categories, brand catalogs, availability by city, and store listings.
      18
      MIT

    • Knihobot MCP

      birosrichard
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to search the Knihobot.cz public book catalog, inspect live physical copies, compare editions, and retrieve recommendations.
      5
      ISC

    • globus-mcp

      toffguy77
      A
      license
      B
      quality
      B
      maintenance
      Enables LLM-driven interaction with the GLOBUS online store, including product search, catalog browsing, product details, promotions, recommendations, and anonymous shopping cart management via MCP.
      22
      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

    A3.6/5.0

    Scored across 15 tools

    Disambiguation5/5

    Every tool targets a distinct concern: product search/details, filters, regions/stores, cart, and auth. Even product_details and search_products, which both accept an article, are clearly differentiated by returning a full card versus search results.

    Naming Consistency3/5

    Naming is readable but mixes conventions: search_products/list_filters/set_region use verb_noun, product_details/store_details use noun_noun, cart_add/cart_view use noun_verb, and auth_status/auth_login use an auth prefix. The groupings help, but the pattern is inconsistent overall.

    Tool Count5/5

    15 tools is at the upper end of the ideal range but each tool earns its place across catalog search, regional/store context, cart, and account auth. No obvious fat or redundant tools.

    Completeness3/5

    Discovery, store, region, and auth flows are well covered, but the cart lifecycle is incomplete: cart_view and cart_add exist without cart_remove, quantity update, or clear cart. There is also no order/checkout surface, which is a notable gap for a retail e-commerce server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources