Moltline Dropship Economics
REMOTE · MCP.MOLTLINESTUDIO.COM
Margin, lead time, SKU mapping and price-ladder maths for dropshipping. 4 of 6 free.
Available components
Last scanned (5 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2232 tokens (~372/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “lead_time” rewrote its description, which is the text the model reads security
- Tool “margin_check” rewrote its description, which is the text the model reads security
- Tool “moq_planner” rewrote its description, which is the text the model reads security
- Tool “price_ladder” rewrote its description, which is the text the model reads security
- Tool “returns_impact” rewrote its description, which is the text the model reads security
- Tool “sku_map_check” rewrote its description, which is the text the model reads security
- “margin_check” reworded the description of “payment_fee_pct” cosmetic
- “returns_impact” reworded the description of “unit_cost” cosmetic
- 25 Oct 26 0
- Tool “lead_time” rewrote its description, which is the text the model reads security
- Tool “margin_check” rewrote its description, which is the text the model reads security
- Tool “moq_planner” rewrote its description, which is the text the model reads security
- Tool “price_ladder” rewrote its description, which is the text the model reads security
- Tool “returns_impact” rewrote its description, which is the text the model reads security
- Tool “sku_map_check” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.moltlinestudio.com/dropship
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=moltlinestudio.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5fcf21014c71aedb0ee8aa375beac0b4 |
| SANs: moltlinestudio.com, *.moltlinestudio.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.moltlinestudio.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| moltlinestudio.com. | present | 2371 | 13 | Verified |
| mcp.moltlinestudio.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15576000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-3121b325-009e-46ea-bda6-e76896d46104'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.moltlinestudio.com https://mcp.moltlinestudio.com; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.moltlinestudio.com/dropship | Verified | 200 | |
| http (plaintext) | http://mcp.moltlinestudio.com/dropship | HTTPS enforced | 301 | https://mcp.moltlinestudio.com/dropship |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lead_time Lead Time ~337
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Days from your order to the supplier despatching it. |
| transit_days | integer | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
margin_check Margin Check ~418
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What the customer pays, excluding tax. Must be above 0. |
| shipping_cost | number | – | Shipping you absorb per order. Default 0. |
| supplier_cost | number | yes | What the supplier charges you per unit. |
Structured output declared, but exposes no named fields.
No examples provided.
moq_planner Moq Planner ~341
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cash_available | number | yes | 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 | yes | Units you expect to sell per month. Must be above 0. |
| moq | integer | yes | 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 | yes | Cost per unit at the MOQ. Must be above 0. |
Structured output declared, but exposes no named fields.
No examples provided.
price_ladder Price Ladder ~381
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
returns_impact Returns Impact ~426
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Percentage of orders returned, e.g. 8. |
| return_shipping | number | – | What an inbound return costs you. Default 0. |
| sell_price | number | yes | Price the customer paid. |
| unit_cost | number | yes | What the goods themselves cost you, the only part a restocked unit gives back. Advertising and fees do not return. |
| unit_profit | number | yes | Profit on one kept sale, from margin_check. May be negative, which the result will make obvious. |
Structured output declared, but exposes no named fields.
No examples provided.
sku_map_check Sku Map Check ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mapping | object | yes | Store SKU to supplier SKU, e.g. {"STORE-1": "SUP-A"}. At least one entry. |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · mcp.moltlinestudio.com
claude mcp add --transport http com-moltlinestudio-dropship 'https://mcp.moltlinestudio.com/dropship'
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,176 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.