Zhihuo Container Loading
REMOTE · MCP.ZHIHUO.NET
How many identical cartons fit in a container or space, where they go, plus a 3D loading plan.
Available components
Last scanned (14 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Cloud Infrastructure
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Moved to com.cuberithm.mcp/container-loading at https://mcp.cuberithm.com/mcp (Brimload Container Loading). This address keeps working.
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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1105 tokens (~552/item across 2 items; 2 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (50% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 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 Oct 26 0
- Server version: 1.27.2 → 1.30.0 functional
- 24 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → good functional
- 19 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: Zhihuo Container Loading → Brimload Container Loading security
- Tool “pack_boxes” rewrote its description, which is the text the model reads security
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 21 Nov 2026 · Probed https://mcp.zhihuo.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.zhihuo.net | CN=YE2,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 652d79865f6b5849f2560849105ff0a8744 |
| SANs: mcp.zhihuo.net | ||||||
| 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.zhihuo.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| zhihuo.net. | No DS | 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.zhihuo.net/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.zhihuo.net/mcp | HTTPS enforced | 308 | https://mcp.zhihuo.net/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 →
pack_boxes ~683
Calculate how many identical boxes fit in a rectangular space, and where. The space is a shipping container, a pallet area, leftover container space, or a larger box. Give the box's L/W/H and EITHER a `container` preset OR the space's L/W/H (all in millimetres - container presets are mm). Boxes mix orientations across regions to pack densely; the plain maximum-load answer uses the exact T1 solver. Args: box_length: Box length. box_width: Box width. box_height: Box height. container: Container preset instead of explicit space dims (fills the internal usable L/W/H in mm; overrides space_* when recognised). ISO dry: 20GP 20HQ 40GP 40HQ 45GP 45HQ; NA domestic: 53HC 48HC; reefers: 20RF 40RF 40RH; EU pallet-wide: 40HQ-PW 45HQ-PW. Many aliases (20/40/45, 20ft, 40HC, 40', 40 reefer, ...). space_length: Space length (front-back). Use this OR `container`. space_width: Space width (left-right). space_height: Space height (up). count: How many boxes to load. 0 (default) loads the maximum. to_front: Anchor a partial load to the front (else the back). to_left: Anchor a partial load to the left (else the right). to_bottom: Kept for compatibility, no effect: boxes always rest on the floor. box_weight: Weight of one box (optional; same unit as max_weight). max_weight: Max total load weight (optional; 0 = no weight limit). include_image: Set true ONLY when the user wants to SEE or visualize the loading plan / 3D layout (e.g. "show the loading plan", "visualize it", "what does it look like?"). Default false is faster and lighter and still returns `image_url`, a shareable link to the 3D render. When true, the image is ALSO embedd…
| Name | Type | Req | Description |
|---|---|---|---|
| box_height | integer | yes | – |
| box_length | integer | yes | – |
| box_weight | integer | – | – |
| box_width | integer | yes | – |
| container | string | – | – |
| count | integer | – | – |
| include_image | boolean | – | – |
| max_weight | integer | – | – |
| space_height | integer | – | – |
| space_length | integer | – | – |
| space_width | integer | – | – |
| to_bottom | boolean | – | – |
| to_front | boolean | – | – |
| to_left | boolean | – | – |
No output schema declared.
No examples provided.
send_feedback ~162
Send a question, suggestion, or bug report about this container-loading tool to the Zhihuo maintainers. Use this when the user wants to ask the tool's authors a question, suggest an improvement (e.g. another container type or output field), or report a result that looks wrong. The note reaches the Zhihuo team. Args: message: The question, suggestion, or bug report, in plain text. contact: Optional email or handle if the user would like a reply. category: Optional tag - "question", "suggestion", "bug", or "other". Returns a short confirmation string.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| contact | string | – | – |
| message | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Zhihuo Container Loading MCP server?
Zhihuo Container Loading is a hosted endpoint at https://mcp.zhihuo.net/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.zhihuo.net
claude mcp add --transport http net-zhihuo-mcp-container-loading 'https://mcp.zhihuo.net/mcp'
What is the Zhihuo Container Loading MCP server?
Zhihuo Container Loading is an MCP server listed in the public MCP registry as net.zhihuo.mcp/container-loading. How many identical cartons fit in a container or space, where they go, plus a 3D loading plan. This page covers its hosted endpoint (https://mcp.zhihuo.net/mcp).
Is the Zhihuo Container Loading MCP server safe to use?
Zhihuo Container Loading scores 79 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 Zhihuo Container Loading MCP server expose?
Zhihuo Container Loading exposes 2 tools: pack_boxes, send_feedback. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.
Does the Zhihuo Container Loading MCP server require authentication?
No. We connected to Zhihuo Container Loading without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zhihuo Container Loading MCP server still maintained?
Zhihuo Container Loading is marked deprecated in the MCP registry. We last reached this channel on 21 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 Zhihuo Container Loading MCP server?
VerifyMCP ran 13 checks on Zhihuo Container Loading, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.