A
licenseA
qualityD
maintenanceAn unofficial MCP server for interacting with Pyaterochka (5ka.ru) grocery store, enabling product search, cart management, and order delivery.
24
4
MIT
Greenweez MCP
by ncleton
Related Servers
Alternatives to Greenweez MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for browsing Glovo stores, menus, products, and managing a basket via API calls without checkout or payment.273MIT
- AlicenseNot gradedqualityAmaintenanceMCP server enabling search and retrieval of public SensCritique data, including works, user profiles, and collections.7 npm1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for VkusVill grocery store, enabling product search, details retrieval, and cart link creation.3-
- AlicenseAqualityDmaintenanceMCP server for Open Food Facts, enabling food product lookup by barcode, search, nutrition facts, allergen checks, and eco-scores without an API key.8MIT
- AlicenseNot gradedqualityBmaintenanceUnofficial MCP and CLI server to read a user's current E.Leclerc Drive catalog through a persistent Camoufox browser session, enabling product search, product and cart reading, and confirmed cart add/remove operations without placing orders or making payments.1MIT
TDQS
A3.6/5.0
Scored across 8 tools
Disambiguation4/5
Most tools are clearly distinct: search vs get product, add vs remove, preview vs confirm. However, the preview/confirm pairs (4 tools) could cause an agent to misselect between the add and remove variants without careful reading, and connect_greenweez vs get_cart have somewhat related 'session/account' purposes.
Naming Consistency4/5
The tool names follow a consistent verb_noun pattern: get_, search_, connect_, preview_, confirm_ prefixes all with clear object names (cart, product, add_to_cart, remove_from_cart). The naming is largely consistent, with preview/confirm pairs being well-paired. Minor deviation: connect_greenweez uses verb_domain-service instead of verb_noun, depa...
Tool Count4/5
8 tools is a reasonable, well-scoped count for an e-commerce cart/catalog server. Each tool maps to a distinct part of the shopping workflow (connect, search, browse, add, remove). Slightly on the larger side but appropriate for the domain.
Completeness4/5
The server covers the core shopping flow: connecting, searching, viewing products, adding and removing from cart. Notable gaps include a dedicated 'update cart quantity' tool (only add-one/remove-whole-line exist) and no checkout/order placement, but the stated scope (browse and manage cart) is largely covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues