Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
Ordoro 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.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Ordoro orders, products, shipments, suppliers and purchase orders; tag and comment on orders.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ordoro-mcp-by-usefulapi https://ordoro.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# ordoro_list_orders, ordoro_get_order, ordoro_get_order_counts and 15 more
Ordoro 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.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 ordoro-mcp-by-usefulapi https://ordoro.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
18 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 orders across all sales channels, newest first by default. Filter by status (awaiting_fulfillment, shipped, cancelled, dropshipment_requested, all), free-text search, SKU, tag, warehouse, and created/updated/shipped date ranges. Returns { count, limit, offset, order: [...] } with lines, addresses, shipping_info (tracking), tags and financials. Ordoro API: GET /v3/order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Order status filter (default: Ordoro's default view). |
| search | string | no | Free-text search. |
| sku | array | no | Only orders containing these SKUs. |
| tag | array | no | Only orders with these tag names. |
| warehouse_id | array | no | Only orders assigned to these warehouse ids. |
| sales_channel | array | no | Only orders from these sales channel (cart) ids. |
| allocation_status | string | no | Inventory allocation status filter. |
| created_after | string | no | Created on/after this date (ISO 8601, e.g. 2026-10-01). |
| created_before | string | no | Created before this date (ISO 8601). |
| updated_after | string | no | Updated on/after this date (ISO 8601). |
| shipped_after | string | no | Shipped on/after this date (ISO 8601). |
| shipped_before | string | no | Shipped before this date (ISO 8601). |
| sort | string | no | Sort field; prefix '-' for descending. |
| limit | integer | no | Max results per page (default 10, max 100). |
| offset | integer | no | Number of results to skip (pagination). |
Get one order by order number: status, lines (SKU, quantity, price), shipping/billing address, warehouse, shipping_info (carrier, tracking number, ship date, cost), comments, tags, financials and dropship info. Ordoro API: GET /v3/order/{order_number}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
Count orders per status: all, awaiting_fulfillment, shipped, unprinted_shipped, cancelled, dropshipment_requested. A quick fulfillment-backlog overview. Ordoro API: GET /v3/order/counts.
No parameter schema on file.
Get the shipment and tracking details of one order: carrier, shipping method, tracking number and tracking URL, ship date, estimated delivery, label cost, plus any return shipment and dropship info. Ordoro API: GET /v3/order/{order_number} (shipping_info).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
List the comments (internal notes and the order's activity log) of one order, with user and date. Paginated: returns { count, limit, offset, comment: [...] }; use offset for the next page. Ordoro API: GET /v3/order/{order_number}/comment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
| limit | integer | no | Max results per page (default 10, max 100). |
| offset | integer | no | Number of results to skip (pagination). |
List the account's order tags (id, name, color). Use the id with ordoro_add_order_tag / ordoro_remove_order_tag. Ordoro API: GET /v3/order/tag.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max results per page (default 10, max 100). |
| offset | integer | no | Number of results to skip (pagination). |
List products with inventory totals (total_on_hand, available_on_hand, total_committed, total_allocated, to_be_shipped, po_total_committed). Filter by search, active, low inventory, oversold, needs_sync, warehouse, supplier, tag, kit status and updated date. Returns { count, limit, offset, products: [...] }. Ordoro API: GET /product/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Search by SKU or name. |
| active | boolean | no | true = active products only, false = archived only. |
| low_inventory_aoh | boolean | no | true = only products low on available-on-hand inventory. |
| oversold | boolean | no | true = only oversold products. |
| to_be_shipped | boolean | no | true = only products with committed (to-be-shipped) inventory. |
| needs_sync | boolean | no | true = only products whose inventory needs syncing to a sales channel. |
| kit | boolean | no | true = only kit parents. |
| dropship | boolean | no | true = only dropshippable products. |
| category | string | no | Product category. |
| warehouse_id | array | no | Only products stocked in these warehouse ids. |
| supplier | array | no | Only products from these supplier ids. |
| tag | array | no | Only products with these tag names. |
| updated_after | string | no | Updated after this date (ISO 8601). |
| sort | string | no | Sort field; prefix '-' for descending. |
| limit | integer | no | Max results per page (default 10, max 100). |
| offset | integer | no | Number of results to skip (pagination). |
Get one product by SKU: price, cost, weight and dimensions, inventory totals, stock per warehouse (on hand, available, committed, location), suppliers, kit components and sales-channel links. Ordoro API: GET /product/{sku}/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sku | string | yes | The product SKU. |
List warehouses (ship-from locations) with id, name, address and whether each is the default. Ordoro API: GET /warehouse/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Free-text search. |
| limit | integer | no | Max results per page (default 10, max 100). |
| offset | integer | no | Number of results to skip (pagination). |
List suppliers and dropshippers with id, company name, address, contact email and dropship settings. Ordoro API: GET /supplier/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Free-text search. |
| limit | integer | no | Max results per page (default 10, max 100). |
| offset | integer | no | Number of results to skip (pagination). |
Get one supplier by id, with address, contact details and dropship/PO settings. Ordoro API: GET /supplier/{supplier_id}/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier_id | integer | yes | The supplier id (from ordoro_list_suppliers). |
List the carrier accounts (shippers) connected to Ordoro: UPS, FedEx, USPS (Endicia/Pitney), DHL, Canada Post, Australia Post, Amazon, Sendle. Returns id, name, vendor, archive/created/updated dates and hidden shipping methods only (carrier credentials are never returned). Ordoro API: GET /shipper/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| all | boolean | no | true = include archived carrier accounts. |
| limit | integer | no | Max results per page (default 10, max 100). |
| offset | integer | no | Number of results to skip (pagination). |
List purchase orders to suppliers with status (unsent, sent, partial, received, cancelled), supplier, lines and expected delivery. Filter by status, SKU, tag, search and updated date. Ordoro API: GET /purchase_order/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Purchase order status filter. |
| search | string | no | Free-text search. |
| sku | array | no | Only POs containing these SKUs. |
| tag | array | no | Only POs with these tag names. |
| updated_after | string | no | Updated after this date (ISO 8601). |
| updated_before | string | no | Updated before this date (ISO 8601). |
| sort | string | no | Sort field; prefix '-' for descending. |
| limit | integer | no | Max results per page (default 10, max 100). |
| offset | integer | no | Number of results to skip (pagination). |
Get one purchase order by its PO id: supplier, warehouse, status, lines (SKU, quantity ordered/received, unit price), shipping/payment method and dates. Ordoro API: GET /purchase_order/{po_id}/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| po_id | string | yes | The purchase order id (po_id, from ordoro_list_purchase_orders). |
List return orders (RMAs) with reference id, status, original order, lines and return label info. Ordoro API: GET /v3/return_order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Free-text search. |
| status | string | no | Return order status filter (e.g. all). |
| sort | string | no | Sort: (-)reference_id, (-)status, (-)warehouse_name, (-)created_date, (-)updated_date. |
| limit | integer | no | Max results per page (default 10, max 100). |
| offset | integer | no | Number of results to skip (pagination). |
WRITE: add an internal comment to an order (visible to the team in Ordoro, not sent to the customer). Each call adds a new comment. Ordoro API: POST /v3/order/{order_number}/comment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
| comment | string | yes | The comment text. |
WRITE: apply an existing order tag (by id, from ordoro_list_order_tags) to an order, for example to put it on hold or route it. Returns the order's tags. Ordoro API: POST /v3/order/{order_number}/tag/{tag_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
| tag_id | integer | yes | The tag id (from ordoro_list_order_tags). |
WRITE: remove a tag (by id) from an order. The tag itself stays defined. Ordoro API: DELETE /v3/order/{order_number}/tag/{tag_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
| tag_id | integer | yes | The tag id (from ordoro_list_order_tags). |
Free
$0 forever
- 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 Ordoro MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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 1.2.1.
1.2.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Ordoro 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.
No reviews yet
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.