Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Ozerki via AgentPay is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Ozerki pharmacy catalog, local pickup availability and tracked basket handoff for AI agents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ozerki-via-agentpay-mcp https://agentpay.shop/ap/mcp/ozerki
# 2 — ask your agent for something these tools do
# list_allowed_stores, search_products, get_product and 5 more
Ozerki via AgentPay costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ozerki-via-agentpay-mcp https://agentpay.shop/ap/mcp/ozerkiReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List stores on this agent's allowlist. The agent MUST shop only here. Never invent a shop, never open a random website to pay. Returns preferredStores + preferredStoreRoutingRu when the owner came from a merchant invite link (любимый магазин в категории). Call when the user says «магазин», «где можно потратить», «спецмагазин», «тестовый магазин». Set demoOnly=true when the owner explicitly asks ab
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | no | Optional topic to match, e.g. техника. Prefer peek_stores for a quiet offer. |
| demoOnly | boolean | no | True only for an explicit demo/test-catalog request. Excludes live partner stores from the answer. |
Search products in allowlisted AgentPay stores. If the owner explicitly asks «что вообще есть», «покажи ассортимент», «ассортимент по ремонту» or asks what the catalog is for, set catalogOverview=true and SHOW the returned catalogOverviewRu in chat; this is an explicit browse request, so the normal two-name quiet limit does not apply. For «демо-каталог» or test shops also set demoOnly=true; discus
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Product search query (min 2 chars). Prefer this field. Example: йогурт, протеин 80. |
| query | string | no | Alias of q — product search string, not an address. |
| search | string | no | Alias of q — product search string, not an address. |
| need | string | no | Alias of q — product search string, not an address. |
| text | string | no | Alias of q — PRODUCT search string only. Do NOT put city/street/phone here (use save_delivery_address for that). |
| storeId | string | no | Optional allowlisted store id |
| limit | number | no | Max hits per store, 1–20 (default 10) |
| location | string | no | Optional city or region explicitly named by the owner, for example Москва or Санкт-Петербург. Omit when geography is unknown. For metro/street/district, follow search with get_ozerki_pickup_options. |
| regionId | number | no | Optional explicit Ozerki region id. Omit unless known; location is preferred for a named city. |
| demoOnly | boolean | no | True for an explicit demo/test-catalog request. Excludes live partner stores such as Dixy and Ozerki. |
| catalogOverview | boolean | no | True when the owner explicitly asks to see or understand the assortment. Returns a grouped overview that should be shown in chat. |
Get one ProductCard by product_id + store_id from an allowlisted store. Public/demo catalog needs no authorization. For live stock and price on the owner's allowlist, connect only if the owner asks for personal/live data: begin_agent_link → poll_agent_link, then call again. Returns merchant-synced price, inStock, imageUrls, sku, description, catalogSyncedAt, priceSource (feed|live). Always include
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | — |
| store_id | string | yes | — |
| q | string | no | Optional owner query so pick.whyRu is about this search |
Create a comparison page (choice board, 2–4 options with pros/cons). MANDATORY when search_products returns 2+ similar hits or clarifyHint.action is present_choices — call immediately, do not wait for «сравни». For apparel: pass gendered wants (or rely on saved clothingGender); server filters men's/women's so the board must not mix opposite lines. For a basket/recipe: pass kind=bundles and wants[{
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agentIntroRu | string | yes | Short RU intro: why you are asking, not choosing for them |
| kind | string | no | alternatives | bundles |
| wants | array | no | Search queries for each slot / product to compare |
| canRenderImages | boolean | no | — |
Poll a choice set from present_choices. Returns status draft|chosen and chosenOptionId. Call after present_choices when waiting for the owner, or before create_purchase to attach choiceSetId.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| choice_set_id | string | yes | — |
Ozerki pickup-point resolver for multi-brand Ozerki-network pharmacies. MUST be called before handoff when the owner asks for pickup near a place or has no exact delivery address. An exact address is NOT required for pickup: pass the intended goodsId basket (include each product name so missingItems are human-readable) and near with at least city + metro/street/district (for example 'метро Белорус
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | — |
| near | string | no | User's metro station, district, street, or exact pharmacy address, including city. A city name alone is insufficient. |
| exactPharmacy | boolean | no | Set true only when the owner asks about one specific pharmacy; read exactPharmacyResult and never substitute a different nearby branch. |
| lat | number | no | — |
| lon | number | no | — |
| regionId | number | no | Ozerki region id, default 14 for Moscow and region |
| limit | number | no | Nearest complete-basket options to return, default 3, max 10 |
Ozerki-only availability preflight and tracked basket handoff. Call only after fulfillment is agreed with the owner. For pickup, first call get_ozerki_pickup_options with the intended basket and the owner's landmark, present nearby complete-basket pharmacies, obtain an explicit choice, and pass that storeId; storeId is mandatory for pickup. Never leave pharmacy selection for the owner after handof
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | — |
| fulfillment | string | yes | — |
| regionId | number | no | Ozerki region id, default 14 for Moscow and region |
| storeId | string/number | no | Required for pickup: store id explicitly chosen by the owner from get_ozerki_pickup_options |
| address | object | no | — |
Look up AgentPay operational FAQ before guessing. Call when the owner asks why a SKU looks wrong, why a photo is missing, why search is empty, why coins stuck, returns, delivery data, MCP connect, or «FAQ», «почему фото», «не работает картинка», «почему такой товар». Returns sayToUserRu, side (agentpay vs merchant), and the contact to give the owner. Do not invent a reason. Do not hide whose side
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | Owner question or error phrase in Russian or English |
| storeId | string | no | Optional store UUID when the issue is about a shop |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ozerki via AgentPay or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Ozerki via AgentPay can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.