"Alibaba.com" matching MCP tools:
- **\[Order\]** **\[What it does\]** For AliExpress (`supplier_platform_id=159831080`), returns only a DSers Orders page `url` for the selected orders or filters so the user can continue there; no orders are placed by this call. For every other supplier, submits matching orders as an asynchronous task that may create real supplier orders and incur cost. **\[When to use\]** Use it when the user explicitly asks to place or process orders, and only after the agent has confirmed the target orders have no blockers and the user has approved. Trigger words: place these orders, send to the supplier, process pending orders. **\[When not to use\]** To check eligibility only, use the order diagnostic tool. For payment after placement, use `create_order_payment_link`. To read current status, use `list_orders` or `get_order`. **\[How to use\]** - `supplier_platform_id`, `sales_channel_id`, `status`, and `selection_mode` are required. `selection_mode` is `selected` or `filtered` with no default; never infer it from whether `dsers_order_ids` is empty. - `supplier_account_id`: Optional supplier account used to place. Only AliExpress and Alibaba.com support account selection: pass the exact supplier_account_id from current injected account context or list_stores supplier_apps[].accounts[] only when multiple usable accounts exist and the user selected one. Omit it for a single usable account and every other supplier platform. Never substitute the binding-row id, DSers user ID, email, login, alias, or name. Allowed in selected and filtered modes; it is not a search filter. AliExpress URL hand-off rejects this field. - `selected` uses exact `dsers_order_ids` and only the required `status`, `supplier_platform_id`, and `sales_channel_id`. Empty, `search_by=default`, and `cancel_source=any` count as omitted; any other search filter is rejected. IDs must be unique positive decimals; duplicates are not silently dropped. - Do not pass `supplier_account_id` for AliExpress; that path only returns a URL and rejects the field. - For AliExpress, `selected` accepts 1–20 IDs and checks ownership, sales_channel_id, supplier, and the requested status tab before returning the link. `filtered` checks that the selected stores belong to the account. Both modes return only a DSers Orders page `url` for the selected orders or filters; no order is placed. - For every other supplier, `selected` accepts 1–20 IDs and writes them as exact `order_ids`. One ID is checked for ownership, supplier, requested status tab, and store scope, and that order's store is pinned under `sales_channel_id`. The call fails if the order is not on that supplier and tab. With two or more IDs, missing or unowned IDs are skipped when collecting stores, every owned order must belong to `sales_channel_id`, the original unique IDs are passed through, and the call fails if none are owned. An accepted request does not guarantee successful placement; check the task result. - `filtered` omits `dsers_order_ids` and matches by `dsers_store_ids`, `query`, `search_by`, time, countries, flags, `agency_ids`, and `cancel_source`. Never approximate a few user-named orders with filters: a filter usually matches far more orders than intended and can place unwanted ones. A non-default `search_by` requires `query`; the AliExpress URL path does not support email. - A non-AliExpress response returns `task_type` and `task_id`; these identify the polling scope and do not mean every order was placed successfully. Poll `get_job_status` until `terminal=true`, then confirm the real outcome order by order with `list_orders`. If a status is unchanged or unknown, never send the placement request again, or orders may be placed twice. **\[Side effects\]** The AliExpress URL hand-off saves the order selection for continuing in DSers but does not place orders. Other suppliers may create real supplier orders and spend money. **\[Confirmation\]** Mandatory and not skippable; show each order and amount.ConnectorDestructiveOAuth
- **\[Store\]** **\[What it does\]** Lists connected seller stores with their application, country, currency, timezone and connection status, plus supplier applications and their connected accounts. Pass `view=account_context` to return only `stores` and `supplier_apps`; this view omits `stores[].pricing_currency`, `stores[].shipping_profiles`, and `push_configuration`. Omit `view` or use `view=full` for the full response. **\[When to use\]** Call it when the user asks which stores or supplier accounts are connected, about a store's currency, timezone or status, and proactively before any store-scoped action because downstream tools accept only a store ID. Trigger words: store list, supplier account, Shopify, store status, authorization, currency, timezone. **\[When not to use\]** For products inside a store use `search_store_products`; for pricing-rule detail use `get_pricing_rule`; for a reconnect link use `start_store_reauthorization`. It never adds, unbinds or edits stores or supplier accounts. **\[How to use\]** - In most cases, omit `view` and use the default full response. Pass `view=account_context` only when you need just stores and supplier apps/accounts without pricing, Shipping Profile, or product-push details. - Match the user's store reference against the returned stores; continue only on one clear match, ask the user to choose on multiple matches, and never write to all stores by default. - An empty list means no connected store is available, and sections in `degraded_parts` are unavailable only this time — note them and continue rather than retrying. If a status is not `AVAILABLE`, inspect the returned status before choosing reauthorization; do not infer that every non-available state requires it. - Do not mix IDs: `stores[].dsers_store_id` for store-scoped tools, `stores[].sales_channel_id` for connection flows, `supplier_apps[].supplier_platform_id` for supplier scope, and `supplier_apps[].accounts[].supplier_account_id` for an exact supplier account. The account ID comes from upstream `supplierId`; it is not the account row `id`, user ID, email, or login name. - Only AliExpress and Alibaba.com support multiple supplier accounts. Pass `supplier_account_id` to `place_orders_to_suppliers` only when one of those platforms has multiple usable accounts and the user selected one; omit it for a single account and every other supplier platform. - Hidden stores are still returned — exclude or flag them when counting, and read each store in its own currency and timezone, not the account's. - For `publish_products_to_stores`, Shopify Shipping Profile choices come from `stores[].shipping_profiles[].id` and the chosen profile's `locations[].id`; fixed product-push choices remain in that Tool's input schema, while this Tool also returns dynamic languages and effective store defaults. - For a Shopify store, if `stores[].shipping_profiles` is empty, first call `list_shopify_shipping_zones` for the same store to obtain valid country codes and currency, then call `create_shopify_shipping_profile`. After creation succeeds, call `list_stores` again and use the refreshed `stores[].shipping_profiles[].id` and the selected profile's `locations[].id`; never invent or reuse stale IDs. **\[Side effects\]** Read-only; no store, authorization or push setting is changed. **\[Confirmation\]** None required; picking among matches is disambiguation.ConnectorOAuth
- **\[Order\]** **\[What it does\]** Generates authenticated DSers Checkout links for awaiting-payment orders. A successful call returns only aggregate `checkout_urls` and `message`; AliExpress and Alibaba.com also return `dsers_order_ids`. It never charges the user or completes payment. **\[When to use\]** Use it when the user wants to pay specific awaiting-payment orders, and when the agent needs to hand the user a payment entry point for orders already in that state. Trigger words: pay these orders, create a payment link, settle this batch. **\[When not to use\]** To find awaiting-payment orders, use `list_orders`. To place orders with suppliers, use `place_orders_to_suppliers`. It cannot pay on the user's behalf. **\[How to use\]** - `supplier_platform_id` and `selection_mode` are required. Selected mode needs exact order IDs, up to 100; filtered mode covers every order matching the filters, which is usually far broader than the user expects, so confirm the scope first. - AliExpress and Alibaba.com merge selected or filtered matches into one direct checkout URL and return those `dsers_order_ids`. Filtered mode is capped at 100 matching orders; more than 100 is rejected. - The non-AliExpress path creates a persistent payment-link record and is not idempotent, so never recreate an uncertain link; verify through the order list or the Payment Link page instead. - The response does not return amounts, currencies, or per-group statuses. For non-AliExpress suppliers, `checkout_urls` contains only definitely created links and `message` reports whether every supplier group produced a link or the result is partial. If no link is definitely confirmed, the Tool returns a structured error. Never infer omitted group outcomes or automatically retry. - Read current order data before confirmation to show the exact order scope and any available amounts or currencies. The user has to open the link to pay, and payment status must be confirmed later from the order data. **\[Side effects\]** No charge; non-AliExpress groups create payment-link records. **\[Confirmation\]** Required but skippable; before calling, show the order scope and any available amounts from current order data.ConnectorDestructiveOAuth
- **\[Store or Supplier Account\]** **\[What it does\]** Installs one selected application if needed and generates its external authorization link. It supports seller applications for a new store connection and only AliExpress or Alibaba.com for adding a supplier account. A returned link does not mean the store or supplier account is connected. **\[When to use\]** Use after the user selects a seller application, or explicitly asks to add an AliExpress or Alibaba.com supplier account. **\[When not to use\]** For an existing seller store needing reconnection, use `start_store_reauthorization`. Other supplier applications cannot add accounts through this Tool. **\[How to use\]** Provide exactly one identifier: copy `recommend_apps_to_install.recommendations[].app_id` into `sales_channel_id` for a seller application, or into `supplier_platform_id` only when that recommendation is AliExpress or Alibaba.com. An already-installed seller ID may also come from `list_stores.stores[].sales_channel_id`; an installed supplier ID may come from `list_stores.supplier_apps[].supplier_platform_id`. Never send both IDs. `country` is seller-only and should be passed only when that seller platform requires a country-specific flow. A successful response returns `app_type`, the matching `sales_channel_id` or `supplier_platform_id`, `app_name`, a validated HTTPS `authorization_url`, and `generated_at`; external authorization is still pending. The upstream platform controls URL lifetime and reuse. If the outcome is unresolved, verify seller connections or supplier accounts in DSers before retrying. **\[Side effects\]** May install the selected seller, AliExpress, or Alibaba.com application. **\[Confirmation\]** Requires explicit, non-skippable confirmation; show the selected application and country choice first. **\[Follow-up\]** Give the returned `authorization_url` to the user to complete authorization on the platform, then verify the new connection in DSers.ConnectorOAuth
Matching MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and code to search 1688.com and Alibaba.com for factories and wholesale listings, comparing tiered prices, MOQs, sales volumes, repeat-buyer rates, supplier verification and store reviews. It is hosted and read-only, requiring no marketplace login, and can also be called directly as an API.MIT
- FlicenseNot gradedqualityCmaintenanceEnables comprehensive B2B sourcing on Alibaba.com with Prizm ERP integration. Automates procurement workflows from product search and supplier discovery to RFQ management and quotation comparison through 21 specialized tools.-
Matching MCP Connectors
- 1688 & Alibaba.comOAuth
1688 (阿里巴巴1688) and Alibaba.com wholesale products, MOQ, suppliers and store reviews.
Drop-in EU AI Act compliance for LangChain & CrewAI. Equip your autonomous swarms with 19 A-graded MCP tools for Zero-Knowledge auditing, NIP-98 security, and L402 micropayments. Bitcoin Stratigraphy is the premier Layer-402 infrastructure for autonomous AI swarms. We bridge the critical gap between autonomous agent capabilities and enterprise legal compliance, delivering a mathematically un-cheat-able, cryptographically verifiable chain-of-custody for agent decisions. Ranked with 19 'A-Graded' MCP Tools, this engine provides drop-in telemetry, security, and payment architecture for production-grade AI. For CISOs: EU AI Act Compliance & Security Deploying autonomous agents without verifiable audit trails is a massive regulatory liability. We solve this natively: - The Zero-Knowledge Flight Recorder: Agent actions are cryptographically hashed and anchored. Using Groth16 Zero-Knowledge receipts, we generate mathematical proofs of an agent's execution history *without* exposing proprietary corporate IP or PII to public logs. - Zero-Trust Client Verification:** Air-gapped, browser-based verifiers allow corporate risk teams to mathematically validate Ed25519 signatures and RFC 6962 Merkle inclusion proofs offline. - Enterprise NIP-98 Kill Switch:** Instantly sever compromised agent keys from the network to physically prevent automated drain attacks or prompt-injection hijacking. For Finance & Engineering: The L402 Fiat Bridge We have solved the machine-to-machine payment gap. Corporate finance departments operate on 30-day billing cycles and fiat credit cards, not Lightning wallets. - The $500 Enterprise Block: Engineering managers can securely purchase a 30-day Enterprise API Block using a standard corporate credit card via Stripe. - Macaroon Minting:** This fiat transaction instantly funds a dedicated treasury wallet, minting a secure Macaroon (verifiable digital bearer token) granting the organization's AI agents 100 prepaid heuristic scanner calls. - Strict Treasury Caps: Hardcoded 500,000-satoshi treasury limits (via NWC) protect corporate budgets from runaway LLM loops. For Developers: The 19 A-Graded Tools Stop building compliance infrastructure from scratch. Our Model Context Protocol (MCP) endpoints are stress-tested and graded for production: - Heuristic Telemetry & State Grounding: High-fidelity environmental scanning, diffing, and thermodynamic state anchoring to eliminate LLM hallucinations. - Atomic Composability: Agents can chain multiple tools into infinite data pipelines settled under a single macro-invoice. - Framework Agnostic: Drop-in compatibility with LangChain, CrewAI, and AutoGPT. Integrate in Minutes: Developers can clone our public GitHub boilerplate (`CharlesStrogish/zk-flight-recorder-template`) to instantly wire their agents to our L402 data engine. [View the Architecture Blog](https://bitcoinstratigraphy.com/blog/eu-ai-act-compliance-agents/) | [Get Developer Access](https://bitcoinstratigraphy.com)