io.github.Dudude-bit/yandex-lavka-mcp
PYPI · YANDEX-LAVKA-MCP
Unofficial MCP server for ordering Yandex Lavka groceries: search, cart, checkout.
Available components
Last scanned (16 hours ago)
Scores higher than 82% of PyPI servers
Category E-commerce
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 hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 29 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1918 tokens (~87/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clear_cart" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 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
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 0
- Stability: 0.97 → pass security
- 2 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +16
- Malware scan: unverified → pass ▲ security
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/yandex-lavka-mcp@0.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
active_orders ~41
Currently tracked orders with status and ETA. Read-only. Covers in-progress orders (Lavka's order-tracking feed); past orders are in order_history.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
add_to_cart ~150
Add a product to the cart (increments if already present). No charge. `product_id` is the `id` from a search result. Pass `price` from the same search result when available (Lavka validates it on cart writes). IMPORTANT: search can return items that are only stocked in «Большая Лавка» (a different store) — they add fine but can't be ordered from the current one. After adding, check the returned cart's `warning` and each item's `unavailable_on_depot`; drop any flagged item with update_cart_item(id, 0).
| Name | Type | Req | Description |
|---|---|---|---|
| price | – | – | – |
| product_id | string | yes | – |
| quantity | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
cancel_order ~34
Cancel an order by id (e.g. one returned by confirm_order/active_orders).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
checkout_preview ~110
Preview the order: items, delivery fee, ETA, address, payment, TOTAL. Charges NOTHING. Show the returned total to the user and ask them to confirm it out loud before calling confirm_order. Always run this before confirming. If the summary has a `warning`, or `available_for_checkout` is false, or any item has `unavailable_on_depot: true`, the order will be REFUSED — fix the cart (remove/replace those items) and preview again before confirming.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
clear_cart ~17
Remove everything from the cart. No charge.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
confirm_order ~157
Place the order and CHARGE the card. Irreversible — real money. Call ONLY after checkout_preview was run and the user explicitly said yes to the previewed total. Pass that exact total as confirmed_total. The order is refused unless: a preview was run recently, confirmed_total matches it, and — critically — the live cart still matches the previewed cart at submit time (same version and total). If anything drifted, nothing is charged and you must preview + confirm again. Returns the order id and payment_status. "wait_user_action" means the bank requires 3-D Secure — give the user redirect_url to finish paying. cancel_order cancels.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed_total | number | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_category_group ~53
List the categories inside one catalog group, by group id. Group ids come from list_categories (each group carries an id). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | – |
| layout_slug | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_category_products ~182
List products in a catalog category. Read-only. Get `category_id` from list_categories or get_category_group. Returns the category's `subcategories` (id, title, product_count) plus up to `limit` products sorted as Lavka shows them — raise the limit to page further using `total_products`. Each result's `id` works with add_to_cart and its `slug` with get_product. Pass `subcategory` (an id or title from the result) to see only that shelf. `group_id`/`layout_slug` are only needed for non-grocery storefronts; without group_id the parent group is resolved via one extra lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | string | yes | – |
| group_id | – | – | – |
| layout_slug | string | – | – |
| limit | integer | – | – |
| subcategory | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_order ~45
Get full details of a specific order: items, totals, address, status, payment. Pass an order_id from order_history or active_orders.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_product ~314
Get one product: price, size, stock, description, nutrition. Read-only. `product` is an `id` or `slug` from a search result, or a Lavka link (a lavka.yandex.ru/good/... page or a shared ...?item=<id> link). `nutrition` is the КБЖУ block exactly as the product card shows it, numbers as Lavka gives them (nothing recomputed), or null when the card has none (non-food items): - `per_100g`: {kcal, protein, fat, carbs} per 100 g, or null. - `per_portion`: the same per the card's other tab, with its `label` ("Всё блюдо", "На упаковку", "На 50 г", ...), or null if the card has only one tab. - `default_basis`: the only tab ("per_100g" / "per_portion") when the card has one; null when it has both (Lavka doesn't say which one opens). - `portion_grams`: the portion's weight when the card states it (from the label, or the item's weight for a whole dish/pack), else null. - `warning`: null, or a note that per_portion doesn't follow from per_100g for that weight — Lavka's own data is wrong then; don't log it blindly.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lavka_status ~34
Show whether the Lavka session and delivery location are configured. Read-only. Call this first to check setup before other tools.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_addresses ~38
List your saved Lavka delivery addresses (by name). Read-only. Use a returned `label` with use_address to switch delivery to that place.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_categories ~110
Browse the Lavka catalog menu: category groups with their categories. Returns every `group` (id, title) and its `categories` (id, title) — use a category id with get_category_products. `layout_slug` picks the storefront: "grocery" (default) is the main food catalog; hubs like "pharmacy" (Аптека) and "pet_store" (Зоотовары) have their own. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| layout_slug | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_payment_methods ~52
List the user's saved cards and which is the default. Read-only. Use a returned `id` with set_payment_method to choose which card an order charges. By default the order uses the account default card.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
order_history ~68
Get list of past orders. Read-only. Use last_order_id from the last result for pagination (pass it as last_order_id to fetch the next page). Returns order id, status, total, items count, date.
| Name | Type | Req | Description |
|---|---|---|---|
| last_order_id | – | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_products ~62
Search the Lavka catalog at the current delivery location. Read-only. Each result has an `id` (use it with add_to_cart) and a `slug`; get_product takes either.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
set_delivery_address ~90
Set delivery to ANY address by free text — works for a new city. Resolves the address to coordinates + city/street/house via Lavka's own geo search. Example: set_delivery_address("Казань, улица Баумана, 1", flat="12").
| Name | Type | Req | Description |
|---|---|---|---|
| comment | – | – | – |
| entrance | – | – | – |
| flat | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
set_location ~57
Set the delivery location (required before catalog/cart calls). Provide either lat+lon coordinates or a saved address_id. Persists to config.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | – | – | – |
| label | – | – | – |
| lat | – | – | – |
| lon | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
set_payment_method ~50
Choose which saved card orders will charge (persists). Pass an `id` from list_payment_methods. Pass an empty string to revert to the account default.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_cart_item ~42
Set the exact quantity of a cart item. quantity=0 removes it. No charge.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | – |
| quantity | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
use_address ~83
Switch delivery to one of your saved addresses, matched by name. Catalog, cart and prices are location-scoped, so this re-points everything. A saved address carries city/street/house; pass flat/entrance/comment if the order needs them.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | – | – | – |
| entrance | – | – | – |
| flat | – | – | – |
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
view_cart ~129
Show the current cart contents and running total. Read-only. The cart also reports order-readiness. Watch these: - `warning`: a plain-language problem to fix (or null). If set, act on it. - each item's `unavailable_on_depot`: true = it's in the cart but CANNOT be ordered from the current store (only in «Большая Лавка», or sold out here). - `available_for_checkout`: false = the order can't be placed as-is. Remove/replace flagged items with update_cart_item(product_id, 0) before checkout.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.Dudude-bit/yandex-lavka-mcp server?
io.github.Dudude-bit/yandex-lavka-mcp runs locally as a PyPI package, launched with uvx yandex-lavka-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · yandex-lavka-mcp
claude mcp add dudude-bit-yandex-lavka-mcp -- uvx yandex-lavka-mcp
What is the io.github.Dudude-bit/yandex-lavka-mcp server?
io.github.Dudude-bit/yandex-lavka-mcp is listed in the public MCP registry as io.github.Dudude-bit/yandex-lavka-mcp. Unofficial MCP server for ordering Yandex Lavka groceries: search, cart, checkout. This page covers its PyPI package (yandex-lavka-mcp).
Is the io.github.Dudude-bit/yandex-lavka-mcp server safe to use?
io.github.Dudude-bit/yandex-lavka-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 io.github.Dudude-bit/yandex-lavka-mcp server expose?
io.github.Dudude-bit/yandex-lavka-mcp exposes 22 tools: lavka_status, set_location, list_addresses, use_address, set_delivery_address, and 17 more. Their descriptions and schemas cost roughly 1,918 tokens of context every time the server is loaded.
Is the io.github.Dudude-bit/yandex-lavka-mcp server still maintained?
io.github.Dudude-bit/yandex-lavka-mcp 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 io.github.Dudude-bit/yandex-lavka-mcp server under?
io.github.Dudude-bit/yandex-lavka-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.