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

shipping-intel

https://ship.rootz.global

Registry code: b49ae35fe08f33fd

api record

Signed global shipping & commodity data: oil, LNG, grain, sanctions, fleet, emissions.

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

endpoint
https://ship.rootz.global/mcp
protocol
streamable-http ·2024-11-05
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 shipping-intel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is shipping-intel free to use?
Yes — the hub reached it with no key and no payment.
What tools does shipping-intel have?
16 tools: shipping_top_exporters, shipping_port_coverage, shipping_oil_prices, shipping_fleet, shipping_oil_trade, shipping_sanctions, shipping_freshness, shipping_country_flows, ….
Is shipping-intel 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.5%

90 days 98.5%· all time 98.5%

latency
308ms

last good check

priced tools
0

of 16 tools

_ answered our checks, 90 days 401 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
maps travel & places logistics & shipping
used for
  • get maritime chokepoint intelligence
  • query tanker fleet database
  • check vessel against ofac sanctions
  • get oil trade flows by country
  • get vessel emissions data
takes → gives
text, data → data
tools
13 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 16 tools
1 open 15 never probed 1 of 16 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.

  • shipping_status reads open 15h ago

    Database statistics plus per-dataset freshness: how recently each dataset was refreshed by our pipeline, how old its newest record is, and whether it is ok / lagging / stale / empty. Call this to decide how much to trust anything else this server returns.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • shipping_top_exporters reads unknown never probed

    Top oil exporting countries by value/volume (a ranking — no query needed). Optional `product` or `query` recognizes a product keyword (crude/refined/lng/coal/iron_ore).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20
    },
    "query": {
      "type": "string"
    },
    "product": {
      "type": "string",
      "default": "crude"
    }
  }
}
    arguments 16 lines
  • shipping_port_coverage unknown never probed

    Coverage ledger across all 2,951 ports: how many we hold at each evidence grade, how many publish a machine-readable movement board, and what happened when we checked those that do not. Call this to find out what this service does NOT know about ports before relying on what it does.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Alias for country"
    },
    "country": {
      "type": "string",
      "description": "Optional ISO-2 or country name filter"
    }
  }
}
    arguments 13 lines
  • shipping_oil_prices reads unknown never probed

    Get oil price benchmarks (WTI, Brent)

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "default": 30
    },
    "benchmark": {
      "type": "string",
      "default": "all"
    }
  }
}
    arguments 13 lines
  • shipping_fleet reads unknown never probed

    Query tanker fleet database. Accepts structured filters OR a free-text `query` (matches vessel name, IMO, owner, or type).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50
    },
    "query": {
      "type": "string",
      "description": "Free-text: vessel name, IMO, owner company, or type"
    },
    "search": {
      "type": "string"
    },
    "company": {
      "type": "string"
    },
    "vessel_type": {
      "type": "string"
    }
  }
}
    arguments 22 lines
  • shipping_oil_trade reads unknown never probed

    Query bilateral oil trade flows (EIA US imports/exports + Eurostat). Accepts structured filters OR a free-text `query` (matches country/notes). NOTE: this is import/export flow data, NOT chokepoint throughput — for Hormuz transit volumes use shipping_chokepoint.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50
    },
    "query": {
      "type": "string",
      "description": "Free-text: a country name or keyword"
    },
    "period": {
      "type": "string"
    },
    "partner": {
      "type": "string"
    },
    "product": {
      "type": "string"
    },
    "reporter": {
      "type": "string"
    }
  }
}
    arguments 25 lines
  • shipping_sanctions reads unknown never probed

    Check vessel/entity against OFAC sanctions

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "type": {
      "enum": [
        "vessel",
        "company",
        "individual",
        "all"
      ],
      "type": "string"
    },
    "query": {
      "type": "string"
    }
  }
}
    arguments 20 lines
  • shipping_freshness reads unknown never probed

    Per-dataset freshness only: pipeline refresh age vs expected cadence, newest record age, source, and status (ok / lagging / stale / empty / unknown). Use before relying on a figure that must be current.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • shipping_country_flows reads unknown never probed

    Trade partners for a specific country (who they export to / import from). Pass the country as `country` or `query`.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 30
    },
    "query": {
      "type": "string",
      "description": "Alias for country"
    },
    "country": {
      "type": "string"
    },
    "direction": {
      "type": "string",
      "default": "exports"
    }
  }
}
    arguments 20 lines
  • shipping_vessel_types reads unknown never probed

    Fleet breakdown by vessel type

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • shipping_emissions reads unknown never probed

    Query EU MRV vessel emissions data — CO2, fuel consumption, time at sea for 22,543 vessels (2018-2024). Search by IMO, ship type, or year — or a free-text `query` (7-digit = IMO, else ship type/name).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "imo": {
      "type": "string",
      "description": "IMO number (7 digits)"
    },
    "year": {
      "type": "string",
      "description": "Reporting period year (2018-2024)"
    },
    "limit": {
      "type": "integer",
      "default": 50
    },
    "query": {
      "type": "string",
      "description": "Free-text: IMO number or ship type/name"
    },
    "ship_type": {
      "type": "string",
      "description": "Ship type filter (e.g., \"Oil tanker\", \"LNG carrier\")"
    }
  }
}
    arguments 25 lines
  • shipping_sanctioned_at_eu reads unknown never probed

    Find sanctioned vessels that called at EU/EEA ports. Cross-references OFAC sanctions with EU MRV emissions data (verifiable IMO-level identity). Filter by year or a free-text `query` (sanctions program e.g. "Iran"/"Russia", flag, or vessel name).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "year": {
      "type": "string",
      "description": "Filter by year (2018-2024)"
    },
    "limit": {
      "type": "integer",
      "default": 50
    },
    "query": {
      "type": "string",
      "description": "Program (e.g. \"Iran\"), flag state, or vessel name"
    }
  }
}
    arguments 17 lines
  • shipping_chokepoint reads unknown never probed

    Maritime chokepoint intelligence for Hormuz, Suez, Malacca, or Bab el-Mandeb. Returns authoritative EIA baseline throughput (barrels/day, % of global), a live AIS snapshot (vessels/tankers/moving/stationary) for the chokepoint, sanctioned vessels currently detected there, and dark-fleet behavioural signals (loitering + AIS gaps). This is the tool for "how is Hormuz doing".

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Alias for chokepoint (free text)"
    },
    "chokepoint": {
      "type": "string",
      "description": "\"Hormuz\", \"Suez\", \"Malacca\", or \"Bab el-Mandeb\""
    }
  }
}
    arguments 13 lines
  • shipping_port unknown never probed

    What this service holds about ONE port, and how good the evidence is. Returns NGA World Port Index identity (UN/LOCODE, coordinates, harbour class, channel/anchorage/pier depths), the evidence grade for our movement data (origin = the authority publishes its own board / custody = a third party publishes it / measured = AIS inference only, asserted by nobody / none), what we do NOT hold, and what happened the last time we fetched the port's own website. Pass a port name, UN/LOCODE, or WPI port number as `query`.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "port": {
      "type": "string",
      "description": "Alias for query"
    },
    "query": {
      "type": "string",
      "description": "Port name, UN/LOCODE (e.g. NZTRG), or WPI port number"
    },
    "unlocode": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • shipping_port_calls unknown never probed

    Berth-level vessel movements harvested from port authority movement boards: vessel, IMO, arrival/departure, berth, agent, declared last/next port. Each row carries its source and whether the channel was TLS-verified. This is TESTIMONY from the port, distinct from the AIS-inferred port_visits behind other tools. Pass a port name or an IMO as `query`.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "imo": {
      "type": "string"
    },
    "port": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 50
    },
    "query": {
      "type": "string",
      "description": "Port name or 7-digit IMO"
    }
  }
}
    arguments 19 lines
  • shipping_doc_intel reads unknown never probed

    Query the shipping document intelligence layer: eBL platform adoption (12 platforms), MLETR country adoption (23 countries, 13 enacted), document fraud cases ($11.3B), DCSA standards (10), industry stats (26 metrics). The state of shipping document digitization.

    mcp-tool

    {
  "type": "object",
  "required": [
    "topic"
  ],
  "properties": {
    "topic": {
      "enum": [
        "platforms",
        "mletr",
        "fraud",
        "standards",
        "stats",
        "overview"
      ],
      "type": "string",
      "description": "Topic: \"platforms\", \"mletr\", \"fraud\", \"standards\", \"stats\", or \"overview\""
    }
  }
}
    arguments 20 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 b49ae35fe08f33fd.

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

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.

_ also on rootz.global 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.