Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Brimload Container Loading

REMOTE · MCP.CUBERITHM.COM

How many identical cartons fit in a container or space, where they go, plus a 3D loading plan.

67 Trust /100

Last scanned (21 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Cloud Infrastructure

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1104 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 Management10
  • Stability observed for 3 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
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
Changelog

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.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Oct 26 66

    First indexed and scored.

Diagnostics

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 22 Oct 2026 · Probed https://mcp.cuberithm.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.cuberithm.com CN=YE1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA384 66e99b1427b4922d8d2becf153c9cd4f867
SANs: mcp.cuberithm.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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.cuberithm.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
cuberithm.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.cuberithm.com/mcp Verified 200
http (plaintext) http://mcp.cuberithm.com/mcp HTTPS enforced 308 https://mcp.cuberithm.com/mcp
MCP tools · 2 exposed · ~845 tokens

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 →

Tool Tokens
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…

NameTypeReqDescription
box_heightintegeryes–
box_lengthintegeryes–
box_weightinteger––
box_widthintegeryes–
containerstring––
countinteger––
include_imageboolean––
max_weightinteger––
space_heightinteger––
space_lengthinteger––
space_widthinteger––
to_bottomboolean––
to_frontboolean––
to_leftboolean––

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.

NameTypeReqDescription
categorystring––
contactstring––
messagestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the Brimload Container Loading MCP server?

Brimload Container Loading is a hosted endpoint at https://mcp.cuberithm.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.cuberithm.com

# add to Claude Code
claude mcp add --transport http com-cuberithm-mcp-container-loading 'https://mcp.cuberithm.com/mcp'
Common questions

What is the Brimload Container Loading MCP server?

Brimload Container Loading is an MCP server listed in the public MCP registry as com.cuberithm.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.cuberithm.com/mcp).

Is the Brimload Container Loading MCP server safe to use?

Brimload Container Loading scores 67 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 Brimload Container Loading MCP server expose?

Brimload 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 Brimload Container Loading MCP server require authentication?

No. We connected to Brimload Container Loading without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Brimload Container Loading MCP server still maintained?

Brimload Container Loading is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.