F
licenseNot graded
qualityC
maintenanceEnables managing Ozon Seller and Performance APIs through MCP, covering products, stocks, prices, orders, finance, analytics, advertising, reviews, and chat operations.
-
ozon-customer-mcp
by Raleose
Related Servers
Alternatives to ozon-customer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables querying and comparing prices, availability, ratings, reviews, and seller details from major Russian and Chinese marketplaces (Wildberries, Ozon, Yandex Market, and others) without requiring API keys, via a unified MCP interface.424MIT
- AlicenseDqualityBmaintenanceEnables product search and price comparison across Ozon and Yandex Market via a read-only MCP server, returning normalized data with source URLs.6MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to search Amazon products, retrieve product details by ASIN, look up seller profiles, and browse seller catalogues as structured JSON across 23 regional Amazon domains.537 npm38 PyPI8MIT
- AlicenseAqualityBmaintenanceEnables querying DNS Shop product data via MCP: search, product details, reviews, specifications, variants, categories, brand catalogs, availability by city, and store listings.1218MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to search Walmart products by keyword or category, retrieve product details including the buy box and other sellers, and page through customer reviews with filters, all as structured JSON without a Walmart developer account.334 npm41 PyPI10MIT
TDQS
A4.2/5.0
Scored across 19 tools
Disambiguation5/5
Each tool maps to a distinct resource/action: search vs category browsing vs filters, product details vs specs vs variants vs offers vs reviews vs questions, and seller info vs seller catalog vs city lookup vs city setting. No two tools appear to do the same thing; close pairs like ozon_search and ozon_category_browse are clearly separated by text-search vs department-browsing.
Naming Consistency3/5
All tools share the consistent ozon_ prefix, which helps recognize them as a family. However, naming conventions are mixed: many are noun-first resources (ozon_product_details, ozon_seller_catalog) while several are verb-first actions (ozon_search_cities, ozon_set_city, ozon_compare_products), and ozon_search contains no noun at all. It is readable but not a uniform verb_noun pattern.
Tool Count4/5
19 tools is above the typical 3–15 sweet spot and feels slightly heavy, but the toolset covers a broad e-commerce domain with distinct workflows: search, category browsing, product details, variants, reviews, questions, offers, seller/brand catalogs, comparison, and delivery-city management. Each tool earns its place, so the count is reasonable rather than bloated.
Completeness5/5
The surface covers the full product-research lifecycle: category discovery, search/filtering, product details/specs/variants, social proof via reviews/questions/offers/seller info, comparison and related products, and delivery-location setup. There are no obvious dead ends or missing critical operations for a browsing-focused Ozon customer assistant.
Maintenance
ActivityMaintained
ResponsivenessNo issues