Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Channable 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 marketplace orders and returns; send shipment, cancellation and stock updates.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http channable-mcp-by-usefulapi https://channable.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# channable_list_orders, channable_get_order, channable_ship_order and 10 more
Channable 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 channable-mcp-by-usefulapi https://channable.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.
13 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 the marketplace orders of a project, newest first. Filters combine with AND; dates are read as UTC. Paged: pass next_offset as offset (total is the size of the page, not of all orders). Reply: orders, error_count (orders with an error), count, next_offset. GET /v2/companies/{company}/projects/{project}/orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
| status | array | no | Only orders in one of these statuses: shipped, not_shipped, waiting, cancelled, processing, pending_shipment, pending_cancellation, cancellation_request, awaiting_confirmation, partial, manual. |
| search | string | no | Free-text search (order ids, names, products). |
| errors | boolean | no | true = only orders with an error. |
| start_date | string | no | Orders created on or after this date (yyyy-mm-dd or ISO 8601, UTC). |
| end_date | string | no | Orders created on or before this date. |
| last_modified_after | string | no | Orders modified after this date. |
| last_modified_before | string | no | Orders modified before this date. |
| retrieved_at_start | string | no | Orders retrieved from the marketplace on or after this date. |
| retrieved_at_end | string | no | Orders retrieved from the marketplace on or before this date. |
| limit | integer | no | Results per page, 1-100 (default 100). |
| offset | integer | no | Skip this many results (default 0). Use next_offset from the previous reply. |
One order with its customer, addresses, items, status, fulfillments and event log. order_id is the Channable order id (the id field from channable_list_orders). GET /v2/companies/{company}/projects/{project}/orders/{order_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Channable order id. |
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
Set an order to shipped, with tracking data. Give transporter as a Channable transporter code (channable_list_transporters lists them) and tracking_code. Pass order_item_ids to ship only some items (the order then becomes partial; repeat with the other items later); omit it to ship the whole order. Spartoo and Veepee do not support partial shipments. POST /v1/companies/{company}/projects/{project}
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Channable order id. |
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
| transporter | string | no | Channable transporter code, e.g. POSTNL, DHL, DPD. |
| tracking_code | string | no | Track and trace code of the parcel. |
| return_transporter | string | no | Transporter code for the return label, if the marketplace asks for it. |
| return_tracking_code | string | no | Track and trace code of the return label. |
| delivery_bill_id | string | no | Delivery bill id, if the marketplace asks for it. |
| order_item_ids | array | no | Only these order items are shipped (partial shipment). Omit to ship all. |
Seller-side cancellation: set an order to cancelled. Pass order_item_ids to cancel only some items (the order then becomes partial); omit it to cancel the whole order. Amazon, Cdiscount and Spartoo do not support partial cancellations. A buyer-side cancellation must be confirmed in the marketplace seller account instead. POST /v1/companies/{company}/projects/{project}/orders/{order_id}/cancel. Cha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Channable order id. |
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
| order_item_ids | array | no | Only these order items are cancelled (partial cancellation). Omit to cancel all. |
Tell Channable that you handle this order yourself: Channable takes no further action on it (no status updates to the marketplace). POST /v1/companies/{company}/projects/{project}/orders/{order_id}/manual. Channable passes this change on to the marketplace. It cannot be undone through this API and the call is never retried; if it times out, check the order in Channable before trying again.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Channable order id. |
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
Manually create a return on the marketplace for products of an order. Only Fruugo, Otto, Veepee and Zalando support this. products lists the product ids (the item id of the order), the quantity and optionally accepted or rejected. POST /v1/companies/{company}/projects/{project}/orders/{order_id}/return. Channable passes this change on to the marketplace. It cannot be undone through this API and th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Channable order id. |
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
| products | array | yes | The products to return. |
List the returns of a project, newest first. Dates are read as UTC. Paged: pass next_offset as offset. Reply: returns, error_count, count, next_offset. GET /v1/companies/{company}/projects/{project}/returns.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
| search | string | no | Free-text search. |
| errors | boolean | no | true = only returns with an error. |
| start_date | string | no | Returns created on or after this date (yyyy-mm-dd or ISO 8601, UTC). |
| end_date | string | no | Returns created on or before this date. |
| last_modified_after | string | no | Returns modified after this date. |
| last_modified_before | string | no | Returns modified before this date. |
| retrieved_at_start | string | no | Returns retrieved on or after this date. |
| retrieved_at_end | string | no | Returns retrieved on or before this date. |
| limit | integer | no | Results per page, 1-100 (default 100). |
| offset | integer | no | Skip this many results (default 0). Use next_offset from the previous reply. |
One return with its item, reason, customer, status and log. return_id is the id field from channable_list_returns. GET /v1/companies/{company}/projects/{project}/returns/{return_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| return_id | integer | yes | Channable return id. |
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
Set the status of a return: accepted, rejected, repaired, keeps, exchanged, cancelled. Depending on the status the customer does or does not get their money back (accepted and cancelled differ from rejected). POST /v1/companies/{company}/projects/{project}/returns/{return_id}/status. Channable passes this change on to the marketplace. It cannot be undone through this API and the call is never retr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| return_id | integer | yes | Channable return id. |
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
| status | string | yes | The new return status. |
List the offers (product stock updates) that were posted to a project, newest first: id, stock, price, title, GTIN. Paged: pass next_offset as offset. Reply: offers, count, next_offset. GET /v1/companies/{company}/projects/{project}/offers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
| search | string | no | Free-text search (offer id, title, GTIN). |
| start_date | string | no | Offers created on or after this date (UTC). |
| end_date | string | no | Offers created on or before this date. |
| last_modified_after | string | no | Offers modified after this date. |
| last_modified_before | string | no | Offers modified before this date. |
| limit | integer | no | Results per page, 1-100 (default 100). |
| offset | integer | no | Skip this many results (default 0). Use next_offset from the previous reply. |
Set the stock of up to 50 offers. Each item is the offer id as the marketplaces know it, plus the WHOLE new stock value (not a delta). Channable passes the new stock to every marketplace of the project, which changes what customers can buy. POST /v1/companies/{company}/projects/{project}/stock_updates. Channable passes this change on to the marketplace. It cannot be undone through this API and the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
| updates | array | yes | 1-50 stock updates. |
Order statistics of a project for a time frame: orders, ordered products, marketplace commission, shipping costs, revenue and daily revenue, per order connection and in total. Pass order_config_id (the order_config_id field of an order) for one order connection only. GET /v1/companies/{company}/projects/{project}/statistics/orders[/{order_config_id}].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Channable project id (Project settings). Default: the project chosen at login. |
| order_config_id | integer | no | Only this order connection (the order_config_id of an order). |
| start_date | string | no | First day (yyyy-mm-dd or ISO 8601, UTC). |
| end_date | string | no | Last day. |
Channable transporter codes for shipping updates. With no argument: all codes and labels (transporter_code is what channable_ship_order expects). With transporter_code: the marketplace-specific carriers behind that code. With channel (a marketplace such as bol, amazon, ebay): the carriers that marketplace supports. Give at most one of the two. GET /v1/transporters/all | /transporter/{code} | /chan
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transporter_code | string | no | A Channable transporter code, e.g. DHL. |
| channel | string | no | A marketplace name, lowercase, e.g. bol, amazon, ebay, otto. |
- 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 Channable 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 | 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 |
|---|---|---|
| channable_list_orders | no tags | |
| channable_get_order | no tags | |
| channable_ship_order | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| channable_cancel_order | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| channable_mark_order_manual | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| channable_create_return | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| channable_list_returns | no tags | |
| channable_get_return | no tags | |
| channable_update_return_status | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| channable_list_stock_updates | no tags | |
| channable_update_stock | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| channable_get_order_statistics | no tags | |
| channable_list_transporters | 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.8.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 Channable 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.