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
botx402 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.
4
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Inventory reorder plans from SKU sales, stock and lead times. $19 a run, paid by card.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http botx402-mcp https://api.botx402.io/mcp
# 2 — ask your agent for something these tools do
# list_bots, validate_inventory_reorder_inputs, start_inventory_reorder and 1 more
botx402 costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BOAll 1 server
botx4021 server
1 category
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 botx402-mcp https://api.botx402.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
4 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 bots this server can run: what each one does, its price per run, what a run returns, its input schema, and the names of its validate_ and start_ tools. Free and read-only.
No parameter schema on file.
Check inputs for Inventory Reorder Snapshot before asking a human to pay. Free; nothing is charged, stored or run. Takes exactly the JSON start_inventory_reorder takes: {"inputs": {...}}, plus "email" if you have it (checked too, optional here). Returns either valid (with a one-line summary of what will be analysed) or every problem found at once, each with its path (e.g. inputs.skus[2].unit_cost)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | The buyer's email: Stripe sends the payment receipt there and botx402 emails the results link. | |
| inputs | object | yes | — |
Start a paid Inventory Reorder Snapshot run ($19.00 per run). This tool never charges anyone; it returns a Stripe checkout link that a person opens and pays. It creates the checkout and returns the link with a receipt_id and access_token. Nothing runs until the person pays on Stripe's page. Show the user the link and the price and ask them to pay; then call get_run with the receipt_id and access_t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The buyer's email: Stripe sends the payment receipt there and botx402 emails the results link. | |
| inputs | object | yes | — |
Check a run started with a start_ tool and fetch its results. Needs the receipt_id AND the access_token that start_ returned: the token is the proof that the caller started the run, and without it nothing is returned. Status is awaiting_payment (the user has not paid yet), running, completed or failed. When completed, structuredContent.result is the bot's full JSON result, ready to act on, and pdf
| Parameter | Type | Required | Notes |
|---|---|---|---|
| access_token | string | yes | access_token from start_<bot>. |
| receipt_id | string | yes | receipt_id from start_<bot>, like RG-202610-1A2B3C4D. |
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 botx402 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. 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 0.1.0.
0.1.0
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 botx402 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.