io.github.lxxmng/container-loading
REMOTE · MCP.LOADINGMCP.COM
Plan optimal container & truck loads: 3D layouts, utilization, centre of gravity, crush checks.
Available components
Last scanned (2 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1479 tokens (~246/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
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 6 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.
- 30 Oct 26 −1
- Tool “export_plan” rewrote its description, which is the text the model reads security
- Schema quality: 168 → 246 ▼ functional
- “plan_load” added an optional parameter “complyingSteerAxle” cosmetic
- “plan_load” added an optional parameter “freight” cosmetic
- “plan_load” added an optional parameter “massLimits” cosmetic
- “plan_load” added an optional parameter “topUp” cosmetic
- “plan_load” added an optional parameter “vehicleTareKg” cosmetic
- “plan_load” reworded the description of “jurisdiction” cosmetic
- 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
- 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 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
- 5 Aug 26 0
- HTTPS: unverified → pass ▲ security
- Schema quality: 631 → 1009 ▼ functional
- New tool “export_dg_paperwork” functional
- New tool “import_packing_list” functional
- “plan_load” added an optional parameter “vesselMotion” cosmetic
- 31 Jul 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
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.loadingmcp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.loadingmcp.com | CN=YE2,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6aae5d37393b20f1681dadc2c4c7956e413 |
| SANs: mcp.loadingmcp.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.loadingmcp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| loadingmcp.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.loadingmcp.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.loadingmcp.com/mcp | HTTPS enforced | 301 | https://mcp.loadingmcp.com/mcp |
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 →
export_dg_paperwork ~181
Draft the dangerous-goods paperwork for a load from its cargo lines: an IMDG 5.4.1 transport-document description per DG line (UN, proper shipping name, class, PG, marine pollutant), the 5.3 placards + marks required, and the 5.4.2 container/vehicle packing-certificate statements. Input is a "loadingmcp.packing-list" document. This is a DRAFT from the curated DGL — it lists the fields a DG-competent person must still complete (flash point, net explosive mass, unverified PSN) and is never signed.
| Name | Type | Req | Description |
|---|---|---|---|
| packingList | object | yes | A loadingmcp.packing-list document with DG-bearing lines (unNumber/hazmatClass/packingGroup/marinePollutant). See docs/INTEGRATION.md. |
No output schema declared.
No examples provided.
export_plan ~286
Export a load as a machine-readable LOADING WORK ORDER: a numbered stuffing sequence (which SKU, where, in what order and orientation), the securing/bracing action list, a securing shopping list per container (`securingBom`: straps, airbags, timber, bars, with quantities, specs and the work-order steps each goes to; recommendations to verify with the carrier), the key declarable figures (VGM, axle load, centre of gravity), and an optional per-retailer inbound-packaging check (Amazon FBA / Walmart). Feed it to a WES/TMS, a robotic palletiser, or a printable worker sheet. A real API key packs it with the production PackingSolver optimizer (the same plan plan_load returns for the same cargo); the public demo key uses the offline preview packer; `engine` in the result says which one ran. This is decision support to MEET published retailer/carrier specs — verify in your own portal; it is not a retailer certification.
| Name | Type | Req | Description |
|---|---|---|---|
| equipmentCode | string | – | Equipment code, e.g. 40HC (see list_equipment). Omit to auto right-size. |
| items | array | yes | Cargo lines to load |
| mode | string | – | Transport mode for auto right-size (ignored when equipmentCode is given). |
| retailers | array | – | Retailer inbound-packaging profiles to check the load against. |
No output schema declared.
No examples provided.
import_packing_list ~137
ERP/TMS on-ramp: take a versioned "loadingmcp.packing-list" document (a WMS/ERP export — cargo lines + equipmentCode) and return a load plan + a container manifest. Parsing is fail-explicit: an invalid document returns the exact per-line issues, never a silently-dropped row. Pairs with plan_load's output for a full round-trip.
| Name | Type | Req | Description |
|---|---|---|---|
| packingList | object | yes | A loadingmcp.packing-list document: { format: "loadingmcp.packing-list", formatVersion, equipmentCode, jurisdiction?, lines: [...] }. See docs/INTEGRATION.md. |
No output schema declared.
No examples provided.
list_equipment ~51
List the standard container, truck, ULD and pallet types LoadingMCP can plan loads into, with internal dimensions (mm) and max payload (kg).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter |
No output schema declared.
No examples provided.
plan_load ~732
Compute a 3D load plan for cargo into a container or truck: containers used, utilization (volume & payload %), centre of gravity, crush-protection violations, and a securing checklist (round cargo that rolls, soft cargo that slumps). Cargo `type` drives realism — drums/pipes hex-nest, big bags/sacks load on top and are never crushed. Omit `equipmentCode` to auto right-size to the cheapest container that fits. A real API key runs the production PackingSolver optimizer; the public demo key uses the offline preview packer.
| Name | Type | Req | Description |
|---|---|---|---|
| complyingSteerAxle | boolean | – | AU only: the prime mover is an HVNL complying steer axle vehicle (6.5 t steer, 44 t combination). Default false. |
| equipmentCode | string | – | Equipment code, e.g. 40HC (see list_equipment). Omit to auto right-size. |
| freight | object | – | Freight cost per unit: split the ocean freight for this load (rate per container x containers used) across the cargo lines, per line and per unit, so it can go into product cost. Uses the indicative… |
| items | array | yes | Cargo lines to load |
| jurisdiction | string | – | Road jurisdiction for the axle / gross-weight compliance check (default EU). Set CN for China GB 1589 drayage limits, AU for Australian HVNL general mass limits (NSW, Vic, Qld, SA, Tas, ACT), AU-WA f… |
| massLimits | string | – | Australian mass tier (default general). hml = HVNL Higher Mass Limits for AU (tri-axle 22.5 t, 6-axle combination 45.5 t; needs an HML route, road-friendly suspension and mass accreditation) or the N… |
| mode | string | – | Transport mode — scopes auto right-size to usable equipment (sea→containers, road→trucks, air→ULDs). Ignored when equipmentCode is given. |
| sequenceStops | boolean | – | Delivery-stop sequencing: with ≥2 distinct deliveryStop values, zone the load nose→doors in reverse delivery order. |
| topUp | boolean | – | Also return `topUp`: for each cargo line, how many MORE units still fit in the same containers with every unit placed and the load still ready (e.g. "+6 of SKU A, fill 82%"). Takes longer, since it r… |
| vehicleTareKg | number | – | Your road vehicle tare in kg (container: prime mover + chassis/skeletal; truck: the truck). Replaces the nominal tare in the gross check (AU default 14,100 kg, elsewhere 11,600 kg for a container com… |
| vesselMotion | object | – | IMO CSS Annex 13 vessel motion + stowage position. When set, the sea leg uses the position-dependent DYNAMIC acceleration field (a container on deck forward sees a far harsher case than one low amids… |
| vgm | object | – | SOLAS Verified Gross Mass declaration (else a tare+cargo estimate is reported) |
No output schema declared.
No examples provided.
suggest_containers ~92
Given total cargo volume (m³) and weight (kg), suggest how many of which container to use — a quick volume/weight estimate. For an exact, dimension-aware plan with utilization, CoG and securing, use plan_load (which can also auto right-size).
| Name | Type | Req | Description |
|---|---|---|---|
| volumeM3 | number | yes | Total cargo volume in cubic metres |
| weightKg | number | yes | Total cargo weight in kilograms |
No output schema declared.
No examples provided.
How do I install the io.github.lxxmng/container-loading MCP server?
io.github.lxxmng/container-loading is a hosted endpoint at https://mcp.loadingmcp.com/mcp, 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.loadingmcp.com
claude mcp add --transport http lxxmng-container-loading 'https://mcp.loadingmcp.com/mcp'
What is the io.github.lxxmng/container-loading MCP server?
io.github.lxxmng/container-loading is an MCP server listed in the public MCP registry as io.github.lxxmng/container-loading. Plan optimal container & truck loads: 3D layouts, utilization, centre of gravity, crush checks. This page covers its hosted endpoint (https://mcp.loadingmcp.com/mcp).
Is the io.github.lxxmng/container-loading MCP server safe to use?
io.github.lxxmng/container-loading scores 76 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 io.github.lxxmng/container-loading MCP server expose?
io.github.lxxmng/container-loading exposes 6 tools: list_equipment, suggest_containers, plan_load, export_plan, import_packing_list, export_dg_paperwork. Their descriptions and schemas cost roughly 1,479 tokens of context every time the server is loaded.
Does the io.github.lxxmng/container-loading MCP server require authentication?
No. We connected to io.github.lxxmng/container-loading without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.lxxmng/container-loading MCP server still maintained?
io.github.lxxmng/container-loading 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.