Analytics

straits.live

Provides comprehensive intelligence and analytics on vessel activity, sanctions, and risk in the Strait of Hormuz.

x402 supported1 endpoint10 known toolsFirst detected July 20, 2026Last detected August 29, 2026

ENDPOINT 1

https://straits.live/api/mcp

No auth detected

MCP server metadata

Name: straits-live
Version: 1.0.0

Capabilities

tools.listChanged

Known tools 10

hormuz_vessels

Strait of Hormuz per-vessel intelligence: the live-AIS vessel manifest (MMSI-keyed, flag from the MMSI MID), OFAC-sanctioned vessels currently in the Persian Gulf window, per-vessel risk bands, latest raw AIS positions, the top AIS-dark hulls with the full dark count alongside, and OFAC + UK sanctions reference-list sizes (per-IMO multi-body detail via hormuz_vessel_dossier).

Inferred read-only

hormuz_history

Strait of Hormuz historical series as one contract: hourly stranded-vessel (stranded) and AIS-dark (ais-gaps) counts up to a full year (free tier: 30 days and none), the 5-minute Hormuz Index (index-5min, days 1-30), and daily transit counts (transits, uncapped: always the full retained history, currently 477+ days and growing) enriched with the 7-day moving average, pre-crisis-baseline deviation, and reopening-threshold headroom.

Inferred read-only

hormuz_snapshot

Everything the Strait of Hormuz crisis monitor knows in one call: verdict, oil, transits, insurance, carriers, pipelines, indices, prediction markets, events, full daily brief.

Inferred read-only

hormuz_brief

AI-assisted Strait of Hormuz daily situation brief as structured JSON: prose summary, bullets, and key figures, by date or latest.

Inferred read-only

hormuz_vessel_dossier

Single Strait of Hormuz vessel sanctions + risk dossier by IMO: the unified multi-body sanctions view (US OFAC and the UK/FCDO list, the UK row adding owner/operator, flag, tonnage, ship type, year built, and Date Designated), merged identity, per-vessel risk band, and dark-activity (AIS-gap) record.

Inferred read-only

hormuz_export

Bulk Strait of Hormuz history export: every requested series (index-5min, stranded, ais-gaps, transits) in one call as JSON.

Inferred read-only

hormuz_flags

Strait of Hormuz flag rollup: the flag states of the live-AIS vessel population ranked by vessel count, each with a per-flag sanctioned tally, plus distinct-flag count and sanctioned share.

Inferred read-only

hormuz_risk_screen

Strait of Hormuz shadow-fleet risk screen: the live-AIS vessel population ranked worst-first, each hull with its risk band, the typed reasons behind it (ofac_sdn, ais_dark, foc_tanker, imo_spoofed), and which sanctions bodies list it (US OFAC and/or UK/FCDO).

Inferred read-only

hormuz_bunker

Strait of Hormuz bunker & marine-fuel feed: current VLSFO, IFO380, and MGO prices ($/tonne) for Fujairah (the #2-3 global bunkering hub, just outside the strait and the physical fueling alternative when transit is disrupted), benchmarked against Singapore and Rotterdam, plus the derived Fujairah premium over each hub.

Inferred read-only

hormuz_risk_premium

Strait of Hormuz war-risk transit premium nowcast: a live MODELED war-risk insurance multiple (Nx over the peace baseline, on the standard 1x-16x scale) for moving a tanker through the strait, recomputed every 5 minutes from throughput deviation (IMF PortWatch), the escalation forecast (Polymarket + Kalshi + Manifold + Brent-WTI spread), crude implied volatility (OVX), and event pressure (GDELT + PGSA).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.straits-live]
url = "https://straits.live/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "straits-live": {
      "type": "http",
      "url": "https://straits.live/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: straits-live
Remote MCP URL: https://straits.live/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "straits-live": {
      "url": "https://straits.live/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "straits-live": {
      "type": "http",
      "url": "https://straits.live/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "straits-live",
  "transport": "streamable-http",
  "url": "https://straits.live/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for straits.live was fetched 2026-09-17T11:12:17.192Z.

Trust status Neutral

straits.live is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.