Ship Intelligence MCP
An MCP server providing signed global shipping and commodity data, including sanctions screening, vessel emissions, oil and LNG trade flows, and chokepoint status. It offers tools for querying OFAC/UN sanctions, EU port calls, AIS coverage, and fleet rankings, with cryptographic verification of data integrity.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://ship.rootz.global/mcpWhat its tools do
16 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Not annotated (16)
shipping_oil_tradeshipping_sanctionsshipping_fleetshipping_oil_pricesshipping_statusshipping_freshnessshipping_top_exportersshipping_country_flowsshipping_vessel_typesshipping_emissionsshipping_sanctioned_at_eushipping_chokepointshipping_portshipping_port_callsshipping_port_coverageshipping_doc_intel
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to ship.rootz.global ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Screen vessels and companies against OFAC/UN sanctions lists
- Check live AIS coverage and throughput at major shipping chokepoints
- Retrieve EU MRV CO2 emissions data for specific vessel types or years
- Analyze bilateral oil trade flows and top exporter rankings
Source and maintenance
- Maintenance checked
Protocol and capabilities
- Server
- shipping-intel 0.1.0
- MCP protocol negotiated in check
- 2024-11-05
- Tools
- 16 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {}
}Tools
16 advertised
shipping_oil_trade
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": {
"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"
}
}
}shipping_sanctions
Check vessel/entity against OFAC sanctions
{
"type": "object",
"required": [
"query"
],
"properties": {
"type": {
"enum": [
"vessel",
"company",
"individual",
"all"
],
"type": "string"
},
"query": {
"type": "string"
}
}
}shipping_fleet
Query tanker fleet database. Accepts structured filters OR a free-text `query` (matches vessel name, IMO, owner, or type).
{
"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"
}
}
}shipping_oil_prices
Get oil price benchmarks (WTI, Brent)
{
"type": "object",
"properties": {
"days": {
"type": "integer",
"default": 30
},
"benchmark": {
"type": "string",
"default": "all"
}
}
}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
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": {
"limit": {
"type": "integer",
"default": 20
},
"query": {
"type": "string"
},
"product": {
"type": "string",
"default": "crude"
}
}
}shipping_country_flows
Trade partners for a specific country (who they export to / import from). Pass the country as `country` or `query`.
{
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 30
},
"query": {
"type": "string",
"description": "Alias for country"
},
"country": {
"type": "string"
},
"direction": {
"type": "string",
"default": "exports"
}
}
}shipping_vessel_types
Fleet breakdown by vessel type
{
"type": "object",
"properties": {}
}shipping_emissions
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": {
"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\")"
}
}
}shipping_sanctioned_at_eu
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": {
"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"
}
}
}shipping_chokepoint
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": {
"query": {
"type": "string",
"description": "Alias for chokepoint (free text)"
},
"chokepoint": {
"type": "string",
"description": "\"Hormuz\", \"Suez\", \"Malacca\", or \"Bab el-Mandeb\""
}
}
}shipping_port
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`.
{
"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"
}
}
}shipping_port_calls
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`.
{
"type": "object",
"properties": {
"imo": {
"type": "string"
},
"port": {
"type": "string"
},
"limit": {
"type": "integer",
"default": 50
},
"query": {
"type": "string",
"description": "Port name or 7-digit IMO"
}
}
}shipping_port_coverage
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.
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Alias for country"
},
"country": {
"type": "string",
"description": "Optional ISO-2 or country name filter"
}
}
}shipping_doc_intel
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",
"required": [
"topic"
],
"properties": {
"topic": {
"enum": [
"platforms",
"mletr",
"fraud",
"standards",
"stats",
"overview"
],
"type": "string",
"description": "Topic: \"platforms\", \"mletr\", \"fraud\", \"standards\", \"stats\", or \"overview\""
}
}
}Prompts
Not advertised
Resources
Not advertised
90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-07: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 263 ms
- 95th percentile latency
- 263 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 263 ms · metadata changed · 16 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http ship-intelligence-mcp https://ship.rootz.global/mcpCodex
codex mcp add ship-intelligence-mcp --url https://ship.rootz.global/mcpCursor
{
"mcpServers": {
"ship-intelligence-mcp": {
"url": "https://ship.rootz.global/mcp"
}
}
}Cline
{
"mcpServers": {
"ship-intelligence-mcp": {
"type": "streamableHttp",
"url": "https://ship.rootz.global/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"ship-intelligence-mcp": {
"type": "http",
"url": "https://ship.rootz.global/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http ship-intelligence-mcp https://ship.rootz.global/mcpClaude Desktop
https://ship.rootz.global/mcpWindsurf
{
"mcpServers": {
"ship-intelligence-mcp": {
"serverUrl": "https://ship.rootz.global/mcp"
}
}
}Let your agent find its tools
Find servers like Ship Intelligence MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other data and analytics servers
Do you run Ship Intelligence MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.