Zhihuo Container Loading
REMOTE · MCP.ZHIHUO.NET · SCANNED AUG 3
How many identical cartons fit in a container or space, where they go, plus a 3D loading plan.
Available components
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 →
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 1 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 Usability56
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1106 tokens (~553/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.zhihuo.net
claude mcp add --transport http net-zhihuo-mcp-container-loading https://mcp.zhihuo.net/mcp
[mcp_servers.net-zhihuo-mcp-container-loading] url = "https://mcp.zhihuo.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-zhihuo-mcp-container-loading": {
"type": "remote",
"url": "https://mcp.zhihuo.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-zhihuo-mcp-container-loading --url https://mcp.zhihuo.net/mcp --transport streamable-http
mcp_servers:
net-zhihuo-mcp-container-loading:
url: "https://mcp.zhihuo.net/mcp" {
"mcpServers": {
"net-zhihuo-mcp-container-loading": {
"type": "http",
"url": "https://mcp.zhihuo.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 54
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 3 Aug 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 | 13 Jun 2026 | 11 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 51a77d6ec339910d9bca78337513c3c9b64 |
| 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 |
DNSSEC insecure
Validation of mcp.zhihuo.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| zhihuo.net. | 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 |
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.
pack_boxes ~680
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 SmartPacker T 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: Anchor a partial load to the bottom (else the top). 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 embedded i…
| 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.