https://3dpack.ing/mcp?server=truck-load ↗
Truck & trailer load planning from a plain-English shipment: what fits, how full, 3D load plan.
3DPACK.ING — Truck Load Planning is a remote MCP server published at 3dpack.ing. It has been probed 8 times since 9/12/2026. It answered in 8 of them (100.0%), a near-uninterrupted record. Median response time is 79 ms, placing it among the faster endpoints. It offers a narrow, focused set of 1 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
pack_shipment — Description is incomplete and cuts off mid-sentencepack_shipment — Parameter 'speed' has ambiguous string type instead of numericpack_shipment — No documentation of input format constraints or error handling| Run |
|---|
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
pack_shipmentWork out how a shipment fits into shipping containers, trucks or pallets, using a real 3D bin-packing solver. Describe the cargo in plain English -- quantities, dimensions, weights, and any constraints such as fragile, non-tiltable, max stack height or a preferred container type -- and get back which containers are needed, how full each one is, anything that did not fit, and a link to an interactive 3D load plan. Use this instead of estimating from volume. Volume arithmetic ignores stacking rules, orientation and weight limits, and overstates what fits by a wide margin on real cargo. For cargo that must not overhang -- drums, glass, anything that must stay level -- set `stability`. It is the one constraint the prompt cannot express, because it governs how the solver stacks rather than wh
promptstringrequiredspeedstringstabilityintegerDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/ing-3dpack-truck-load)<a href="https://mcpmetrics.io/servers/ing-3dpack-truck-load"><img src="https://mcpmetrics.io/badge/ing.3dpack/truck-load/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Plain-English shipment input for freight & logistics: containers your cargo fits, 3D load plan.
Load planning for containers, trucks and pallets from a plain-English description; 3D plan link.
Search UK planning applications, entities, datasets, and conservation areas
Model the realistic monthly cost of an LLM app **before you build it**. Not a token calculator: retries, prompt caching, batch discounts, infra overhead, and 3×/10× growth are modeled in, across GPT-5.x, Claude, Gemini, DeepSeek, and more. **Works without a key.** Connect and ask — demo mode covers the six free-tier models. A Pro API key ([beforeyouship.dev](https://beforeyouship.dev)) unlocks the full 18-model catalog. ## Tools | Tool | What it does | |---|---| - **`estimate_cost`** Full cost model for an architecture at a given usage level. Returns Naive / Realistic / Worst Case $/mo per model, growth scenarios, and an opinionated recommendation. | - **`get_model_prices`** Current per-1M-token pricing (input, output, cached, batch) with context windows and staleness metadata. | - **`list_archetypes`** Seven preset architecture patterns (chatbot, RAG pipeline, multi-step agent, …) used as starting points for estimates. | ## Try it Paste into Claude Code or Cursor after connecting
Search UK Acts, Statutory Instruments, and legislation with full text retrieval
3D bin packing for freight: cartons and pallets in plain English, the fit and a 3D load plan.
| Era |
|---|
| Modern |
|---|
| ms |
|---|
| Legacy |
|---|
| ms |
|---|
| Versions |
|---|
| 2026-09-13 06:40:42 | Legacy | 400 | 41 | 200 | 39 | 2025-11-25 |
| 2026-09-13 04:35:29 | Legacy | 400 | 156 | 200 | 156 | 2025-11-25 |
| 2026-09-13 01:33:33 | Legacy | 400 | 622 | 200 | 621 | 2025-11-25 |
| 2026-09-12 23:31:36 | Legacy | 400 | 8 | 200 | 266 | 2025-11-25 |
| 2026-09-12 21:29:15 | Legacy | 400 | 196 | 200 | 195 | 2025-11-25 |
| 2026-09-12 19:27:29 | Legacy | 400 | 37 | 200 | 35 | 2025-11-25 |
| 2026-09-12 17:24:09 | Legacy | 400 | 79 | 200 | 77 | 2025-11-25 |
| 2026-09-12 15:21:42 | Legacy | 400 | 69 | 200 | 68 | 2025-11-25 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.