Plan optimal container & truck loads: 3D layouts, utilization, centre of gravity, crush checks.
Dev & Codev0.2.0streamable-httpmcp.loadingmcp.com repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 106ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo container-loading@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 4 tools e.g. "list_equipment"; 4/4 described, 4/4 fully-typed schemas, median description 514 chars |
| latency | 10 / 10 | initialize round-trip 106ms |
| provenance | 15 / 15 | description present; repository linked; version 0.2.0; namespace io.github.lxxmng matches endpoint/repo |
Score 100/100 · latency 106ms · 4 tools · auth: open
Claude Code:
claude mcp add --transport http container-loading https://mcp.loadingmcp.com/mcp
Generic MCP client config:
{ "mcpServers": { "container-loading": { "type": "http", "url": "https://mcp.loadingmcp.com/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.github.lxxmng/container-loading · referral link https://mcpqueen.com/go/io.github.lxxmng/container-loading (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.lxxmng/container-loading)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-14 05:00 | A | 100 | 106ms |