Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Ecwid 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
Read store products, orders, customers, categories and coupons; adjust inventory and update orders.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ecwid-mcp https://ecwid.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# ecwid_get_store_profile, ecwid_search_products, ecwid_get_product and 9 more
Ecwid 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 ecwid-mcp https://ecwid.usefulapi.io/mcpReconnect, 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.
12 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.
Get the store's profile — general info (store id, name, currency), company details, and settings. Ecwid REST: GET /profile.
No parameter schema on file.
Search / list the store's products with optional filters (keyword, SKU, category, stock, price range) and sorting. Returns a paged collection ({total, count, offset, limit, items}). Ecwid REST: GET /products.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | no | Full-text search term (matches title, description, SKU…). |
| sku | string | no | Filter by exact product SKU. |
| category | integer | no | Filter to products in this category id (0 = root). |
| inStock | boolean | no | Filter to in-stock (true) or out-of-stock (false) products. |
| enabled | boolean | no | Filter to enabled (true) or disabled (false) products. |
| priceFrom | number | no | Minimum price (inclusive). |
| priceTo | number | no | Maximum price (inclusive). |
| sortBy | string | no | Sort order: RELEVANCE | PRICE_ASC | PRICE_DESC | NAME_ASC | NAME_DESC | ADDED_TIME_ASC | ADDED_TIME_DESC | UPDATED_TIME_ASC | UPDATED_TIME_DESC. |
| offset | integer | no | Pagination offset. |
| limit | integer | no | Max results per page (1-100). |
Get a single product by its id, including price, stock, options, images, and category assignments. Ecwid REST: GET /products/{productId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | integer | yes | Product id. |
Search / list the store's orders with optional filters (keyword, customer email/id, payment & fulfillment status, coupon, created-date range). Returns a paged collection. Ecwid REST: GET /orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | no | Full-text search term (order number, customer name, email…). |
| string | no | Filter by customer email. | |
| customer_id | integer | no | Filter by customer id. |
| payment_status | string | no | Filter by payment status: AWAITING_PAYMENT | PAID | CANCELLED | REFUNDED | PARTIALLY_REFUNDED | INCOMPLETE. |
| fulfillment_status | string | no | Filter by fulfillment status: AWAITING_PROCESSING | PROCESSING | SHIPPED | DELIVERED | WILL_NOT_DELIVER | RETURNED | READY_FOR_PICKUP | OUT_FOR_DELIVERY. |
| coupon_code | string | no | Filter by applied coupon code. |
| created_from | string | no | Filter to orders created on/after this date (YYYY-MM-DD or Unix timestamp). |
| created_to | string | no | Filter to orders created on/before this date (YYYY-MM-DD or Unix timestamp). |
| offset | integer | no | Pagination offset. |
| limit | integer | no | Max results per page (1-100). |
Get a single order by its order number, including line items, totals, customer, and payment/fulfillment status. Ecwid REST: GET /orders/{orderNumber}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | yes | Order number (the store-visible order id). |
Search / list the store's customers with optional filters (keyword, email, name, customer group). Returns a paged collection. Ecwid REST: GET /customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | no | Full-text search term (name, email…). |
| string | no | Filter by customer email. | |
| name | string | no | Filter by customer name. |
| customer_group_id | integer | no | Filter by customer group id. |
| offset | integer | no | Pagination offset. |
| limit | integer | no | Max results per page (1-100). |
Get a single customer by id, including contact details, addresses, and customer group. Ecwid REST: GET /customers/{customerId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | Customer id. |
List the store's product categories, optionally scoped to a parent category and including hidden ones. Returns a paged collection. Ecwid REST: GET /categories.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parent | integer | no | List only subcategories of this parent category id (0 = root). |
| hidden_categories | boolean | no | Include hidden (disabled) categories when true. |
| offset | integer | no | Pagination offset. |
| limit | integer | no | Max results per page (1-100). |
Get a single category by id, including its name, parent, product ids, and images. Ecwid REST: GET /categories/{categoryId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | integer | yes | Category id. |
List the store's discount coupons with optional filters (coupon code, discount type, availability). Returns a paged collection. Ecwid REST: GET /discount_coupons.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coupon_code | string | no | Filter by exact coupon code. |
| discount_type | string | no | Filter by discount type, e.g. ABS | PERCENT | SHIPPING | ABS_AND_SHIPPING | PERCENT_AND_SHIPPING. |
| availability | string | no | Filter by availability, e.g. ACTIVE | PAUSED | EXPIRED | COMPLETE. |
| offset | integer | no | Pagination offset. |
| limit | integer | no | Max results per page (1-100). |
ADJUSTS a product's in-stock quantity by a delta — this MODIFIES live store data. Positive increases stock, negative decreases it. Ecwid REST: PUT /products/{productId}/inventory with JSON body {quantityDelta}. Returns {updateCount, warning?}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | integer | yes | Product id to adjust. |
| quantity_delta | integer | yes | Change in stock quantity — positive increases stock, negative decreases. |
UPDATES an order — its payment status, fulfillment status, and/or tracking number. This MODIFIES live store data and may trigger customer notifications. Ecwid REST: PUT /orders/{orderNumber}. Provide only the fields you want to change. Returns {updateCount}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | yes | Order number to update. | |
| payment_status | string | no | New payment status: AWAITING_PAYMENT | PAID | CANCELLED | REFUNDED | PARTIALLY_REFUNDED | INCOMPLETE. |
| fulfillment_status | string | no | New fulfillment status: AWAITING_PROCESSING | PROCESSING | SHIPPED | DELIVERED | WILL_NOT_DELIVER | RETURNED | READY_FOR_PICKUP | OUT_FOR_DELIVERY. |
| tracking_number | string | no | Shipping tracking number to record on the order. |
- 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 Ecwid 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ecwid_get_store_profile | no tags | |
| ecwid_search_products | no tags | |
| ecwid_get_product | no tags | |
| ecwid_search_orders | no tags | |
| ecwid_get_order | no tags | |
| ecwid_search_customers | no tags | |
| ecwid_get_customer | no tags | |
| ecwid_list_categories | no tags | |
| ecwid_get_category | no tags | |
| ecwid_list_discount_coupons | no tags | |
| ecwid_adjust_product_inventory | state-write | state-write: declares destructiveHint: true |
| ecwid_update_order | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 1.11.1.
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 Ecwid 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.