_ registry / mcp http-sse · checked 2h ago

hansatic

https://hansatic.com

Registry code: 2d4aa2fa9fa928f2

api record

MCP server for the Hansatic packing API — truck & container load optimization for AI agents. Returns physically valid layouts with LDM, linear feet and pallet positions.

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

endpoint
https://hansatic.com/mcp
protocol
http-sse ·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 hansatic live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is hansatic free to use?
Yes — the hub reached it with no key and no payment.
What tools does hansatic have?
3 tools: pack_cargo, check_job, list_vehicles.
Is hansatic 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
98.1%

90 days 98.1%· all time 98.1%

latency
410ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 317 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • optimize cargo loading in a truck or container
  • list trucks and containers with dimensions
  • check a packing job status
takes → gives
text → data
tools
3 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 3 tools
1 open 2 never probed 1 of 3 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.

  • list_vehicles reads open 24h ago

    List all available trucks, trailers and shipping containers with their interior dimensions (mm) and max payload (kg). Use the returned codes as the "vehicle" argument of pack_cargo.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • pack_cargo reads unknown never probed

    Optimize how cargo is loaded into a truck, trailer or shipping container. Returns a physically valid layout (placements with x/y/z and rotation, respecting stacking, fragility, weight and axle constraints) plus the freight billing metrics: LDM (loading meters), linear feet, EUR pallet positions and total weight. Submits an async job and waits for the result — typically 5-30 seconds. Use list_vehicles first if you are unsure of the vehicle code.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vehicle",
        "items"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Plan name (production mode)"
        },
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "length",
              "width",
              "height",
              "weight"
            ],
            "properties": {
              "name": {
                "type": "string",
                "description": "Label shown in the plan"
              },
              "width": {
                "type": "number",
                "description": "Width",
                "exclusiveMinimum": 0
              },
              "height": {
                "type": "number",
                "description": "Height",
                "exclusiveMinimum": 0
              },
              "length": {
                "type": "number",
                "description": "Length (mm by default, inches when units=imperial)",
                "exclusiveMinimum": 0
              },
              "weight": {
                "type": "number",
                "minimum": 0,
                "description": "Weight (kg by default, lb when units=imperial)"
              },
              "fragile": {
                "type": "boolean",
                "description": "Fragile items go on top layers only (default false)"
              },
              "quantity": {
                "type": "integer",
                "maximum": 9007199254740991,
                "minimum": 1,
                "description": "How many identical units (default 1)"
              },
              "tiltable": {
                "type": "boolean",
                "description": "May the item be laid on its side (default true)"
              },
              "max_stack": {
                "type": "number",
                "description": "Max weight this item can bear on top"
              },
              "stackable": {
                "type": "boolean",
                "description": "May other cargo rest on top (default true)"
              },
              "destination_stop": {
                "type": "integer",
                "maximum": 9007199254740991,
                "minimum": 1,
                "description": "Delivery stop for multi-stop LIFO loading (default 1)"
              }
            }
          },
          "minItems": 1,
          "description": "The cargo manifest"
        },
        "units": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "description": "How item numbers are read AND returned: mm/kg (default) or in/lb"
        },
        "sandbox": {
          "type": "boolean",
          "description": "Force sandbox mode (nothing persisted). Omit to let the account tier decide: enterprise accounts create a real plan with a shareable link, others sandbox automatically."
        },
        "vehicle": {
          "type": "string",
          "description": "Vehicle code, e.g. CURTAINSIDER_136 (13.6m curtainsider) or 40HC (40ft high-cube container). Get valid codes from list_vehicles."
        },
        "objective": {
          "enum": [
            "ldm",
            "pallets"
          ],
          "type": "string",
          "description": "Minimize loading meters (default) or billed pallet positions"
        },
        "ldm_limit_m": {
          "type": "number",
          "description": "Restrict the load to the first N loading meters (trucks)"
        }
      }
    }
    arguments 110 lines
  • check_job reads unknown 24h ago

    Check the status/result of a packing job by id (only needed if pack_cargo timed out on a very large manifest).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string",
          "description": "The job id returned by pack_cargo"
        }
      }
    }
    arguments 13 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 2d4aa2fa9fa928f2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2d4aa2fa9fa928f2/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/2d4aa2fa9fa928f2/badge.svg)](https://brick.blue/agent/2d4aa2fa9fa928f2?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
70%

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.