# Яндекс Маркет MCP (RU) (pypi · yandex-market-mcp-ru)

API Яндекс Маркета в ИИ-ассистенте: заказы, товары, цены, отчёты, отзывы

- Trust score: 53/100 (low)
- Change this week: −14
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `yandex-market-mcp-ru`: 53/100 (this document), [markdown](https://verifymcp.io/servers/ilyautov-yandex-market-mcp-ru/yandex-market-mcp-ru.md), [page](https://verifymcp.io/servers/ilyautov-yandex-market-mcp-ru/yandex-market-mcp-ru)

## Channel facts

- Registry: `pypi`
- Package: `yandex-market-mcp-ru`
- Version: `0.6.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3319 tokens (~127/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 25/100
  - Stability check failed: the tool surface changed between 0.5.3 and 0.6.0: 1 tool removals, 0 breaking changes, 5 additions.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 95/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 4 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ym_call_method" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Яндекс Маркет MCP (RU) server?

Яндекс Маркет MCP (RU) runs locally as a PyPI package, launched with uvx yandex-market-mcp-ru. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ilyautov-yandex-market-mcp-ru -- uvx yandex-market-mcp-ru
```

### Cursor

```json
{
  "mcpServers": {
    "ilyautov-yandex-market-mcp-ru": {
      "command": "uvx",
      "args": [
        "yandex-market-mcp-ru"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ilyautov-yandex-market-mcp-ru": {
      "command": "uvx",
      "args": [
        "yandex-market-mcp-ru"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ilyautov-yandex-market-mcp-ru -- uvx yandex-market-mcp-ru
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ilyautov-yandex-market-mcp-ru": {
      "type": "local",
      "command": [
        "uvx",
        "yandex-market-mcp-ru"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ilyautov-yandex-market-mcp-ru --command uvx --arg yandex-market-mcp-ru
```

### Hermes

```yaml
mcp_servers:
  ilyautov-yandex-market-mcp-ru:
    command: "uvx"
    args: ["yandex-market-mcp-ru"]
```

### Netclaw

```json
{
  "McpServers": {
    "ilyautov-yandex-market-mcp-ru": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "yandex-market-mcp-ru"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ilyautov-yandex-market-mcp-ru -t stdio -c uvx -a yandex-market-mcp-ru
```

### Other

```json
{
  "mcpServers": {
    "ilyautov-yandex-market-mcp-ru": {
      "command": "uvx",
      "args": [
        "yandex-market-mcp-ru"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 22 to 25.

### 2026-09-18 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 15 to 19.

### 2026-09-17 (score 51, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-16 (score 66, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 50, −17)

- [security regression] Malware scan: pass → unverified
- [security regression] Stability: 0.07 → fail
- [functional regression] Schema quality: 2654 → 3319
- [functional] Schema quality: excellent → good
- [functional] Destructive annotations: 4 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ym_call_method" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does.
- [functional] Package version: 0.5.4 → 0.6.0

### 2026-09-13 (score 67, +16)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.5.3 → 0.5.4

### 2026-09-12 (score 51, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-11 (score 66)

First indexed and scored.

## MCP tools (26)

### `ym_check_auth` (~54 tokens)

Check whether the required credentials are present in the environment.

Does NOT reveal secret values — only reports which variables are set.
Returns JSON: {"ready": bool, "missing": [str], "required": [str]}.

Output parameters:

- `result` (string)

### `ym_list_sections` (~20 tokens)

List API sections and how many catalog endpoints each contains.

Output parameters:

- `result` (string)

### `ym_get_section` (~58 tokens)

List all endpoints in one section.

Args:
    section: section name (see ym_list_sections), e.g. "statistics".
Returns JSON list of {operation_id, method, path, safety, summary}.

Input parameters:

- `section` (string, required)

Output parameters:

- `result` (string)

### `ym_search_methods` (~78 tokens)

Search the endpoint catalog by keyword (works in Russian and English).

Args:
    query: free text, e.g. "остатки", "stocks", "update price".
    limit: max results (1-50).
Returns JSON list of matching endpoints (best first).

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (string)

### `ym_map` (~81 tokens)

The big picture: business entities this API covers and the go-to
methods for each. Call with no args to see the whole map ("you are
here"); pass entity="reviews" (or stocks/prices/orders/…) to list every
method of one entity. Use this before guessing — it orients you fast.

Input parameters:

- `entity` (string)

Output parameters:

- `result` (string)

### `ym_describe_method` (~49 tokens)

Return the full catalog record for one endpoint: method, host, path,
scope, safety level, pagination style, rate limit, params and doc URL.

Input parameters:

- `operation_id` (string, required)

Output parameters:

- `result` (string)

### `ym_call_method` (~161 tokens)

Execute one READ endpoint from the catalog by operation_id.

Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.

Reads only: nothing here changes data, so it runs without confirmation.
To change data use ym_write_method, to delete use ym_delete_method.

Args:
    operation_id: id from the catalog (see ym_search_methods).
    path_values: values for {placeholders} in the path.
    query: query-string parameters.
    body: JSON request body (a few read endpoints take one).
Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Input parameters:

- `body`
- `operation_id` (string, required)
- `path_values`
- `query`

Output parameters:

- `result` (string)

### `ym_write_method` (~171 tokens)

Execute one WRITE endpoint from the catalog: create or update data.

Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.

Requires confirm_write=true; nothing is sent without it. Irreversible
operations live in ym_delete_method, reads in ym_call_method.

Args:
    operation_id: id from the catalog (see ym_search_methods).
    path_values: values for {placeholders} in the path.
    query: query-string parameters.
    body: JSON request body.
    confirm_write: must be true.
Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Input parameters:

- `body`
- `confirm_write` (boolean)
- `operation_id` (string, required)
- `path_values`
- `query`

Output parameters:

- `result` (string)

### `ym_delete_method` (~194 tokens)

Execute one DESTRUCTIVE endpoint: deletes or irreversibly changes data.

Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.

Both confirm_write=true and i_understand_this_modifies_data=true are
required; nothing is sent without both.

Args:
    operation_id: id from the catalog (see ym_search_methods).
    path_values: values for {placeholders} in the path.
    query: query-string parameters.
    body: JSON request body.
    confirm_write: must be true.
    i_understand_this_modifies_data: must be true.
Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Input parameters:

- `body`
- `confirm_write` (boolean)
- `i_understand_this_modifies_data` (boolean)
- `operation_id` (string, required)
- `path_values`
- `query`

Output parameters:

- `result` (string)

### `ym_get_raw` (~180 tokens)

Read ANY endpoint by path, including ones missing from the catalog.

Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.

Safe verbs only (GET, HEAD, OPTIONS). To change data use
ym_write_raw, to delete use ym_delete_raw.

Args:
    path: full path beginning with '/', e.g. "/v2/regions".
    method: safe verb, GET by default.
    host: host override; defaults to the service's default host.
    query: query-string parameters.
    body: JSON request body (rare on reads; some APIs want one).
Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Input parameters:

- `body`
- `host`
- `method` (string)
- `path` (string, required)
- `query`

Output parameters:

- `result` (string)

### `ym_write_raw` (~166 tokens)

Create or update data at ANY path, including paths not in the catalog.

Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.

POST, PUT and PATCH only; requires confirm_write=true.

Args:
    method: POST, PUT or PATCH.
    path: full path beginning with '/'.
    host: host override; defaults to the service's default host.
    query: query-string parameters.
    body: JSON request body.
    confirm_write: must be true.
Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Input parameters:

- `body`
- `confirm_write` (boolean)
- `host`
- `method` (string, required)
- `path` (string, required)
- `query`

Output parameters:

- `result` (string)

### `ym_delete_raw` (~194 tokens)

Delete data at ANY path, including paths not in the catalog.

Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.

DELETE only. Both confirm_write=true and
i_understand_this_modifies_data=true are required.

Args:
    path: full path beginning with '/'.
    method: DELETE.
    host: host override; defaults to the service's default host.
    query: query-string parameters.
    body: JSON request body.
    confirm_write: must be true.
    i_understand_this_modifies_data: must be true.
Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Input parameters:

- `body`
- `confirm_write` (boolean)
- `host`
- `i_understand_this_modifies_data` (boolean)
- `method` (string)
- `path` (string, required)
- `query`

Output parameters:

- `result` (string)

### `ym_fetch_all` (~195 tokens)

Auto-paginate a read endpoint and return every row in one response.

Handles offset, last_id, cursor (Ozon v4/v5), page and WB lastChangeDate
styles. The array path is taken from the catalog automatically.

Args:
    operation_id: a read endpoint from the catalog.
    query / body / path_values: base parameters (cursor fields are managed).
    items_path: override the array path (default: the endpoint's own).
    limit: page size to request.
    max_items: hard cap to protect context (default 10000).
Returns JSON: {"ok", "items", "total_fetched", "pages_fetched", "truncated"}.

Input parameters:

- `body`
- `items_path`
- `limit` (integer)
- `max_items` (integer)
- `operation_id` (string, required)
- `path_values`
- `query`

Output parameters:

- `result` (string)

### `ym_list_cabinets` (~53 tokens)

List configured cabinets for this marketplace and which one is active.

Returns JSON: {"active": str|null, "cabinets": [names], "fields_needed": [...]}.
Secret values are never returned.

Output parameters:

- `result` (string)

### `ym_add_cabinet` (~218 tokens)

Add or update a cabinet (a named set of API credentials), from chat.

⚠️ This puts the key into the chat transcript — requires
i_understand_key_goes_to_chat=true. The terminal-free safe alternative is
the installer (install.py / double-click), where the key never enters chat.

Args:
    credentials: dict with the required fields for this service
        ({fields}). For Ozon: {{"client_id": "...", "api_key": "..."}};
        for WB: {{"token": "..."}}.
    name: optional label. If omitted, the cabinet is named after the real
        shop name fetched from the marketplace (falls back to "main").
    i_understand_key_goes_to_chat: must be true to proceed.
Saved to ~/.marketplace-mcp/cabinets.json (local, chmod 600), never echoed.

Input parameters:

- `credentials` (object, required)
- `i_understand_key_goes_to_chat` (boolean)
- `name` (string)

Output parameters:

- `result` (string)

### `ym_set_key` (~221 tokens)

Change / rotate the API key from chat (e.g. the old one expired or
leaked).

⚠️ The key goes into the chat transcript — requires
i_understand_key_goes_to_chat=true. The safe, terminal-free alternative
is the installer, where the key never enters chat. Use a scoped key and
rotate it in the seller cabinet if it was exposed.

Args:
    credentials: dict with the required fields ({fields}).
    cabinet: which cabinet to update. Default: the active one (so "my key
        expired" just works). If there is none, the cabinet is named from
        the marketplace's shop name, else "main".
    i_understand_key_goes_to_chat: must be true to proceed.
On success the key is validated against the marketplace and the shop name
is reported. Saved locally (chmod 600), never echoed back.

Input parameters:

- `cabinet` (string)
- `credentials` (object, required)
- `i_understand_key_goes_to_chat` (boolean)

Output parameters:

- `result` (string)

### `ym_use_cabinet` (~48 tokens)

Switch the active cabinet. Subsequent API calls use its credentials.

Args:
    name: the cabinet to activate (see ym_list_cabinets).

Input parameters:

- `name` (string, required)

Output parameters:

- `result` (string)

### `ym_remove_cabinet` (~42 tokens)

Delete a stored cabinet. If it was active, another becomes active.

Args:
    name: the cabinet to remove.

Input parameters:

- `name` (string, required)

Output parameters:

- `result` (string)

### `ym_list_workflows` (~54 tokens)

List ready-made analytical workflows (recipes) for this marketplace.

Returns JSON: [{name, category, when_to_use}]. Use {svc}_get_workflow
to fetch the full step-by-step plan for one.

Output parameters:

- `result` (string)

### `ym_get_workflow` (~65 tokens)

Return the full plan for one workflow: ordered steps (each naming a
catalog operation_id and why), interpretation guidance, and common
mistakes to avoid.

Args:
    name: workflow name (see {svc}_list_workflows).

Input parameters:

- `name` (string, required)

Output parameters:

- `result` (string)

### `ym_get_campaigns` (~141 tokens)

List the seller's shops (кампании) with their campaignId and businessId.

Call this first: nearly every other Yandex Market method needs a campaignId
(магазин) or businessId (кабинет продавца). Both are in the response:
campaigns[].id and campaigns[].business.id.

Args:
    page_token: pageToken from a previous page (empty for the first page).
    limit: page size (<=100).
Returns JSON: {"ok": true, "data": {"campaigns": [...], "paging": {...}}}.

Input parameters:

- `limit` (integer)
- `page_token` (string)

Output parameters:

- `result` (string)

### `ym_get_orders` (~211 tokens)

List orders of one shop (GET /v2/campaigns/{campaignId}/orders).

Args:
    campaign_id: shop id from ym_get_campaigns.
    status: filter, e.g. PROCESSING | DELIVERY | PICKUP | DELIVERED |
        CANCELLED | UNPAID (comma-separated allowed). Empty = all.
    from_date: order creation date lower bound, DD-MM-YYYY (Yandex format).
    to_date: upper bound, DD-MM-YYYY.
    page_token: pageToken from a previous page.
    limit: page size (<=50).
Returns JSON: {"ok": true, "data": {"orders": [...], "paging": {...}}}.
For every order across pages use ym_fetch_all with ym_get_orders.

Input parameters:

- `campaign_id` (integer, required)
- `from_date` (string)
- `limit` (integer)
- `page_token` (string)
- `status` (string)
- `to_date` (string)

Output parameters:

- `result` (string)

### `ym_get_offers` (~150 tokens)

List the seller's offers (товары) with their Market card mapping
(POST /v2/businesses/{businessId}/offer-mappings).

Args:
    business_id: cabinet id (campaigns[].business.id).
    offer_ids: comma-separated offerId (SKU) filter; empty = all.
    page_token: pageToken from a previous page.
    limit: page size (<=200).
Returns JSON: {"ok": true, "data": {"result": {"offerMappings": [...], "paging": {...}}}}.

Input parameters:

- `business_id` (integer, required)
- `limit` (integer)
- `offer_ids` (string)
- `page_token` (string)

Output parameters:

- `result` (string)

### `ym_get_stocks` (~170 tokens)

Stock per offer per warehouse for one shop, with optional turnover
(POST /v2/campaigns/{campaignId}/offers/stocks).

Args:
    campaign_id: shop id.
    offer_ids: comma-separated offerId filter; empty = all.
    with_turnover: also return turnover (оборачиваемость) per offer.
    page_token: pageToken from a previous page.
    limit: page size (<=200).
Returns JSON: {"ok": true, "data": {"result": {"warehouses": [{"warehouseId", "offers": [...]}]}}}.

Input parameters:

- `campaign_id` (integer, required)
- `limit` (integer)
- `offer_ids` (string)
- `page_token` (string)
- `with_turnover` (boolean)

Output parameters:

- `result` (string)

### `ym_get_prices` (~129 tokens)

Base prices set for all shops of the cabinet
(POST /v2/businesses/{businessId}/offer-prices).

Args:
    business_id: cabinet id.
    offer_ids: comma-separated offerId filter; empty = all.
    page_token: pageToken from a previous page.
    limit: page size (<=200).
Returns JSON with result.offers[].price {value, currencyId, discountBase, updatedAt}.

Input parameters:

- `business_id` (integer, required)
- `limit` (integer)
- `offer_ids` (string)
- `page_token` (string)

Output parameters:

- `result` (string)

### `ym_set_price` (~216 tokens)

Set the base price of ONE offer for all shops of the cabinet
(POST /v2/businesses/{businessId}/offer-prices/updates). WRITE.

Requires confirm_write=true. discount_base is the strikethrough price
(must be higher than price); 0 = no discount shown.

Args:
    business_id: cabinet id.
    offer_id: seller's SKU (offerId).
    price: new price, e.g. 1499.
    discount_base: pre-discount price, or 0 to clear.
    currency: RUR (default) — Yandex uses "RUR", not "RUB".
    confirm_write: must be true to send.
Returns JSON: {"ok": true, "data": {"status": "OK"}} on success.

Input parameters:

- `business_id` (integer, required)
- `confirm_write` (boolean)
- `currency` (string)
- `discount_base` (number)
- `offer_id` (string, required)
- `price` (number, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/ilyautov-yandex-market-mcp-ru/yandex-market-mcp-ru#diagnostics

## Score history

- 2026-09-20: 53
- 2026-09-19: 52
- 2026-09-18: 52
- 2026-09-17: 51
- 2026-09-16: 66
- 2026-09-15: 50
- 2026-09-14: 50
- 2026-09-13: 67
- 2026-09-12: 51
- 2026-09-11: 66

## Common questions

### What is the Яндекс Маркет MCP (RU) server?

Яндекс Маркет MCP (RU) is listed in the public MCP registry as io.github.ilyautov/yandex-market-mcp-ru. API Яндекс Маркета в ИИ-ассистенте: заказы, товары, цены, отчёты, отзывы. This page covers its PyPI package (yandex-market-mcp-ru).

### Is the Яндекс Маркет MCP (RU) server safe to use?

Яндекс Маркет MCP (RU) scores 53 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Яндекс Маркет MCP (RU) server expose?

Яндекс Маркет MCP (RU) exposes 26 tools: ym_check_auth, ym_list_sections, ym_get_section, ym_search_methods, ym_map, and 21 more. Their descriptions and schemas cost roughly 3,319 tokens of context every time the server is loaded.

### Is the Яндекс Маркет MCP (RU) server still maintained?

Яндекс Маркет MCP (RU) is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/yandex-market-mcp-ru/
- Socket report: https://socket.dev/pypi/package/yandex-market-mcp-ru
- Repository: https://github.com/ilyautov/yandex-market-mcp-ru
- Website: https://marketplaces-mcp-ru.aifrontier.tech/yandex-market-api.html
- Changelog RSS feed: https://verifymcp.io/servers/ilyautov-yandex-market-mcp-ru/yandex-market-mcp-ru.xml
- Changelog JSON feed: https://verifymcp.io/servers/ilyautov-yandex-market-mcp-ru/yandex-market-mcp-ru.json
- HTML version of this page: https://verifymcp.io/servers/ilyautov-yandex-market-mcp-ru/yandex-market-mcp-ru