ozon-connectorlisted
Install: claude install-skill Vladimir-Human/ru-marketplace-mcp
# Ozon Connector
Two-tier connector. Tier 1 is `curl_cffi` with TLS impersonation and handles most
queries — no browser involved. Only when Cloudflare serves a JS challenge does the
fetch fall back to tier 2, inside the operator's logged-in Chrome over the DevTools
Protocol. Plain curl/httpx fails outright (307 loop on the TLS fingerprint), which is
why tier 1 impersonates and tier 2 exists at all.
## Prerequisite
Nothing to set up for tier 1. For the tier-2 fallback, Chrome is started on first use
by `mcp_core.transport.chrome_cdp` if the CDP port is not already listening, into a
dedicated `%LOCALAPPDATA%\Chrome-Scraping` profile. From a Russian residential IP
tier 1 usually answers and Chrome is never touched.
## When to use
- Product detail: price, rating, seller, characteristics
- Search Ozon catalog
- Cross-check Ozon vs WB prices
## Tools available
- `ozon_card(sku_or_path)` — fetch full product card via composer-api.bx
- `ozon_search(query, page)` — search Ozon catalog; `page` is 1..10, one page per call
- `ozon_reviews(sku_or_path, limit, sort)` — product reviews; the rating and the
star distribution belong to the card family's review POOL, not to the SKU you
asked for
**Not an MCP tool:** `ozon_selfcheck()` is a drift canary: `success` means both
tiers answered, `inconclusive` means Chrome was unreachable, `drift_detected`
means the payload shape moved. It is CLI-only — `marketplace-mcp doctor` runs
every connector's canary at once.
## Workflow
1. `ozon_sea