Superzoo MCP
Related Servers
Alternatives to Superzoo MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables searching products, retrieving product details, listing stores, checking stock availability, and comparing prices across Czech DIY retailers.5MIT
- AlicenseNot gradedqualityCmaintenanceProvides LLM clients read-only access to product search, pricing, discounts, catalog categories, store locations, and per-store availability through the retailer's official integration API.MIT
- AlicenseAqualityCmaintenanceEnables read-only search and retrieval of the public Reknihy.cz book catalog, including filtering, sorting, ISBN lookup, category browsing, and access to product details such as price, availability, and images.4ISC
- AlicenseNot gradedqualityBmaintenanceEnables read-only product catalog search and detail retrieval, inventory checks, quotes, catalog audits, and JSON-LD export from validated local Japanese shop catalogs over MCP stdio. It does not support checkout, payments, reservations, or orders.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceSearch product catalogs across thousands of Central European e-shops. Semantic search, keyword matching, GTIN/EAN lookup — via REST API or MCP. \~2,500 e-shops | ~8.5M products | 7 countries (CZ, SK, PL, HU, RO, DE, AT)MIT
- AlicenseAqualityCmaintenanceEnables querying live offers and prices from 10 Dutch supermarket chains through a single normalised JSON API. Exposes 26 curated tools, including product search and category lookups, over stdio or authenticated Streamable HTTP.201MIT
TDQS
Scored across 3 tools
search_products, get_product, and get_product_availability target distinct actions (discovery, detail, store-level stock), and the descriptions clarify that get_product includes only availability summaries while get_product_availability is for one variant's store availability. There is mild overlap around availability, but the variant-specific scope of get_product_availability makes the boundary workable.
All three names follow a consistent snake_case verb_noun pattern: search_products, get_product, get_product_availability. The shared get_product prefix also makes the detail/availability relationship predictable.
Three tools are reasonable for a focused read-only product catalog: search, detail, and availability. The surface is slightly thin, but each tool has a clear role and the server does not appear to need broader mutation operations.
The core read-only product workflow is covered: find products, inspect product details and variants, and check store availability for a variant. Minor gaps exist, such as no standalone store listing or category browsing, but agents can work around these through search and product details.