global.rootz.ship/maritime

REMOTE · SHIP.ROOTZ.GLOBAL · SCANNED AUG 3

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

Available components

+5 this week 60 60 Trust /100

Trust breakdown (6 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 →

Endpoint Security60

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability64

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 946 tokens (~78/item across 12 items; 12 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage79

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
36% of tool parameters carry a description.Partial

Capabilities20

Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · ship.rootz.global

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http global-rootz-ship-maritime https://ship.rootz.global/mcp

# ~/.codex/config.toml

[mcp_servers.global-rootz-ship-maritime]
url = "https://ship.rootz.global/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "global-rootz-ship-maritime": {
      "type": "remote",
      "url": "https://ship.rootz.global/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add global-rootz-ship-maritime --url https://ship.rootz.global/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  global-rootz-ship-maritime:
    url: "https://ship.rootz.global/mcp"

// mcp.json

{
  "mcpServers": {
    "global-rootz-ship-maritime": {
      "type": "http",
      "url": "https://ship.rootz.global/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

3 Aug 26 +1

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

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 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.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 54

First indexed and scored.

Show 6 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://ship.rootz.global/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=ship.rootz.global	CN=YE1,O=Let's Encrypt,C=US	29 Jun 2026	27 Sept 2026	ECDSA 256	ECDSA-SHA384	51c753dde868422e6181e74e762bcaec8ca
SANs: ship.rootz.global
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

DNSSEC secure

Validation of ship.rootz.global. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
global.	present	13060	8	Verified
rootz.global.	present	40948, 52524	13, 13	Verified
ship.rootz.global.				Verified address RRset verified with the apex keys

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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://ship.rootz.global/mcp	Verified	200
http (plaintext)	http://ship.rootz.global/mcp	HTTPS enforced	301	https://ship.rootz.global/mcp

MCP tools — 12 exposed · ~946 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.

Tool Tokens

shipping_chokepoint ~146

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".

Input Output Examples

Name	Type	Req	Description
chokepoint	string	—	"Hormuz", "Suez", "Malacca", or "Bab el-Mandeb"
query	string	—	Alias for chokepoint (free text)

No output schema declared.

No examples provided.

shipping_country_flows ~67

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

Input Output Examples

Name	Type	Req	Description
country	string	—	—
direction	string	—	—
limit	integer	—	—
query	string	—	Alias for country

No output schema declared.

No examples provided.

shipping_doc_intel ~99

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.

Input Output Examples

Name	Type	Req	Description
topic	string	yes	Topic: "platforms", "mletr", "fraud", "standards", "stats", or "overview"

No output schema declared.

No examples provided.

shipping_emissions ~141

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).

Input Output Examples

Name	Type	Req	Description
imo	string	—	IMO number (7 digits)
limit	integer	—	—
query	string	—	Free-text: IMO number or ship type/name
ship_type	string	—	Ship type filter (e.g., "Oil tanker", "LNG carrier")
year	string	—	Reporting period year (2018-2024)

No output schema declared.

No examples provided.

shipping_fleet ~86

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

Input Output Examples

Name	Type	Req	Description
company	string	—	—
limit	integer	—	—
query	string	—	Free-text: vessel name, IMO, owner company, or type
search	string	—	—
vessel_type	string	—	—

No output schema declared.

No examples provided.

shipping_oil_prices ~34

Get oil price benchmarks (WTI, Brent)

Input Output Examples

Name	Type	Req	Description
benchmark	string	—	—
days	integer	—	—

No output schema declared.

No examples provided.

shipping_oil_trade ~120

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.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	—
partner	string	—	—
period	string	—	—
product	string	—	—
query	string	—	Free-text: a country name or keyword
reporter	string	—	—

No output schema declared.

No examples provided.

shipping_sanctioned_at_eu ~118

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).

Input Output Examples

Name	Type	Req	Description
limit	integer	—	—
query	string	—	Program (e.g. "Iran"), flag state, or vessel name
year	string	—	Filter by year (2018-2024)

No output schema declared.

No examples provided.

shipping_sanctions ~32

Check vessel/entity against OFAC sanctions

Input Output Examples

Name	Type	Req	Description
query	string	yes	—
type	string	—	—

No output schema declared.

No examples provided.

shipping_status ~14

Database statistics and data freshness

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

shipping_top_exporters ~73

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).

Input Output Examples

Name	Type	Req	Description
limit	integer	—	—
product	string	—	—
query	string	—	—

No output schema declared.

No examples provided.

shipping_vessel_types ~16

Fleet breakdown by vessel type

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	54
27 Jul	55
28 Jul	56
29 Jul	56
30 Jul	56
31 Jul	58
1 Aug	59
2 Aug	59
3 Aug	60