maritime

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

使うべきか

品質と安全性

B
説明の品質
92%
スキーマの完全性
69%
命名の品質
80%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

検出事項(2)

  • LOWTool 'shipping_vessel_types' description lacks action verbshipping_vessel_types 内
  • LOWTool 'shipping_chokepoint' description lacks action verbshipping_chokepoint 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,350トークン数(ツール定義)
~536 B一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 1.05%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "maritime": {
      "url": "https://ship.rootz.global/mcp"
    }
  }
}

リモートエンドポイント

https://ship.rootz.global/mcpstreamable-http

できること

ツール一覧

ツール(13)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢shipping_oil_trade(query, reporter, partner, product, period, ...)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text: a country name or keyword"
    },
    "reporter": {
      "type": "string"
    },
    "partner": {
      "type": "string"
    },
    "product": {
      "type": "string"
    },
    "period": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 50
    }
  }
}
🟢shipping_sanctions(query, type)

Check vessel/entity against OFAC sanctions

入力スキーマ

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string"
    },
    "type": {
      "type": "string",
      "enum": [
        "vessel",
        "company",
        "individual",
        "all"
      ]
    }
  },
  "required": [
    "query"
  ]
}
🟢shipping_fleet(query, company, vessel_type, search, limit)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text: vessel name, IMO, owner company, or type"
    },
    "company": {
      "type": "string"
    },
    "vessel_type": {
      "type": "string"
    },
    "search": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 50
    }
  }
}
🟢shipping_oil_prices(benchmark, days)

Get oil price benchmarks (WTI, Brent)

入力スキーマ

{
  "type": "object",
  "properties": {
    "benchmark": {
      "type": "string",
      "default": "all"
    },
    "days": {
      "type": "integer",
      "default": 30
    }
  }
}
⚪shipping_status

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.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
⚪shipping_freshness

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.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
🟢shipping_top_exporters(product, query, limit)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "product": {
      "type": "string",
      "default": "crude"
    },
    "query": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 20
    }
  }
}
⚪shipping_country_flows(country, query, direction, limit)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "country": {
      "type": "string"
    },
    "query": {
      "type": "string",
      "description": "Alias for country"
    },
    "direction": {
      "type": "string",
      "default": "exports"
    },
    "limit": {
      "type": "integer",
      "default": 30
    }
  }
}
⚪shipping_vessel_types

Fleet breakdown by vessel type

入力スキーマ

{
  "type": "object",
  "properties": {}
}
🟢shipping_emissions(query, imo, ship_type, year, limit)

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

入力スキーマ

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

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Program (e.g. \"Iran\"), flag state, or vessel name"
    },
    "year": {
      "type": "string",
      "description": "Filter by year (2018-2024)"
    },
    "limit": {
      "type": "integer",
      "default": 50
    }
  }
}
⚪shipping_chokepoint(chokepoint, query)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "chokepoint": {
      "type": "string",
      "description": "\"Hormuz\", \"Suez\", \"Malacca\", or \"Bab el-Mandeb\""
    },
    "query": {
      "type": "string",
      "description": "Alias for chokepoint (free text)"
    }
  }
}
🟢shipping_doc_intel(topic)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "description": "Topic: \"platforms\", \"mletr\", \"fraud\", \"standards\", \"stats\", or \"overview\"",
      "enum": [
        "platforms",
        "mletr",
        "fraud",
        "standards",
        "stats",
        "overview"
      ]
    }
  },
  "required": [
    "topic"
  ]
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 13 件
検証済みバージョンは記録されていませんツール 13 件
検証済みバージョンは記録されていませんツール 13 件