winelab-mcp
Related Servers
Alternatives to winelab-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables local MCP clients to search regional grocery products, authenticate with QR, inspect and modify a cart, preview checkout, and manage orders while requiring explicit confirmation for consequential writes.21GPL 3.0
- FlicenseNot gradedqualityDmaintenanceMCP server for VkusVill grocery store, enabling product search, details retrieval, and cart link creation.3-
- AlicenseAqualityCmaintenanceEnables querying DNS Shop product data via MCP: search, product details, reviews, specifications, variants, categories, brand catalogs, availability by city, and store listings.18MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to search Webhallen’s product catalog, browse categories, compare products, check current and 30-day-lowest prices, inspect physical-store stock, and read customer reviews.711 npm1MIT
- AlicenseAqualityDmaintenanceAn unofficial MCP server for interacting with Pyaterochka (5ka.ru) grocery store, enabling product search, cart management, and order delivery.244MIT
- FlicenseNot gradedqualityDmaintenanceConsumer-side MCP server for Webless storefront operations, enabling catalog browsing, product search, and order lookup via tools.-
TDQS
Scored across 15 tools
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 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.
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.
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.