# Moltline Shipping Maths (remote · mcp.moltlinestudio.com)

Dimensional weight, parcel fit, landed cost and freight class. 4 of 6 tools free.

- Trust score: 85/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`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-moltlinestudio-shipping/shipping.md), [page](https://verifymcp.io/servers/com-moltlinestudio-shipping/shipping)

## Channel facts

- Endpoint: `https://mcp.moltlinestudio.com/shipping`
- 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**: 57/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2369 tokens (~394/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 Shipping Maths MCP server?

Moltline Shipping Maths is a hosted endpoint at https://mcp.moltlinestudio.com/shipping, 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-shipping 'https://mcp.moltlinestudio.com/shipping'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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 85, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 85, +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-15 (score 84, +1)

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

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

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

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

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

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

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

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

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

### 2026-09-05 (score 79, +1)

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

## MCP tools (6)

### `dim_weight` (~474 tokens)

Dim Weight

Work out whether a parcel bills on its size or its weight. FREE.

Carriers charge the greater of actual weight and dimensional weight, so a
light bulky box costs more than the scale suggests. Typical input
{"length": 18, "width": 12, "height": 10, "actual_weight": 6} returns
{"cubic": 2160.0, "dim_weight": 15.54, "actual_weight": 6.0,
"billable_weight": 15.54, "billed_on": "dimensional", "overage": 9.54,
"divisor_used": 139.0, "note": "..."}.

Use when deciding whether a smaller box is worth the packing effort, or
why an invoice exceeded the scale weight. Not for choosing a box from a
list of candidates — that is parcel_fit. 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": "custom_divisor must be greater than 0 when divisor is 'custom'"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `actual_weight` (number, required): Scale weight in pounds (or kilograms with a metric divisor). Must be greater than 0.
- `custom_divisor` (number): Your contracted divisor, used only when divisor is "custom". Must be greater than 0 in that case.
- `divisor` (string): Which published divisor to apply. "ups_daily" is 139 and "ups_retail" is 166 cubic inches per pound, as UPS states them; "usps" is 166; the metric options are cubic centimetres per kilogram. Use "cus…
- `height` (number, required): Third side, same unit as length. Must be greater than 0.
- `length` (number, required): Longest side of the packed parcel, in inches (or centimetres when using a metric divisor). Must be greater than 0.
- `width` (number, required): Second side, same unit as length. Must be greater than 0.

### `parcel_fit` (~405 tokens)

Parcel Fit

Pick the smallest box an item actually fits in, allowing for padding. FREE.

Tries every rotation of the item against every box, so an item that only
fits diagonally-oriented is still found. Typical input {"item_length": 10,
"item_width": 6, "item_height": 4, "box_options": [[12, 9, 4], [14, 10,
6]]} returns {"fits": [{"box": [14, 10, 6], "cubic": 840.0, "slack": [2,
2, 0]}], "best": [14, 10, 6], "rejected": [...]}.

Use when choosing packaging from stock. Not for what the carrier will bill
once a box is chosen — that is dim_weight. 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": "box_options must contain at least one [l, w, h] box"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `box_options` (array, required): Candidate inner box dimensions, each a list of exactly three positive numbers, e.g. [[12, 9, 4], [14, 10, 6]].
- `item_height` (number, required): Item's third side, same unit. Must be greater than 0.
- `item_length` (number, required): Item's longest side, in inches. Must be greater than 0.
- `item_width` (number, required): Item's second side, same unit. Must be greater than 0.
- `padding` (number): Cushioning allowance added to every item side before the comparison, in the same unit. Default 1.0; use 0 for a bare fit.

### `landed_cost` (~413 tokens)

Landed Cost

Total what a unit really costs once freight, duty and fees are in. FREE.

Duty is applied to goods value, tax to goods plus duty plus freight — the
common import treatment — and the order is spelled out in the response so
you can check it against your own broker's method. Typical input
{"unit_cost": 8.5, "quantity": 200, "freight_total": 640, "duty_pct": 6.5,
"tax_pct": 0} returns {"goods": 1700.0, "duty": 110.5, "freight": 640.0,
"tax": 0.0, "total_landed": 2450.5, "landed_unit_cost": 12.25, ...}.

Use before setting a price on imported stock. Not for the margin that price
leaves you — that is the dropship server's 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:

- `duty_pct` (number): Import duty as a percentage of goods value, e.g. 6.5. Default 0.
- `freight_total` (number): Total freight and insurance for the whole shipment, not per unit. Default 0.
- `other_fees` (number): Brokerage, port and handling charges for the shipment. Default 0.
- `quantity` (integer): Units in the shipment. Must be at least 1. Default 1.
- `tax_pct` (number): Import VAT or GST as a percentage of goods plus duty plus freight, e.g. 20. Default 0.
- `unit_cost` (number, required): Ex-works cost of one unit in your currency. Must be greater than 0.

### `freight_class` (~323 tokens)

Freight Class

Derive a US LTL freight class from density. FREE.

Density in pounds per cubic foot maps to a class on the published NMFC
density scale. Typical input {"length": 48, "width": 40, "height": 36,
"weight": 400} returns {"cubic_feet": 40.0, "density_pcf": 10.0,
"density_class": "100", "caveat": "..."}.

Use for a first estimate before a carrier quote. Not as a final
classification: NMFC also weighs stowability, handling and liability, so a
carrier can and does reclassify. 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": "dimensions produce zero volume"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `height` (number, required): Third side, including the pallet. Must be greater than 0.
- `length` (number, required): Longest side of the palletised freight. Must be greater than 0.
- `units` (string): "in_lb" for inches and pounds, or "cm_kg" for centimetres and kilograms. Default "in_lb".
- `weight` (number, required): Gross weight including the pallet. Must be greater than 0.
- `width` (number, required): Second side. Must be greater than 0.

### `rate_card` (~393 tokens)

Rate Card

Turn a cost model into a customer-facing weight-banded price table. PREMIUM (license).

Prices each band at its upper bound so you never under-charge inside a
band, then rounds up to a tidy increment. Typical input {"base_cost": 4.2,
"cost_per_lb": 0.65, "bands_lb": [1, 2, 5, 10], "margin_pct": 25} returns
{"bands": [{"up_to_lb": 1, "cost": 4.85, "price": 6.5}, ...],
"over_top_band": "quote individually"}.

Use when publishing shipping prices customers pay. Not for the cut-off at
which shipping becomes free — that is free_shipping_threshold. 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": "bands_lb must contain at least one upper bound"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `bands_lb` (array, required): Upper weight bound of each band in ascending order, e.g. [1, 2, 5, 10]. At least one band, each greater than 0.
- `base_cost` (number, required): Fixed cost per shipment before weight, e.g. pick, pack and label. Must be greater than 0.
- `cost_per_lb` (number, required): Marginal cost per pound. Use 0 for a flat rate card.
- `margin_pct` (number): Margin added on top of cost, e.g. 25 for 25%. Default 0.
- `round_to` (number): Increment to round each published price up to, e.g. 0.5 or 1. Default 0.5.

### `free_shipping_threshold` (~307 tokens)

Free Shipping Threshold

Find the order value at which free shipping stops costing you money. PREMIUM (license).

Break-even is where the gross margin on the order covers the shipping you
absorb. Typical input {"gross_margin_pct": 45, "ship_cost": 7.5,
"current_aov": 38, "target_uplift_pct": 15} returns {"break_even": 16.67,
"suggested_threshold": 43.7, "above_current_aov_by": 5.7, "rationale":
"..."}.

Use when setting or defending a free-shipping bar. Not for what shipping
should cost when it is not free — that is rate_card. 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:

- `current_aov` (number, required): Your current average order value.
- `gross_margin_pct` (number, required): Gross margin on a typical order, e.g. 45 for 45%. Must be above 0 and at most 100.
- `ship_cost` (number, required): What one shipment actually costs you to send.
- `target_uplift_pct` (number): How far above current AOV you want the threshold set, to pull baskets up. Default 0, which returns break-even.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Moltline Shipping Maths MCP server?

Moltline Shipping Maths is an MCP server listed in the public MCP registry as com.moltlinestudio/shipping. Dimensional weight, parcel fit, landed cost and freight class. 4 of 6 tools free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/shipping).

### Is the Moltline Shipping Maths MCP server safe to use?

Moltline Shipping Maths scores 85 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 Shipping Maths MCP server expose?

Moltline Shipping Maths exposes 6 tools: dim_weight, parcel_fit, landed_cost, freight_class, rate_card, free_shipping_threshold. Their descriptions and schemas cost roughly 2,315 tokens of context every time the server is loaded.

### Does the Moltline Shipping Maths MCP server require authentication?

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

### Is the Moltline Shipping Maths MCP server still maintained?

Moltline Shipping Maths 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/shipping
- Repository: https://github.com/GarphenGate/moltline-mcp
- Website: https://moltlinestudio.com/servers.html#shipping
- Changelog RSS feed: https://verifymcp.io/servers/com-moltlinestudio-shipping/shipping.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-moltlinestudio-shipping/shipping.json
- HTML version of this page: https://verifymcp.io/servers/com-moltlinestudio-shipping/shipping