maritime

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

Sollte ich dies verwenden

Qualität und Sicherheit

B
Qualität der Beschreibung
92%
Vollständigkeit des Schemas
69%
Qualität der Benennung
80%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Befunde (2)

  • LOWTool 'shipping_vessel_types' description lacks action verbin shipping_vessel_types
  • LOWTool 'shipping_chokepoint' description lacks action verbin shipping_chokepoint

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~1,350Tokens (Tool-Definitionen)
~536 BTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (1.05% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

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

Remote-Endpunkte

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

Was es kann

Tool-Inventar

Tools (13)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢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.

Eingabe-Schema

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

Eingabe-Schema

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

Eingabe-Schema

{
  "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)

Eingabe-Schema

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

Eingabe-Schema

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

Eingabe-Schema

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

Eingabe-Schema

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

Eingabe-Schema

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

Eingabe-Schema

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

Eingabe-Schema

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

Eingabe-Schema

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

Eingabe-Schema

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

Eingabe-Schema

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

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet13 Tools
verifiziertVersion nicht aufgezeichnet13 Tools
verifiziertVersion nicht aufgezeichnet13 Tools