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)