# global.rootz.ship/maritime (remote · ship.rootz.global)

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

- Trust score: 60/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ship.rootz.global`: 60/100 (this document), [markdown](https://verifymcp.io/servers/global-rootz-ship-maritime/ship.md), [page](https://verifymcp.io/servers/global-rootz-ship-maritime/ship)

## Channel facts

- Endpoint: `https://ship.rootz.global/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 946 tokens (~78/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 36% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

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

### Hermes

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

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 60, +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.

### 2026-08-01 (score 59, +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.

### 2026-07-31 (score 58, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 56, +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.

### 2026-07-27 (score 55, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 54)

First indexed and scored.

## MCP tools (12)

### `shipping_oil_trade` (~120 tokens)

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 parameters:

- `limit` (integer)
- `partner` (string)
- `period` (string)
- `product` (string)
- `query` (string): Free-text: a country name or keyword
- `reporter` (string)

### `shipping_sanctions` (~32 tokens)

Check vessel/entity against OFAC sanctions

Input parameters:

- `query` (string, required)
- `type` (string)

### `shipping_fleet` (~86 tokens)

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

Input parameters:

- `company` (string)
- `limit` (integer)
- `query` (string): Free-text: vessel name, IMO, owner company, or type
- `search` (string)
- `vessel_type` (string)

### `shipping_oil_prices` (~34 tokens)

Get oil price benchmarks (WTI, Brent)

Input parameters:

- `benchmark` (string)
- `days` (integer)

### `shipping_status` (~14 tokens)

Database statistics and data freshness

### `shipping_top_exporters` (~73 tokens)

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 parameters:

- `limit` (integer)
- `product` (string)
- `query` (string)

### `shipping_country_flows` (~67 tokens)

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

Input parameters:

- `country` (string)
- `direction` (string)
- `limit` (integer)
- `query` (string): Alias for country

### `shipping_vessel_types` (~16 tokens)

Fleet breakdown by vessel type

### `shipping_emissions` (~141 tokens)

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 parameters:

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

### `shipping_sanctioned_at_eu` (~118 tokens)

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 parameters:

- `limit` (integer)
- `query` (string): Program (e.g. "Iran"), flag state, or vessel name
- `year` (string): Filter by year (2018-2024)

### `shipping_chokepoint` (~146 tokens)

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 parameters:

- `chokepoint` (string): "Hormuz", "Suez", "Malacca", or "Bab el-Mandeb"
- `query` (string): Alias for chokepoint (free text)

### `shipping_doc_intel` (~99 tokens)

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 parameters:

- `topic` (string, required): Topic: "platforms", "mletr", "fraud", "standards", "stats", or "overview"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/global-rootz-ship-maritime/ship#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 59
- 2026-08-01: 59
- 2026-07-31: 58
- 2026-07-30: 56
- 2026-07-29: 56
- 2026-07-28: 56
- 2026-07-27: 55
- 2026-07-26: 54

## Links

- Remote endpoint: https://ship.rootz.global/mcp
- Repository: https://github.com/rootz-global/mcp-servers
- Website: https://ship.rootz.global/
- Changelog RSS feed: https://verifymcp.io/servers/global-rootz-ship-maritime/ship/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/global-rootz-ship-maritime/ship/changelog.json
- HTML version of this page: https://verifymcp.io/servers/global-rootz-ship-maritime/ship