Yango Tech Retail MCP
NPM · MCP-YANGO-RETAIL · SCANNED SEP 23
MCP server for the Yango Tech Retail B2B API: orders, products, prices, discounts, stocks.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
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 35 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2766 tokens (~172/item across 16 items; 16 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 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
How do I install the Yango Tech Retail MCP server?
Yango Tech Retail MCP runs locally as an npm package, launched with npx -y mcp-yango-retail. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-yango-retail
claude mcp add a1-x-tech-mcp-yango-retail -- npx -y mcp-yango-retail
{
"mcpServers": {
"a1-x-tech-mcp-yango-retail": {
"command": "npx",
"args": [
"-y",
"mcp-yango-retail"
]
}
}
} {
"servers": {
"a1-x-tech-mcp-yango-retail": {
"command": "npx",
"args": [
"-y",
"mcp-yango-retail"
]
}
}
} codex mcp add a1-x-tech-mcp-yango-retail -- npx -y mcp-yango-retail
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"a1-x-tech-mcp-yango-retail": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-yango-retail"
],
"enabled": true
}
}
} openclaw mcp add a1-x-tech-mcp-yango-retail --command npx --arg -y --arg mcp-yango-retail
mcp_servers:
a1-x-tech-mcp-yango-retail:
command: "npx"
args: ["-y", "mcp-yango-retail"] {
"McpServers": {
"a1-x-tech-mcp-yango-retail": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-yango-retail"
]
}
}
} assistant mcp add a1-x-tech-mcp-yango-retail -t stdio -c npx -a -y mcp-yango-retail
{
"mcpServers": {
"a1-x-tech-mcp-yango-retail": {
"command": "npx",
"args": [
"-y",
"mcp-yango-retail"
]
}
}
} 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.
- 23 Sept 26 0
- Package version: 1.0.0 → 1.1.0 functional
- 22 Sept 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.
- 20 Sept 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.
- 18 Sept 26 −3
- Stability: pass → 0.77 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
- Package version: 1.0.0 → 1.1.0 functional
- 12 Sept 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.
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 23 Sept 2026 · Analysed npm/mcp-yango-retail@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
cancel_order Cancel an order ~90
Cancels an existing order (POST /b2b/v1/orders/cancel). Optionally pass a reason. The response body is not documented upstream and is returned verbatim; verify the outcome with get_orders_state (expect canceled or pending_cancel).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id (the client-side id the order was created with). |
| reason | string | – | Free-form cancellation reason. |
No output schema declared.
No examples provided.
create_discounts Create discounts ~130
Creates per-store product discounts (POST /b2b/v1/discounts/create), at most 100 per request. CAUTION: the exact key names inside discount_activity_period and discount_value are NOT documented (the official client types them as plain string→string maps with no example) — confirm the expected keys with Yango Tech before relying on this tool, and note there is no endpoint to list or delete discounts. The response body is not documented upstream (2xx = success) and is returned verbatim.
| Name | Type | Req | Description |
|---|---|---|---|
| discounts | array | yes | Discounts to create (at most 100 per request). |
No output schema declared.
No examples provided.
create_order Create an order ~302
Creates an order on the Yango Tech platform (POST /b2b/v1/orders/create). You supply the order_id; the same body shape is used by the platform for order updates. All money fields are decimal STRINGS (e.g. "150.00"), never numbers. The response body is not documented upstream and is returned verbatim. After creation, track progress with get_orders_state (get_order does NOT return the state).
| Name | Type | Req | Description |
|---|---|---|---|
| cart | object | – | Shopping cart: items plus totals (all money as decimal strings). |
| client_phone_number | string | – | Customer phone number in international format. |
| courier_pin | string | – | PIN the courier must present on handover. |
| delivery_address | object | – | Delivery address: coordinates plus optional structured address and comment. |
| delivery_properties | object | – | Delivery properties: type and optional {start, end} slot. |
| human_order_id | string | – | Human-readable order number shown to the customer. |
| order_id | string | yes | Client-side order id (you choose it; reuse it in the other order tools). |
| payment_type | string | – | Payment type. Known values: cash, online, card, apple_pay, loyalty (the list is open-ended). |
| store_id | string | – | WMS store (darkstore) id from get_stores. |
| use_external_logistics | boolean | – | true — delivery is handled by external (3PL) logistics instead of the platform. |
No output schema declared.
No examples provided.
create_products Create or update products ~128
Creates (or upserts) products in the catalog (POST /b2b/v1/products/create), at most 100 per request. Each product uses the same shape query_products returns: {product_id, master_category, status, is_meta, custom_attributes}. custom_attributes must include longName ({lang: text}), shortNameLoc, markCount and markCountUnitList; extra keys are passed through. The response body is not documented upstream (2xx = success) and is returned verbatim.
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | Products to create/upsert (at most 100 per request). |
No output schema declared.
No examples provided.
get_order Get order details ~88
Details of a single order (POST /b2b/v1/orders/get): every field the order was created with (cart, delivery_address, payment_type, store_id, …) plus create_time. NOTE: the response does NOT include the order state — use get_orders_state for tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id (the client-side id the order was created with). |
No output schema declared.
No examples provided.
get_orders_state Get order states (batch) ~121
Batch order tracking (POST /b2b/v1/orders/state). Returns {query_results: [{order_id, query_result, state?}]} — query_result reports per-order lookup success (an unknown id is reported here, not as an HTTP error). Known states: draft, checked_out, reserving, reserved, postpone_reserving, postponed, assembling, assembled, courier_assigned, delivering, closed, pending_cancel, canceled (the list is open-ended).
| Name | Type | Req | Description |
|---|---|---|---|
| orders | array | yes | Order ids to check (client-side ids used at creation). |
No output schema declared.
No examples provided.
get_prices Get prices ~89
Product prices for one or more price lists (POST /b2b/v1/prices/get). Returns {results: [{pricelist_id, prices_data: [{product_id, price, price_per_quantity?}]}]}. price may arrive as a number or a string — treat it as a decimal either way.
| Name | Type | Req | Description |
|---|---|---|---|
| pricelist_ids | array | yes | Price-list ids from query_price_lists. |
No output schema declared.
No examples provided.
get_receipt Get fiscal receipts ~189
Fiscal receipt(s) by receipt id OR order id (POST /b2b/v1/receipts/get) — pass exactly one of the two. Returns {receipts: [{receipt_id, order, create_time, store, receipt_type (payment|refund), payment_methods, items, client?}]}; items is a map keyed by item id, and all amounts are decimal strings. Client PII (full_name, phone_number, email, delivery_address) is included only for the fields you list in client_fields.
| Name | Type | Req | Description |
|---|---|---|---|
| client_fields | array | – | Which client PII fields to include in the response (omitted = no PII). |
| order_id | string | – | Order id to fetch receipts for. Mutually exclusive with receipt_id. |
| receipt_id | string | – | Receipt id (e.g. from a receipt_issued order event). Mutually exclusive with order_id. |
No output schema declared.
No examples provided.
get_stores List stores ~85
All stores (darkstores) of the retailer (POST /b2b/v1/stores/get, no parameters). Returns {stores: [{id, status, location: {lat, lon}, address?, name?}]}. The store id is the WMS store id used by create_order, update_stocks and create_discounts; status values are not enumerated upstream.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_order_events Poll the order event feed ~149
Cursor-based order event feed (POST /b2b/v1/orders/events/query): new orders, state changes and issued receipts. Returns {cursor, orders_events: [{order_id, occurred, data: {type, …}}]} where data.type is state_change (with current_state), new_order, or receipt_issued (with receipt_id). Omit cursor for the first call, then keep passing the returned cursor — the feed is continuous, so poll again later with the last cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from the previous response of this tool. Omit it for the first page; the feed is exhausted when a page comes back with fewer items than `limit`. |
No output schema declared.
No examples provided.
query_price_lists Query price lists ~183
Cursor-based price-list feed (POST /b2b/v1/pricelists/query) — the API's only way to list price lists, so a full snapshot means iterating until a page has fewer items than limit. Returns {pricelists: [{id, name, status (active|removed)}], cursor}. Price-list ids feed get_prices and set_prices. Related endpoints without a dedicated tool (pricelists/get, pricelists/create, store-pricelist-links/*) are reachable via raw_request.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from the previous response of this tool. Omit it for the first page; the feed is exhausted when a page comes back with fewer items than `limit`. |
| limit | integer | – | Page size (default 100 — the official client's value; the server-side maximum is undocumented). |
No output schema declared.
No examples provided.
query_products Query the product catalog ~207
Cursor-based product catalog / product-updates feed (POST /b2b/v1/products/query). Returns {products, cursor}; iterate until a page has fewer items than limit to build a full snapshot. Each product: {product_id, master_category, status (active|disabled|archived), is_meta, custom_attributes}. custom_attributes carries localized maps (longName, shortNameLoc, descriptionLoc: {lang: text}), markCount + markCountUnitList (unit/gram/kilogram/liter/millilitre — open-ended), barcode[], images[], typeAccounting (byUnit|byWeight|byTrueWeight) and arbitrary extra attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from the previous response of this tool. Omit it for the first page; the feed is exhausted when a page comes back with fewer items than `limit`. |
| limit | integer | – | Page size (default 300 — the official client's value; the server-side maximum is undocumented). |
No output schema declared.
No examples provided.
query_stocks Query stock levels ~194
Cursor-based stock feed across stores (POST /b2b/v1/stocks/query). Returns {stocks: [{product_id, quantity, shelf_type, store_id}], cursor}; iterate until a page has fewer items than limit for a full snapshot. Known shelf_type values (open-ended): store, markdown, incoming, out, trash, lost, found, office, parcel, parcel_returned, collection, cargo, repacking, review, kitchen_on_demand, kitchen_components, kitchen_trash, kitchen_lost, kitchen_found. Sellable stock normally lives on shelf_type "store".
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from the previous response of this tool. Omit it for the first page; the feed is exhausted when a page comes back with fewer items than `limit`. |
| limit | integer | – | Page size (default 100 — the official client's value; the server-side maximum is undocumented). |
No output schema declared.
No examples provided.
raw_request Raw Yango Tech Retail API call ~194
Escape hatch: direct call to any Yango Tech Retail B2B endpoint — for paths without a dedicated tool (orders/update, receipts/documents/upload, wms/picking/set-state, logistics/delivery/set-state, products-vat/*, pricelists/get|create, store-pricelist-links/*, 3pl/deliveries/*). Every endpoint of this API is a POST with a JSON body; pass a relative path like "b2b/v1/pricelists/get" and the body object. CAUTION: this tool can perform writes; 5xx/network errors are never retried for it.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON request body (defaults to {} — the API expects a JSON object on every call). |
| path | string | yes | Relative API path, e.g. "b2b/v1/pricelists/get". Absolute URLs are rejected (SSRF guard). |
No output schema declared.
No examples provided.
set_prices Set prices ~108
Sets product prices in price lists (POST /b2b/v1/prices/set), at most 100 per request. Prices are decimal STRINGS (e.g. "150.00"); price_per_quantity (pack size the price applies to) defaults to 1 when omitted. The response body is not documented upstream (2xx = success) and is returned verbatim. There is no delete endpoint for prices.
| Name | Type | Req | Description |
|---|---|---|---|
| prices | array | yes | Price assignments (at most 100 per request). |
No output schema declared.
No examples provided.
update_stocks Update stock quantities ~161
Writes stock quantities for one store. mode=modify (default) POSTs /b2b/v1/stocks/update with update_mode "modify" (at most 1000 items per request); mode=initialize POSTs /b2b/v1/stocks/initialize for the first-time stock load of a store. The response body is not documented upstream (2xx = success) and is returned verbatim. Verify the result with query_stocks.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | modify (default) — regular stock update; initialize — first-time stock load of a store. |
| stocks | array | yes | Stock lines to write (at most 1000 per request). |
| store_id | string | yes | WMS store id from get_stores. |
No output schema declared.
No examples provided.
What is the Yango Tech Retail MCP server?
Yango Tech Retail MCP is listed in the public MCP registry as io.github.A1-x-Tech/mcp-yango-retail. MCP server for the Yango Tech Retail B2B API: orders, products, prices, discounts, stocks. This page covers its npm package (mcp-yango-retail).
Is the Yango Tech Retail MCP server safe to use?
Yango Tech Retail MCP scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. It declares no install or post-install scripts. 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 Yango Tech Retail MCP server expose?
Yango Tech Retail MCP exposes 16 tools: create_order, cancel_order, get_order, get_orders_state, query_order_events, and 11 more. Their descriptions and schemas cost roughly 2,418 tokens of context every time the server is loaded.
Is the Yango Tech Retail MCP server still maintained?
Yango Tech Retail MCP is still listed as active in the MCP registry. We last reached this channel on 23 September 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 Yango Tech Retail MCP server under?
Yango Tech Retail 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.