3DPACK.ING — Truck Load Planning
REMOTE · 3DPACK.ING
Truck & trailer load planning in Claude & ChatGPT: what fits, how full, a labelled 3D plan in chat.
Available components
Last scanned (9 hours ago)
Scores higher than 35% of remote servers
Reachable. Last reached 6 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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 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
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Sept 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 6 Nov 2026 · Probed https://3dpack.ing/mcp?server=truck-load
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=3dpack.ing | CN=YR2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | RSA 2048 | SHA256-RSA | 6079041b0ac0302f1a84e7b5eec93234277 |
| SANs: 3dpack.ing, www.3dpack.ing | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 3dpack.ing. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ing. | DS published | 27256 | 8 | Verified |
| 3dpack.ing. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://3dpack.ing/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://3dpack.ing/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| www-authenticate | Bearer resource_metadata="https://3dpack.ing/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://3dpack.ing/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://3dpack.ing/mcp |
| Authorisation server | https://3dpack.ing |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://3dpack.ing/mcp?server=truck-load | Auth required | 401 | |
| http (plaintext) | http://3dpack.ing/mcp?server=truck-load | HTTPS enforced | 308 | https://3dpack.ing/mcp?server=truck-load |
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 →
pack_shipment Pack a shipment into containers or trucks ~429
Work 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 what is being shipped.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | The shipment, in plain English. Include quantities, dimensions with units, and weights if known. Examples: "Pack 50 boxes of 60x40x30 cm into a 20ft container"; "Load 100 fragile items 80x60x40cm, ma… |
| speed | string | – | How hard the solver should look for a better arrangement. Omit to let it choose. Use 'fast' for a quick feasibility check, 'thorough' when the packing quality matters. |
| stability | integer | – | How much of a box must rest on what is underneath it, as a percentage of its own footprint. Omit for the standard rule of 75, which allows a quarter of a box to overhang and packs the most. Raise it… |
No output schema declared.
No examples provided.
How do I install the 3DPACK.ING — Truck Load Planning MCP server?
3DPACK.ING — Truck Load Planning is a hosted endpoint at https://3dpack.ing/mcp?server=truck-load, 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 · 3dpack.ing
claude mcp add --transport http ing-3dpack-truck-load 'https://3dpack.ing/mcp?server=truck-load'
What is the 3DPACK.ING — Truck Load Planning MCP server?
3DPACK.ING — Truck Load Planning is an MCP server listed in the public MCP registry as ing.3dpack/truck-load. Truck & trailer load planning in Claude & ChatGPT: what fits, how full, a labelled 3D plan in chat. This page covers its hosted endpoint (https://3dpack.ing/mcp?server=truck-load).
Is the 3DPACK.ING — Truck Load Planning MCP server safe to use?
3DPACK.ING — Truck Load Planning scores 39 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 3DPACK.ING — Truck Load Planning MCP server expose?
3DPACK.ING — Truck Load Planning exposes 1 tool: pack_shipment. Their descriptions and schemas cost roughly 429 tokens of context every time the server is loaded.
Does the 3DPACK.ING — Truck Load Planning MCP server require authentication?
Yes. 3DPACK.ING — Truck Load Planning asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the 3DPACK.ING — Truck Load Planning MCP server still maintained?
3DPACK.ING — Truck Load Planning is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the 3DPACK.ING — Truck Load Planning MCP server?
VerifyMCP ran 5 checks on 3DPACK.ING — Truck Load Planning, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about 3DPACK.ING — Truck Load Planning: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.