Aether-X Port Delay Intelligence

io.github.belegante-byte由 GitHub 帳號 belegante-byte 發布v0.4.4更新於 Oct 24, 2026

Port delay exposure with p50/p90 confidence intervals, demurrage impact and a free public feed.

發布方自己的服務：Port

已驗證Streamable HTTP可網頁執行資料與分析商業與電商

服務詳細資訊

識別碼: io.github.belegante-byte/aetherx-mcp
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 18, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 belegante-byte。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.belegante-byte%2Faetherx-mcp.svg)](https://sourceweft.com/mcp/io.github.belegante-byte%2Faetherx-mcp?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

Aether-X Port Delay Intelligence 是一個 MCP 伺服器，讓助理取得全球港口與咽喉點的壅塞、船舶排隊與延誤風險訊號。

可以做什麼: 依 UN/LOCODE 查詢單一港口的白話營運狀態（正常或壅塞）、延誤天數與等待船舶數，結果附資料來源與時間戳。取得單一港口或整組港口的壅塞分數、預計到港延誤、運價波動指數與每日延滯費估算，組合查詢可平行取得。取得 24/48/72 小時壅塞預測與趨勢標籤。列出支援的 35 個港口與咽喉點。
適用情境: 適合助理回答某港口目前是否延誤、有多少船舶在等待，或比較多個港口的壅塞風險與延滯費曝險。適用於物流、航運與供應鏈分析，而非一般網頁查詢。
執行需求: 可作為遠端端點使用，也可透過 PyPI 套件 aetherx-mcp 在本機執行（例如用 uvx），本機執行需要 Python 工具鏈。可選設定 RAPIDAPI_KEY 以經 RapidAPI 閘道轉送請求；未設定時直接呼叫公開正式環境 API。可用 RAPIDAPI_HOST 與 AETHERX_BASE_URL 覆寫端點。需要網路存取。

安裝前請注意

僅巴西港口（桑托斯、巴拉那瓜、里約熱內盧、尼泰羅伊、伊塔瓜伊）使用即時排隊資料；其他港口回傳靜態參考種子資料，並非即時現場資料，24/48/72 小時趨勢為合成推估而非即時預測。設定 RAPIDAPI_KEY 會經計量計費的閘道轉送請求。README 中部分範例提示引用了工具表中未記錄的工具與 M2M 金鑰。

安裝

在 SourceWeft 中

開啟儀表板中的 Aether-X Port Delay Intelligence，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.belegante-byte%2Faetherx-mcp/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "aether-x-port-delay-intelligence": {
      "type": "http",
      "url": "https://aetherx.aether-grid.io/mcp"
    }
  }
}

README

aetherx-mcp — Port Congestion, Maritime Logistics & Supply Chain MCP Server

Aether-X is an MCP server for the Aether-X Port Congestion Oracle that gives any MCP-compatible agent (Claude Desktop, Cursor, VS Code, custom LLM agents) port congestion, maritime delay, vessel queue and supply-chain risk signals for global trade — answered in plain language for simple queries ("is Rotterdam delayed?") and in USD exposure for decision-grade workflows (demurrage, charter risk, fiscal arbitrage across routes).

Keywords: maritime, shipping, vessels, ports, port congestion, demurrage, freight, logistics, supply chain, ETA delay, vessel queue, chokepoints, Suez, Panama, trade lanes, cargo, quantitative finance.

DATA INTEGRITY NOTICE: Brazilian ports (BRSSZ Santos, BRPNG Paranaguá, BRRIO Rio de Janeiro) feed live operational line-ups (data_source="live:appa+santos+lachmann"); Niterói (BRNIT) and Itaguaí (BRITG) together with Rio de Janeiro feed live line-up from SILOG PortosRio (data_source="live:portosrio_silog"). The remaining ports serve a static reference seed (data_source="static_reference_seed"). Every tool result includes data_source and as_of. The 24/48/72h trend is a synthetic projection, not a live forecast. Seed values are NOT real-time field data.

Install

Configure your MCP client

Claude Desktop (`claude_desktop_config.json`)

json

{  "mcpServers": {    "aetherx-oracle": {      "command": "uvx",      "args": ["aetherx-mcp"],      "env": { "RAPIDAPI_KEY": "SUA_RAPIDAPI_KEY" }    }  }}

{  "mcpServers": {    "aetherx-oracle": {      "command": "uvx",      "args": ["aetherx-mcp"],      "env": { "RAPIDAPI_KEY": "SUA_RAPIDAPI_KEY" }    }  }}

Cursor (`~/.cursor/mcp.json`)

json

{  "mcpServers": {    "aetherx-oracle": {      "command": "uvx",      "args": ["aetherx-mcp"],      "env": { "RAPIDAPI_KEY": "SUA_RAPIDAPI_KEY" }    }  }}

{  "mcpServers": {    "aetherx-oracle": {      "command": "uvx",      "args": ["aetherx-mcp"],      "env": { "RAPIDAPI_KEY": "SUA_RAPIDAPI_KEY" }    }  }}

Tools

Tool	Arguments	Returns
`get_port_operations_status`	`port_id` (UN/LOCODE)	Plain-language status (NORMAL / CONGESTED), delay, waiting vessels, source provenance + optional decision-layer upsell — free observation
`get_port_risk`	`port_id` (UN/LOCODE)	Congestion score, ETA delay, waiting vessels, freight volatility, daily demurrage estimate
`get_ports_risk`	`port_ids` (list)	Same, for a whole portfolio, fetched in parallel
`get_port_trend`	`port_id` (UN/LOCODE)	24h / 48h / 72h congestion projection + trend label (acelerando / estável / descongestionando)
`list_supported_ports`	—	The 35 ports & chokepoints (id, name, country)

Every response is a typed payload:

json

{  "port_id": "BRSSZ",  "port_name": "Santos",  "country": "Brasil",  "congestion_score": 0.78,  "eta_delay_days": 1.6,  "waiting_vessels": 12,  "freight_volatility_index": 0.42,  "estimated_daily_demurrage_usd": 63200,  "updated_at": "2026-09-17 15:46:53"}

{  "port_id": "BRSSZ",  "port_name": "Santos",  "country": "Brasil",  "congestion_score": 0.78,  "eta_delay_days": 1.6,  "waiting_vessels": 12,  "freight_volatility_index": 0.42,  "estimated_daily_demurrage_usd": 63200,  "updated_at": "2026-09-17 15:46:53"}

Configuration

Variable	Default	Description
`RAPIDAPI_KEY`	—	When set, requests are routed through the RapidAPI gateway (metered billing)
`RAPIDAPI_HOST`	`aether-x-port-congestion-oracle.p.rapidapi.com`	RapidAPI host
`AETHERX_BASE_URL`	`https://aetherx.aether-grid.io`	Direct API base URL

Without RAPIDAPI_KEY, the server calls the public production API directly.

Example agent prompts

"Is the port of Santos delayed right now?" (→ get_port_operations_status)
"Where is my cargo stuck? What's the waiting time at Paranaguá?" (→ get_port_operations_status)
"What's the congestion risk at Rotterdam over the next 3 days?" (→ get_port_trend, forecast_vessel_queue_delays)
"Rank these ports by congestion: BRSSZ, CNSHA, NLRTM, USLAX." (→ get_ports_risk)
"How many ships are waiting at Shanghai?" (→ get_port_state, get_port_operations_status)
"Which route minimizes demurrage + fiscal cost for my fertilizer cargo to MT?" (→ evaluate_fiscal_routing, requires M2M key)