Skip to main content
Glama
Dudude-bit

yandex-lavka-mcp

by Dudude-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to yandex-lavka-mcp

No user-submitted related servers found.

    Related Servers

    • Yango Tech Retail MCP

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      Enables natural-language interaction with the Yango Tech Retail B2B API to create and track orders, browse product catalogs, and manage prices, discounts, and stock levels across darkstores.
      16
      57 npm
      MIT

    • AgentPay MCP

      zapnikita95
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search merchant catalogs, verify product prices and stock, and create purchases with budget limits and human-in-the-loop approval in Russian specialty stores.
      25
      4 npm
      Apache 2.0

    • Blinkit MCP

      SinghChinmay
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables assistants to search products, build and validate a Blinkit cart, manage delivery locations and addresses, and use saved staples or combos through Blinkit's JSON API while leaving payment to the user.
      MIT

    • MCP Picnic

      ivo-toby
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Picnic online supermarket for grocery shopping, meal planning, cart management, delivery tracking, and budget-conscious shopping in Netherlands and Germany.
      103 npm
      113
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools map to distinct resource+action pairs, but the location cluster (set_location, use_address, set_delivery_address) and the catalog cluster (list_categories vs get_category_group, which both surface categories by group) have overlapping purposes that could cause misselection. Descriptions do a good job clarifying the differences.

    Naming Consistency4/5

    The set is dominated by a predictable verb_noun pattern (get_product, list_categories, add_to_cart, set_payment_method, cancel_order), with a few noun-only outliers (active_orders, order_history, lavka_status, checkout_preview). Minor deviations, still clearly readable.

    Tool Count4/5

    22 tools is on the heavy side but justified by a genuinely broad domain spanning catalog browsing, cart, checkout, orders, payment, and addresses. Each tool earns a place, though the category-browsing tools could likely be consolidated.

    Completeness4/5

    The surface covers the full shopping lifecycle: discovery, cart mutation, preview, charge, cancel, order history, payment methods, and address/location setup. Minor gaps like deleting a saved address (only setting one exists) are workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources