_ registry / mcp streamable-http · checked 7h ago

containermath-public

https://mcp.containermath.com

Registry code: 9b371cdc68102057

api record

Calculate shipment volume (CBM/CFT), weight, and how cargo fits standard shipping containers.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.containermath.com
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is containermath-public live?
Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.
Is containermath-public free to use?
Yes — the hub reached it with no key and no payment.
What tools does containermath-public have?
4 tools: calculate_cbm, plan_cargo_load, how_many_pallets_fit, get_container_dimensions.
Is containermath-public safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.1%· all time 99.1%

latency
164ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 566 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • calculate shipment cbm and weight
  • check how many pallets fit a container
  • plan cargo loading
  • get container dimensions
takes → gives
data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_container_dimensions reads open 7h ago

    Interior dimensions, volume, floor area and maximum payload for 47 shipping containers, truck trailers, rail wagons and air ULDs. Use this when someone asks for the internal or interior dimensions, cubic capacity, floor area, payload or weight limit of a container or trailer — 20ft, 40ft, 40ft High Cube, 45ft, reefer, open top, flat rack, 53ft dry van, curtainsider, boxcar, LD-3, PMC and more. Called with no arguments (optionally filtered by mode) it lists the whole catalog with the slug for each vessel.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "mode": {
          "enum": [
            "sea",
            "road",
            "rail",
            "air"
          ],
          "type": "string",
          "description": "When listing, restrict to one transport mode. Ignored when `vessel` is given."
        },
        "vessel": {
          "type": "string",
          "description": "The vessel to look up, as a slug (\"20ft-container\") or plain name (\"20 foot container\", \"40HC\"). Omit to list the catalog instead."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • calculate_cbm reads unknown 16h ago

    Calculate total shipment volume (CBM / cubic metres and CFT / cubic feet), total weight, and how that cargo fits into standard shipping containers (20ft Standard, 40ft Standard, 40ft High Cube). Use this whenever someone asks how much space a shipment takes, how many cubic metres or CBM their boxes / pallets / cartons add up to, whether cargo will fit in a container, what container size they need, or how full a container will be. Accepts a list of items with length, width, height, weight and quantity in metric (cm, kg) or imperial (in, lb) units; returns total CBM, CFT, total weight, and per-container fill percentage with an overload flag.

    mcp-tool

    {
      "type": "object",
      "required": [
        "items"
      ],
      "properties": {
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "length",
              "width",
              "height",
              "quantity"
            ],
            "properties": {
              "name": {
                "type": "string",
                "maxLength": 100,
                "description": "Optional label for the item."
              },
              "width": {
                "type": "number",
                "maximum": 100000,
                "exclusiveMinimum": 0
              },
              "height": {
                "type": "number",
                "maximum": 100000,
                "exclusiveMinimum": 0
              },
              "length": {
                "type": "number",
                "maximum": 100000,
                "exclusiveMinimum": 0
              },
              "weight": {
                "type": "number",
                "default": 0,
                "maximum": 1000000,
                "minimum": 0,
                "description": "Per-unit weight. Optional (defaults to 0)."
              },
              "quantity": {
                "type": "integer",
                "maximum": 1000000,
                "exclusiveMinimum": 0
              }
            },
            "additionalProperties": false
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "The cargo line items to total up."
        },
        "unitSystem": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Units for the item dimensions and weight. 'metric' = centimetres and kilograms; 'imperial' = inches and pounds."
        }
      },
      "additionalProperties": false
    }
    arguments 68 lines
  • plan_cargo_load reads unknown 7h ago

    Plan how one cargo size loads into a shipping container, truck trailer or rail wagon. Use this when someone asks how many of their boxes, cartons, crates or pallets (of a given size, and optionally weight) fit in a 20ft, 40ft, 40ft High Cube, 45ft, 53ft dry van, curtainsider or other vehicle, how many containers or trucks a quantity needs, or whether weight or space limits the load. Returns units per floor layer (mixed orientations), layers by interior height, units per load, whether space or payload binds, loads needed, utilisation, and a link to the same plan drawn on the web. One size per call; for several sizes, call once per size.

    mcp-tool

    {
      "type": "object",
      "required": [
        "vessel",
        "length",
        "width",
        "height"
      ],
      "properties": {
        "width": {
          "type": "number",
          "maximum": 100000,
          "description": "Width of one unit.",
          "exclusiveMinimum": 0
        },
        "height": {
          "type": "number",
          "maximum": 100000,
          "description": "Height of one unit. For a pallet, the loaded height including the deck.",
          "exclusiveMinimum": 0
        },
        "length": {
          "type": "number",
          "maximum": 100000,
          "description": "Length of one unit (carton, crate or loaded pallet).",
          "exclusiveMinimum": 0
        },
        "vessel": {
          "type": "string",
          "description": "The container, truck trailer or rail wagon to load. Accepts a slug (\"40ft-high-cube-container\") or a plain name (\"40HC\", \"20ft\", \"53ft dry van\", \"curtainsider\"). Air ULDs are not supported. Call get_container_dimensions with no arguments for the catalog."
        },
        "weight": {
          "type": "number",
          "default": 0,
          "maximum": 1000000,
          "minimum": 0,
          "description": "Gross weight of one unit. Optional; without it the payload is not checked."
        },
        "quantity": {
          "type": "integer",
          "default": 1,
          "maximum": 1000000,
          "minimum": 1,
          "description": "How many units ship."
        },
        "stackable": {
          "type": "boolean",
          "default": false,
          "description": "Whether units may be stacked on top of each other."
        },
        "unitSystem": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Units for the dimensions and weight. 'metric' = centimetres and kilograms; 'imperial' = inches and pounds."
        },
        "keepUpright": {
          "type": "boolean",
          "default": true,
          "description": "\"This side up\": false lets the unit lie on a side if that fits more."
        }
      },
      "additionalProperties": false
    }
    arguments 67 lines
  • how_many_pallets_fit reads unknown 7h ago

    How many pallets fit in a given shipping container, truck trailer, rail wagon or air ULD. Use this whenever someone asks how many pallets (Euro 1200x800, standard 1200x1000, or US GMA 48x40) fit in a 20ft, 40ft, 40ft High Cube, 45ft, 53ft trailer or any other vessel. Returns the best single-layer floor count with pallets turned to their best orientation — a solved pallet-loading result, not length divided by length, so a 20ft holds 11 Euro pallets and a 40ft holds 25 — plus the double-stacked count with the load height that allows it, and how many the payload allows, which is what decides whether weight or floor space runs out first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "vessel"
      ],
      "properties": {
        "vessel": {
          "type": "string",
          "description": "The container, trailer, rail wagon or air ULD to load. Accepts a slug (\"40ft-high-cube-container\") or a plain name (\"40HC\", \"40' high cube\", \"53ft trailer\"). Call get_container_dimensions with no arguments for the full catalog."
        },
        "palletType": {
          "enum": [
            "euro",
            "standard",
            "gma",
            "all"
          ],
          "type": "string",
          "default": "all",
          "description": "Which pallet: 'euro' (1200x800mm), 'standard' (1200x1000mm), 'gma' (US 48x40in), or 'all' for every size."
        },
        "grossWeightKgPerPallet": {
          "type": "number",
          "default": 700,
          "maximum": 5000,
          "minimum": 1,
          "description": "Gross weight of one LOADED pallet, kg. Only affects the payload-limited count, which is what decides whether weight or floor space binds first."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9b371cdc68102057.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9b371cdc68102057/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9b371cdc68102057/badge.svg)](https://brick.blue/agent/9b371cdc68102057?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.