Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Авито MCP (RU)

PYPI · AVITO-MCP-RU

API Авито в ИИ-ассистенте: объявления, чаты, заказы, автозагрузка, отзывы

Available components

−5 this week 87 Trust /100

Last scanned (16 hours ago)

Scores higher than 89% of PyPI servers

Category E-commerce

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ilyautov/avito-mcp-ru). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 50 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3528 tokens (~117/item across 30 items; 30 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety95
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 4 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "avito_call_method" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 −6
    • Stability: pass → 0.60 functional
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
  • 20 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 19 Oct 26 +1
    • Stability: fail → pass ▲ security
  • 17 Oct 26 +2
    • Stability: 0.83 → fail ▼ security
  • 15 Oct 26 +40
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → 0.80 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 5 Oct 26 −38
    • Tool safety: pass → unverified ▼ security
    • Stability: fail → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed pypi/avito-mcp-ru@0.6.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo ilyautov/avito-mcp-ru
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ilyautov/avito-mcp-ru/.github/workflows/publish-pypi.yml@refs/tags/v0.6.0
Rekor log index 2831873466
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:1ba07b213b7bfdfc0f81561b9571ec272d8a805592a43ab2b68b92e320a9d472

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 30 packages
Packages resolved 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 30 exposed · ~3,528 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
avito_add_cabinet ~219

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.

NameTypeReqDescription
credentialsobjectyes–
i_understand_key_goes_to_chatboolean––
namestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_call_method ~160

Execute one READ endpoint from the catalog by operation_id. Target API: https://developers.avito.ru/api-catalog. Reads only: nothing here changes data, so it runs without confirmation. To change data use avito_write_method, to delete use avito_delete_method. Args: operation_id: id from the catalog (see avito_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.

NameTypeReqDescription
body–––
operation_idstringyes–
path_values–––
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_check_auth ~55

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]}.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

avito_delete_method ~191

Execute one DESTRUCTIVE endpoint: deletes or irreversibly changes data. Target API: https://developers.avito.ru/api-catalog. 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 avito_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.

NameTypeReqDescription
body–––
confirm_writeboolean––
i_understand_this_modifies_databoolean––
operation_idstringyes–
path_values–––
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_delete_raw ~190

Delete data at ANY path, including paths not in the catalog. Target API: https://developers.avito.ru/api-catalog. 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.

NameTypeReqDescription
body–––
confirm_writeboolean––
host–––
i_understand_this_modifies_databoolean––
methodstring––
pathstringyes–
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_describe_method ~50

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

NameTypeReqDescription
operation_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_fetch_all ~196

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"}.

NameTypeReqDescription
body–––
items_path–––
limitinteger––
max_itemsinteger––
operation_idstringyes–
path_values–––
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_balance ~52

Wallet balance: real money and bonuses (GET /core/v1/accounts/{user_id}/balance/). Returns JSON: {"ok": true, "data": {"real": ..., "bonus": ...}}.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_chats ~149

Buyer chats (GET /messenger/v2/accounts/{user_id}/chats). Requires the Messenger API to be enabled on the seller's Avito plan. Args: unread_only: only chats with unread messages. item_ids: comma-separated listing ids to filter chats by. limit: page size (<=100). offset: pagination offset (<=1000). Returns JSON: {"ok": true, "data": {"chats": [{"id", "context", "last_message", "users"}]}}.

NameTypeReqDescription
item_idsstring––
limitinteger––
offsetinteger––
unread_onlyboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_item_stats ~141

Views / contacts / favorites per listing per period (POST /stats/v1/accounts/{user_id}/items). Up to 200 ids, 270 days deep. Args: item_ids: comma-separated listing ids. date_from: YYYY-MM-DD (inclusive). date_to: YYYY-MM-DD (inclusive). period_grouping: day | week | month. Returns JSON with result.items[].stats[] {date, uniqViews, uniqContacts, uniqFavorites}.

NameTypeReqDescription
date_fromstringyes–
date_tostringyes–
item_idsstringyes–
period_groupingstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_items ~179

List the seller's listings (объявления): status, category, url (GET /core/v1/items). Max 25 requests/min. Args: status: active | removed | old | blocked | rejected (comma-separated ok). category: Avito category id filter, 0 = all. updated_from: YYYY-MM-DD lower bound on the listing update date. page: 1-based page number. per_page: page size (<100). Returns JSON: {"ok": true, "data": {"meta": {...}, "resources": [...]}}. For all pages use avito_fetch_all with avito_get_items_info.

NameTypeReqDescription
categoryinteger––
pageinteger––
per_pageinteger––
statusstring––
updated_fromstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_orders ~182

Orders placed with Авито Доставка (GET /order-management/1/orders). Business (B2C) sellers only. Args: statuses: comma-separated filter: on_confirmation, ready_to_ship, in_transit, canceled, delivered, on_return, in_dispute, closed. date_from: unix timestamp — only orders created after it. page: 1-based page number. limit: page size (<=20). Returns JSON: {"ok": true, "data": {"orders": [...], "hasMore": bool}}. Each order has availableActions (confirm / reject / setTrackNumber …) and schedules (deadlines such as confirmTill, shipTill).

NameTypeReqDescription
date_frominteger––
limitinteger––
pageinteger––
statusesstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_raw ~178

Read ANY endpoint by path, including ones missing from the catalog. Target API: https://developers.avito.ru/api-catalog. Safe verbs only (GET, HEAD, OPTIONS). To change data use avito_write_raw, to delete use avito_delete_raw. Args: path: full path beginning with '/', e.g. "/core/v1/items". 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.

NameTypeReqDescription
body–––
host–––
methodstring––
pathstringyes–
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_reviews ~110

Published reviews on the seller with score, text, deal stage and the seller's answer (GET /ratings/v1/reviews). Use avito_get_ratings_info_v1 via avito_call_method for the aggregate rating. Args: offset: pagination offset. limit: page size (<=50). Returns JSON: {"ok": true, "data": {"total": n, "reviews": [...]}}.

NameTypeReqDescription
limitinteger––
offsetinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_section ~60

List all endpoints in one section. Args: section: section name (see avito_list_sections), e.g. "statistics". Returns JSON list of {operation_id, method, path, safety, summary}.

NameTypeReqDescription
sectionstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_stocks ~88

Stock per listing (POST /stock-management/1/info): quantity, is_unlimited, is_out_of_stock. Up to 500 ids per call. Args: item_ids: comma-separated Avito listing ids. Returns JSON: {"ok": true, "data": {"stocks": [{"item_id", "quantity", ...}]}}.

NameTypeReqDescription
item_idsstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_get_workflow ~66

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).

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_list_cabinets ~54

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

avito_list_sections ~21

List API sections and how many catalog endpoints each contains.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

avito_list_workflows ~55

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

avito_map ~82

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.

NameTypeReqDescription
entitystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_remove_cabinet ~43

Delete a stored cabinet. If it was active, another becomes active. Args: name: the cabinet to remove.

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_search_methods ~79

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).

NameTypeReqDescription
limitinteger––
querystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_set_key ~222

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.

NameTypeReqDescription
cabinetstring––
credentialsobjectyes–
i_understand_key_goes_to_chatboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_update_price ~130

Set the price of ONE listing (POST /core/v1/items/{item_id}/update_price). WRITE. Requires confirm_write=true. Goods, spare parts, cars, real estate only; max 150 requests/min. Args: item_id: Avito listing id. price: new price in roubles (integer). confirm_write: must be true to send. Returns JSON: {"ok": true, "data": {"result": {"success": true}}}.

NameTypeReqDescription
confirm_writeboolean––
item_idintegeryes–
priceintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_update_stock ~128

Set the available quantity of ONE listing (PUT /stock-management/1/stocks). WRITE. Requires confirm_write=true. quantity 0 hides the "buy with delivery" button. Args: item_id: Avito listing id. quantity: units available (0..999999). confirm_write: must be true to send. Returns JSON: {"ok": true, "data": {"stocks": [{"item_id", "success", "errors"}]}}.

NameTypeReqDescription
confirm_writeboolean––
item_idintegeryes–
quantityintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_use_cabinet ~50

Switch the active cabinet. Subsequent API calls use its credentials. Args: name: the cabinet to activate (see avito_list_cabinets).

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_whoami ~66

Authorized Avito account: id (needed as user_id in many methods), name, email, phone, profile_url. Also the cheapest way to verify the credentials. Returns JSON: {"ok": true, "data": {"id": ..., "name": ..., ...}}.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

avito_write_method ~170

Execute one WRITE endpoint from the catalog: create or update data. Target API: https://developers.avito.ru/api-catalog. Requires confirm_write=true; nothing is sent without it. Irreversible operations live in avito_delete_method, reads in avito_call_method. Args: operation_id: id from the catalog (see avito_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.

NameTypeReqDescription
body–––
confirm_writeboolean––
operation_idstringyes–
path_values–––
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

avito_write_raw ~162

Create or update data at ANY path, including paths not in the catalog. Target API: https://developers.avito.ru/api-catalog. 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.

NameTypeReqDescription
body–––
confirm_writeboolean––
host–––
methodstringyes–
pathstringyes–
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the Авито MCP (RU) server?

Авито MCP (RU) runs locally as a PyPI package, launched with uvx avito-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.

pypi · avito-mcp-ru

# add to Claude Code
claude mcp add ilyautov-avito-mcp-ru -- uvx avito-mcp-ru
Common questions

What is the Авито MCP (RU) server?

Авито MCP (RU) is listed in the public MCP registry as io.github.ilyautov/avito-mcp-ru. API Авито в ИИ-ассистенте: объявления, чаты, заказы, автозагрузка, отзывы. This page covers its PyPI package (avito-mcp-ru).

Is the Авито MCP (RU) server safe to use?

Авито MCP (RU) scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 30 tools: avito_check_auth, avito_list_sections, avito_get_section, avito_search_methods, avito_map, and 25 more. Their descriptions and schemas cost roughly 3,528 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Авито MCP (RU) server under?

Авито MCP (RU) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.