# Moltline Dropship Economics (remote · mcp.moltlinestudio.com)

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

- Trust score: 86/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.moltlinestudio.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-moltlinestudio-dropship/dropship.md), [page](https://verifymcp.io/servers/com-moltlinestudio-dropship/dropship)

## Channel facts

- Endpoint: `https://mcp.moltlinestudio.com/dropship`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2233 tokens (~372/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Moltline Dropship Economics MCP server?

Moltline Dropship Economics is a hosted endpoint at https://mcp.moltlinestudio.com/dropship, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-moltlinestudio-dropship 'https://mcp.moltlinestudio.com/dropship'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "com-moltlinestudio-dropship": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/dropship"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-moltlinestudio-dropship]
url = "https://mcp.moltlinestudio.com/dropship"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-moltlinestudio-dropship": {
      "type": "remote",
      "url": "https://mcp.moltlinestudio.com/dropship",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-moltlinestudio-dropship --url 'https://mcp.moltlinestudio.com/dropship' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-moltlinestudio-dropship:
    url: "https://mcp.moltlinestudio.com/dropship"
```

### Netclaw

```json
{
  "McpServers": {
    "com-moltlinestudio-dropship": {
      "Transport": "http",
      "Url": "https://mcp.moltlinestudio.com/dropship"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-moltlinestudio-dropship -t streamable-http -u 'https://mcp.moltlinestudio.com/dropship'
```

### Other

```json
{
  "mcpServers": {
    "com-moltlinestudio-dropship": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/dropship"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `margin_check` (~418 tokens)

Margin Check

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.

Input parameters:

- `ad_cost_per_order` (number): Blended acquisition cost per order. Default 0, but leaving it at 0 is the most common way this maths lies.
- `other_cost` (number): Anything else per order: packaging inserts, app fees, support time. Default 0.
- `payment_fee_fixed` (number): Processor fixed fee per transaction. Default 0.30.
- `payment_fee_pct` (number): Processor percentage fee. Default 2.9 — a common published rate, not a statement about your account.
- `sell_price` (number, required): What the customer pays, excluding tax. Must be above 0.
- `shipping_cost` (number): Shipping you absorb per order. Default 0.
- `supplier_cost` (number, required): What the supplier charges you per unit.

### `lead_time` (~337 tokens)

Lead Time

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.

Input parameters:

- `buffer_days` (integer): Extra days added before the date you publish. Default 2.
- `order_date` (string): Start date as YYYY-MM-DD, e.g. "2026-08-20". Defaults to today when omitted.
- `supplier_days` (integer, required): Days from your order to the supplier despatching it.
- `transit_days` (integer, required): Days in transit from despatch to the customer.
- `working_days_only` (boolean): When true, count supplier and transit days as Monday-Friday only. Default false.

### `sku_map_check` (~273 tokens)

Sku Map Check

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.

Input parameters:

- `mapping` (object, required): Store SKU to supplier SKU, e.g. {"STORE-1": "SUP-A"}. At least one entry.

### `price_ladder` (~382 tokens)

Price Ladder

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.

Input parameters:

- `charm_ending` (string): Force prices to end in these cents, e.g. ".99". Pass an empty string for exact prices. Default ".99".
- `payment_fee_fixed` (number): Processor fixed fee. Default 0.30.
- `payment_fee_pct` (number): Processor percentage fee. Default 2.9.
- `shipping_cost` (number): Shipping you absorb per order. Default 0.
- `supplier_cost` (number, required): Per-unit cost from the supplier. Must be above 0.
- `target_margins_pct` (array, required): Margins to solve for, e.g. [30, 40, 50]. Each must be above 0 and below 100.

### `moq_planner` (~341 tokens)

Moq Planner

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.

Input parameters:

- `cash_available` (number, required): Cash you can commit to stock right now.
- `lead_time_days` (integer): Days from placing the order to stock being sellable. Default 30.
- `monthly_demand` (number, required): Units you expect to sell per month. Must be above 0.
- `moq` (integer, required): The supplier's minimum order quantity, in units.
- `safety_weeks` (number): Weeks of demand held as buffer against a late delivery. Default 2.
- `unit_cost` (number, required): Cost per unit at the MOQ. Must be above 0.

### `returns_impact` (~426 tokens)

Returns Impact

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.

Input parameters:

- `refund_pct` (number): Percentage of the sale price refunded, e.g. 100 for a full refund or 80 when a restocking fee is kept. Default 100.
- `restock_pct` (number): Percentage of returned units resellable at full price. Default 0, the conservative case.
- `return_rate_pct` (number, required): Percentage of orders returned, e.g. 8.
- `return_shipping` (number): What an inbound return costs you. Default 0.
- `sell_price` (number, required): Price the customer paid.
- `unit_cost` (number, required): What the goods themselves cost you — the only part a restocked unit gives back. Advertising and fees do not return.
- `unit_profit` (number, required): Profit on one kept sale, from margin_check. May be negative, which the result will make obvious.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-moltlinestudio-dropship/dropship#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 86
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 83
- 2026-09-12: 83
- 2026-09-11: 82
- 2026-09-10: 82
- 2026-09-09: 81
- 2026-09-08: 81
- 2026-09-07: 80
- 2026-09-06: 80
- 2026-09-05: 79
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 78
- 2026-09-01: 78
- 2026-08-31: 77
- 2026-08-30: 77
- 2026-08-29: 76
- 2026-08-28: 76
- 2026-08-27: 75
- 2026-08-26: 75
- 2026-08-25: 73
- 2026-08-24: 72
- 2026-08-23: 72

## Common questions

### What is the Moltline Dropship Economics MCP server?

Moltline Dropship Economics is an MCP server listed in the public MCP registry as com.moltlinestudio/dropship. Margin, lead time, SKU mapping and price-ladder maths for dropshipping. 4 of 6 free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/dropship).

### Is the Moltline Dropship Economics MCP server safe to use?

Moltline Dropship Economics scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Moltline Dropship Economics MCP server expose?

Moltline Dropship Economics exposes 6 tools: margin_check, lead_time, sku_map_check, price_ladder, moq_planner, returns_impact. Their descriptions and schemas cost roughly 2,177 tokens of context every time the server is loaded.

### Does the Moltline Dropship Economics MCP server require authentication?

No. We connected to Moltline Dropship Economics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Moltline Dropship Economics MCP server still maintained?

Moltline Dropship Economics is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.moltlinestudio.com/dropship
- Repository: https://github.com/GarphenGate/moltline-mcp
- Website: https://moltlinestudio.com/servers.html#dropship
- Changelog RSS feed: https://verifymcp.io/servers/com-moltlinestudio-dropship/dropship.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-moltlinestudio-dropship/dropship.json
- HTML version of this page: https://verifymcp.io/servers/com-moltlinestudio-dropship/dropship