Moltline Dropship Economics

Margin, lead time, SKU mapping and price-ladder maths for dropshipping. 4 of 6 free.

使うべきか

品質と安全性

A
説明の品質
100%
スキーマの完全性
100%
命名の品質
80%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~3,039トークン数(ツール定義)
~2.6 KB一般的なレスポンスサイズ
注意への影響は大きい(128k コンテキストの 2.37%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "dropship": {
      "url": "https://mcp.moltlinestudio.com/dropship"
    }
  }
}

リモートエンドポイント

https://mcp.moltlinestudio.com/dropshipstreamable-http

できること

ツール一覧

ツール(6)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢margin_check(sell_price, supplier_cost, shipping_cost, payment_fee_pct, payment_fee_fixed, ...)

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.93, "margin_pct": 32.33, "markup_pct": 222.5, "break_even_price": 27.06, "biggest_cost": "supplier_cost"}. Use before listing a product. Not for a whole tiered price list — that is price_ladder — and not for the effect of returns, which is returns_impact. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

入力スキーマ

{
  "type": "object",
  "properties": {
    "sell_price": {
      "exclusiveMinimum": 0,
      "type": "number",
      "description": "What the customer pays, excluding tax. Must be above 0."
    },
    "supplier_cost": {
      "exclusiveMinimum": 0,
      "type": "number",
      "description": "What the supplier charges you per unit."
    },
    "shipping_cost": {
      "default": 0,
      "minimum": 0,
      "type": "number",
      "description": "Shipping you absorb per order. Default 0."
    },
    "payment_fee_pct": {
      "default": 2.9,
      "minimum": 0,
      "type": "number",
      "description": "Processor percentage fee. Default 2.9 — a common\npublished rate, not a statement about your account."
    },
    "payment_fee_fixed": {
      "default": 0.3,
      "minimum": 0,
      "type": "number",
      "description": "Processor fixed fee per transaction. Default 0.30."
    },
    "ad_cost_per_order": {
      "default": 0,
      "minimum": 0,
      "type": "number",
      "description": "Blended acquisition cost per order. Default 0,\nbut leaving it at 0 is the most common way this maths lies."
    },
    "other_cost": {
      "default": 0,
      "minimum": 0,
      "type": "number",
      "description": "Anything else per order: packaging inserts, app fees,\nsupport time. Default 0."
    }
  },
  "required": [
    "sell_price",
    "supplier_cost"
  ],
  "additionalProperties": false
}

出力スキーマ

{
  "type": "object",
  "additionalProperties": true
}
🟢lead_time(supplier_days, transit_days, buffer_days, order_date, working_days_only)

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 policy or answering "when will it arrive". Not for what the shipping costs — that is the shipping server. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "order_date must be YYYY-MM-DD, e.g. 2026-08-20"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

入力スキーマ

{
  "type": "object",
  "properties": {
    "supplier_days": {
      "minimum": 0,
      "type": "integer",
      "description": "Days from your order to the supplier despatching it."
    },
    "transit_days": {
      "minimum": 0,
      "type": "integer",
      "description": "Days in transit from despatch to the customer."
    },
    "buffer_days": {
      "default": 2,
      "minimum": 0,
      "type": "integer",
      "description": "Extra days added before the date you publish. Default 2."
    },
    "order_date": {
      "default": "",
      "type": "string",
      "description": "Start date as YYYY-MM-DD, e.g. \"2026-08-20\". Defaults to\ntoday when omitted."
    },
    "working_days_only": {
      "default": false,
      "type": "boolean",
      "description": "When true, count supplier and transit days as\nMonday-Friday only. Default false."
    }
  },
  "required": [
    "supplier_days",
    "transit_days"
  ],
  "additionalProperties": false
}

出力スキーマ

{
  "type": "object",
  "additionalProperties": true
}
🟢sku_map_check(mapping)

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": ["STORE-1", "STORE-2"]}, "whitespace_issues": []}. Use before importing a mapping or handing one to a fulfilment app. Not for validating Shopify's CSV columns — that is the shopify server. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "mapping must contain at least one store SKU"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

入力スキーマ

{
  "type": "object",
  "properties": {
    "mapping": {
      "additionalProperties": {
        "type": "string"
      },
      "type": "object",
      "description": "Store SKU to supplier SKU, e.g. {\"STORE-1\": \"SUP-A\"}. At\nleast one entry."
    }
  },
  "required": [
    "mapping"
  ],
  "additionalProperties": false
}

出力スキーマ

{
  "type": "object",
  "additionalProperties": true
}
🟢price_ladder(supplier_cost, target_margins_pct, payment_fee_pct, payment_fee_fixed, shipping_cost, ...)

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": 32.07}, ...]}. Use when setting a price list. Not for checking one price you already have — that is margin_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "target_margins_pct must contain at least one margin"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

入力スキーマ

{
  "type": "object",
  "properties": {
    "supplier_cost": {
      "exclusiveMinimum": 0,
      "type": "number",
      "description": "Per-unit cost from the supplier. Must be above 0."
    },
    "target_margins_pct": {
      "items": {
        "type": "number"
      },
      "type": "array",
      "description": "Margins to solve for, e.g. [30, 40, 50]. Each\nmust be above 0 and below 100."
    },
    "payment_fee_pct": {
      "default": 2.9,
      "minimum": 0,
      "type": "number",
      "description": "Processor percentage fee. Default 2.9."
    },
    "payment_fee_fixed": {
      "default": 0.3,
      "minimum": 0,
      "type": "number",
      "description": "Processor fixed fee. Default 0.30."
    },
    "shipping_cost": {
      "default": 0,
      "minimum": 0,
      "type": "number",
      "description": "Shipping you absorb per order. Default 0."
    },
    "charm_ending": {
      "default": ".99",
      "type": "string",
      "description": "Force prices to end in these cents, e.g. \".99\". Pass an\nempty string for exact prices. Default \".99\"."
    }
  },
  "required": [
    "supplier_cost",
    "target_margins_pct"
  ],
  "additionalProperties": false
}

出力スキーマ

{
  "type": "object",
  "additionalProperties": true
}
🟢moq_planner(unit_cost, moq, monthly_demand, cash_available, lead_time_days, ...)

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_units": 236, "verdict": "..."}. Use before committing to a supplier's minimum. Not for the margin each unit earns — that is margin_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

入力スキーマ

{
  "type": "object",
  "properties": {
    "unit_cost": {
      "exclusiveMinimum": 0,
      "type": "number",
      "description": "Cost per unit at the MOQ. Must be above 0."
    },
    "moq": {
      "minimum": 1,
      "type": "integer",
      "description": "The supplier's minimum order quantity, in units."
    },
    "monthly_demand": {
      "exclusiveMinimum": 0,
      "type": "number",
      "description": "Units you expect to sell per month. Must be above 0."
    },
    "cash_available": {
      "exclusiveMinimum": 0,
      "type": "number",
      "description": "Cash you can commit to stock right now."
    },
    "lead_time_days": {
      "default": 30,
      "minimum": 0,
      "type": "integer",
      "description": "Days from placing the order to stock being sellable.\nDefault 30."
    },
    "safety_weeks": {
      "default": 2,
      "minimum": 0,
      "type": "number",
      "description": "Weeks of demand held as buffer against a late delivery.\nDefault 2."
    }
  },
  "required": [
    "unit_cost",
    "moq",
    "monthly_demand",
    "cash_available"
  ],
  "additionalProperties": false
}

出力スキーマ

{
  "type": "object",
  "additionalProperties": true
}
🟢returns_impact(sell_price, unit_profit, unit_cost, return_rate_pct, restock_pct, ...)

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": 6} returns {"cost_per_return": 37.31, "effective_profit": 10.25, "profit_lost_pct": 22.56, "break_even_return_rate_pct": 35.46}. Use when a category's returns are high enough to argue about. Not for the pre-returns margin itself — that is margin_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

入力スキーマ

{
  "type": "object",
  "properties": {
    "sell_price": {
      "exclusiveMinimum": 0,
      "type": "number",
      "description": "Price the customer paid."
    },
    "unit_profit": {
      "type": "number",
      "description": "Profit on one kept sale, from margin_check. May be\nnegative, which the result will make obvious."
    },
    "unit_cost": {
      "minimum": 0,
      "type": "number",
      "description": "What the goods themselves cost you — the only part a\nrestocked unit gives back. Advertising and fees do not return."
    },
    "return_rate_pct": {
      "maximum": 100,
      "minimum": 0,
      "type": "number",
      "description": "Percentage of orders returned, e.g. 8."
    },
    "restock_pct": {
      "default": 0,
      "maximum": 100,
      "minimum": 0,
      "type": "number",
      "description": "Percentage of returned units resellable at full price.\nDefault 0, the conservative case."
    },
    "return_shipping": {
      "default": 0,
      "minimum": 0,
      "type": "number",
      "description": "What an inbound return costs you. Default 0."
    },
    "refund_pct": {
      "default": 100,
      "maximum": 100,
      "minimum": 0,
      "type": "number",
      "description": "Percentage of the sale price refunded, e.g. 100 for a\nfull refund or 80 when a restocking fee is kept. Default 100."
    }
  },
  "required": [
    "sell_price",
    "unit_profit",
    "unit_cost",
    "return_rate_pct"
  ],
  "additionalProperties": false
}

出力スキーマ

{
  "type": "object",
  "additionalProperties": true
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 6 件
検証済みバージョンは記録されていませんツール 6 件