Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
MyOnlineStore MCP by usefulapi 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 orders, articles, customers, discount codes and newsletter subscribers in MyOnlineStore.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http myonlinestore-mcp-by-usefulapi https://myonlinestore.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# myonlinestore_get_store, myonlinestore_list_shipping_methods, myonlinestore_list_articles and 17 more
MyOnlineStore MCP by usefulapi 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 myonlinestore-mcp-by-usefulapi https://myonlinestore.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.
20 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 shop's own details: name, primary domain, currency, default and active languages, prices-include-tax setting and business models. Good first call to check the connection. GET /v1/store.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Language for translated fields (default: the shop language). |
List the shipping methods the shop offers: display name, countries served, default flag and the free-shipping threshold. GET /v1/shipping/methods.
No parameter schema on file.
List the shop's articles (products) with name, SKU, price and stock. Filter by ids, uuids or created/changed dates. GET /v1/articles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Language for translated fields (default: the shop language). |
| limit | integer | no | Maximum number of results. |
| offset | integer | no | Number of results to skip (paging). |
| ids | string | no | Comma-separated article ids. |
| uuids | string | no | Comma-separated article uuids. |
| created_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| created_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
Get one article (product) by its id. Set use_url_id to true when the id is the one shown in the article page URL. GET /v1/articles/{article_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| article_id | string | yes | The article id (from myonlinestore_list_articles). |
| use_url_id | boolean | no | True when the id is the one from the article page URL (default false). |
| language | string | no | Language for translated fields (default: the shop language). |
Count the shop's articles, optionally within a created or changed date range. GET /v1/articles/count.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Language for translated fields (default: the shop language). |
| created_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| created_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
List the shop's categories with title, parent, visibility and sort order. Set as_tree to get the nested tree. GET /v1/categories.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Language for translated fields (default: the shop language). |
| limit | integer | no | Maximum number of results. |
| offset | integer | no | Number of results to skip (paging). |
| as_tree | boolean | no | Return the nested category tree (default false). |
| max_depth | integer | no | Tree depth limit when as_tree is true. |
| created_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| created_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
Get one category by id: title, content, SEO fields, parent and sorting. GET /v1/categories/{category_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | yes | The category id (from myonlinestore_list_categories). |
| language | string | no | Language for translated fields (default: the shop language). |
List the articles that belong to one category. GET /v1/categories/{category_id}/articles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | yes | The category id. |
| language | string | no | Language for translated fields (default: the shop language). |
| limit | integer | no | Maximum number of results. |
| offset | integer | no | Number of results to skip (paging). |
List the shop's customers. Search with q (name, email or similar). Set embed to address to include addresses. GET /v1/customers. Contains personal data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search text (name, email or similar). |
| embed | string | no | Include related data: address. |
Get one customer by id. Contains personal data. GET /v1/customers/{customerId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The customer id (from myonlinestore_list_customers). |
List the saved addresses of one customer. Contains personal data. GET /v1/customers/{customerId}/addresses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The customer id. |
List orders with status, date, currency, discount code and payment status. Filter by order date, status, status change, customer email or customer id. GET /v1/orders. Contains personal data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Language for translated fields (default: the shop language). |
| limit | integer | no | Maximum number of results. |
| offset | integer | no | Number of results to skip (paging). |
| start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| status_id | integer | no | Filter by order status id. |
| status_changed_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| status_changed_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| debtor_email | string | no | Filter by customer email. |
| debtor_id | string | no | Filter by customer id. |
| archived | boolean | no | Include or filter archived orders. |
Get one order by its order number: status, dates, currency, discount code, payment status and the price block. Contains personal data. GET /v1/orders/{order_number}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | The order number (from myonlinestore_list_orders). |
| language | string | no | Language for translated fields (default: the shop language). |
Count orders, optionally filtered by order date, status or status change. GET /v1/orders/count.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Language for translated fields (default: the shop language). |
| start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| status_id | integer | no | Filter by order status id. |
| status_changed_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| status_changed_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| archived | boolean | no | Include or filter archived orders. |
List the payments recorded on one order. GET /v1/orders/{order_number}/payments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | The order number. |
| embed | string | no | Comma-separated related data to include, as the API documents it. |
List the shop's discount codes: the code, percentage or fixed discount, validity dates and active flag. Filter by active state or validity. GET /v1/discountcodes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| active | boolean | no | Only active (true) or inactive (false) codes. |
| valid_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| valid_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
Get one discount code by its code text: discount values, validity dates, minimum order rules and single-use flag. GET /v1/discountcodes/{code}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The discount code text. |
List newsletter subscribers with their activation state and dates. Filter by activation or created/changed dates. GET /v1/newsletter/subscribers. Contains personal data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Language for translated fields (default: the shop language). |
| limit | integer | no | Maximum number of results. |
| offset | integer | no | Number of results to skip (paging). |
| activated | boolean | no | Only activated (true) or not activated (false) subscribers. |
| created_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| created_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
Get one newsletter subscriber by email address. Contains personal data. GET /v1/newsletter/subscribers/{email}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The subscriber's email address. | |
| language | string | no | Language for translated fields (default: the shop language). |
Count newsletter subscribers, optionally filtered by activation or created/changed dates. GET /v1/newsletter/subscribers/count.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Language for translated fields (default: the shop language). |
| activated | boolean | no | Only activated (true) or not activated (false) subscribers. |
| created_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| created_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_start_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
| changed_end_date | string | no | Date filter as the API expects it (for example 2026-01-31). |
- 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 MyOnlineStore MCP by usefulapi 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 | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| 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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| myonlinestore_get_store | no tags | |
| myonlinestore_list_shipping_methods | no tags | |
| myonlinestore_list_articles | no tags | |
| myonlinestore_get_article | no tags | |
| myonlinestore_count_articles | no tags | |
| myonlinestore_list_categories | no tags | |
| myonlinestore_get_category | no tags | |
| myonlinestore_list_category_articles | no tags | |
| myonlinestore_list_customers | no tags | |
| myonlinestore_get_customer | no tags | |
| myonlinestore_list_customer_addresses | no tags | |
| myonlinestore_list_orders | no tags | |
| myonlinestore_get_order | no tags | |
| myonlinestore_count_orders | no tags | |
| myonlinestore_list_order_payments | no tags | |
| myonlinestore_list_discount_codes | no tags | |
| myonlinestore_get_discount_code | no tags | |
| myonlinestore_list_newsletter_subscribers | no tags | |
| myonlinestore_get_newsletter_subscriber | no tags | |
| myonlinestore_count_newsletter_subscribers | no tags |
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.1.2.
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 MyOnlineStore MCP by usefulapi 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.