Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Moltline Dropship Economics 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
Margin, lead time, SKU mapping and price-ladder maths for dropshipping. 4 of 6 free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http moltline-dropship-economics-mcp https://mcp.moltlinestudio.com/dropship
# 2 — ask your agent for something these tools do
# margin_check, lead_time, sku_map_check and 3 more
Moltline Dropship Economics 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 moltline-dropship-economics-mcp https://mcp.moltlinestudio.com/dropshipReconnect, 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.
6 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.
Show what one sale actually leaves after every cost. FREE. Subtracts supplier cost, shipping, payment fees, the ad spend that found the buyer, and anything else — then reports the break-even price so you know how much room there is. Typical input {"sell_price": 39.99, "supplier_cost": 12.4, "shipping_cost": 4.2, "ad_cost_per_order": 9} returns {"revenue": 39.99, "total_cost": 27.06, "profit": 12.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sell_price | number | yes | What the customer pays, excluding tax. Must be above 0. |
| supplier_cost | number | yes | What the supplier charges you per unit. |
| shipping_cost | number | no | Shipping you absorb per order. Default 0. |
| payment_fee_pct | number | no | Processor percentage fee. Default 2.9 — a common published rate, not a statement about your account. |
| payment_fee_fixed | number | no | Processor fixed fee per transaction. Default 0.30. |
| ad_cost_per_order | number | no | Blended acquisition cost per order. Default 0, but leaving it at 0 is the most common way this maths lies. |
| other_cost | number | no | Anything else per order: packaging inserts, app fees, support time. Default 0. |
Turn supplier and transit times into a date you can promise. FREE. Adds a buffer, because the number a supplier quotes is their best case and the date you publish is a commitment. Typical input {"supplier_days": 3, "transit_days": 12, "order_date": "2026-08-20"} returns {"total_days": 17, "delivery_date": "2026-09-06", "promise_date": "2026-09-09", "advice": "..."}. Use when writing a shipping p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier_days | integer | yes | Days from your order to the supplier despatching it. |
| transit_days | integer | yes | Days in transit from despatch to the customer. |
| buffer_days | integer | no | Extra days added before the date you publish. Default 2. |
| order_date | string | no | Start date as YYYY-MM-DD, e.g. "2026-08-20". Defaults to today when omitted. |
| working_days_only | boolean | no | When true, count supplier and transit days as Monday-Friday only. Default false. |
Find the breaks in a supplier-to-store SKU map before they ship. FREE. Two store SKUs pointing at one supplier SKU is usually intentional; two supplier SKUs claiming one store SKU is not, and it sends the wrong item. Typical input {"mapping": {"STORE-1": "SUP-A", "STORE-2": "SUP-A", "STORE-3": ""}} returns {"ok": false, "count": 3, "empty_targets": ["STORE-3"], "shared_supplier_skus": {"SUP-A": [
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mapping | object | yes | Store SKU to supplier SKU, e.g. {"STORE-1": "SUP-A"}. At least one entry. |
Work backwards from the margin you want to the price you must charge. FREE. Solves for price including the percentage fee, which is why it is not simply cost divided by one minus margin. Typical input {"supplier_cost": 12.4, "target_margins_pct": [30, 40, 50], "shipping_cost": 4.2} returns {"rows": [{"target_margin_pct": 30, "price": 25.99, "total_cost": 17.65, "profit": 8.34, "actual_margin_pct"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier_cost | number | yes | Per-unit cost from the supplier. Must be above 0. |
| target_margins_pct | array | yes | Margins to solve for, e.g. [30, 40, 50]. Each must be above 0 and below 100. |
| payment_fee_pct | number | no | Processor percentage fee. Default 2.9. |
| payment_fee_fixed | number | no | Processor fixed fee. Default 0.30. |
| shipping_cost | number | no | Shipping you absorb per order. Default 0. |
| charm_ending | string | no | Force prices to end in these cents, e.g. ".99". Pass an empty string for exact prices. Default ".99". |
Decide how much to order against demand, lead time and the cash you have. PREMIUM (license). A minimum order quantity is a cash-flow decision disguised as a purchasing one. Typical input {"unit_cost": 4.2, "moq": 500, "monthly_demand": 120, "cash_available": 3000, "lead_time_days": 45} returns {"moq_cost": 2100.0, "months_of_cover": 4.17, "affordable": true, "cash_after": 900.0, "reorder_point_un
| Parameter | Type | Required | Notes |
|---|---|---|---|
| unit_cost | number | yes | Cost per unit at the MOQ. Must be above 0. |
| moq | integer | yes | The supplier's minimum order quantity, in units. |
| monthly_demand | number | yes | Units you expect to sell per month. Must be above 0. |
| cash_available | number | yes | Cash you can commit to stock right now. |
| lead_time_days | integer | no | Days from placing the order to stock being sellable. Default 30. |
| safety_weeks | number | no | Weeks of demand held as buffer against a late delivery. Default 2. |
Show what a return rate does to a margin that looked fine. PREMIUM (license). A 10% return rate does not cost 10% of profit. A returned order gives back the refund, adds inbound shipping, and recovers only the goods — never the advertising that found the buyer. Typical input {"sell_price": 39.99, "unit_profit": 13.23, "unit_cost": 12.4, "return_rate_pct": 8, "restock_pct": 70, "return_shipping":
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sell_price | number | yes | Price the customer paid. |
| unit_profit | number | yes | Profit on one kept sale, from margin_check. May be negative, which the result will make obvious. |
| unit_cost | number | yes | What the goods themselves cost you — the only part a restocked unit gives back. Advertising and fees do not return. |
| return_rate_pct | number | yes | Percentage of orders returned, e.g. 8. |
| restock_pct | number | no | Percentage of returned units resellable at full price. Default 0, the conservative case. |
| return_shipping | number | no | What an inbound return costs you. Default 0. |
| refund_pct | number | no | Percentage of the sale price refunded, e.g. 100 for a full refund or 80 when a restocking fee is kept. Default 100. |
- 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 Moltline Dropship Economics 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.
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 1.2.0.
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 Moltline Dropship Economics 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.