# Aether-X Port Congestion Oracle (remote · aetherx.aether-grid.io)

Live port congestion signal, vessel queue, ETA delay and demurrage exposure for 19 ports.

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `aetherx.aether-grid.io`: 60/100 (this document), [markdown](https://verifymcp.io/servers/belegante-byte-aetherx-mcp/aetherx.md), [page](https://verifymcp.io/servers/belegante-byte-aetherx-mcp/aetherx)
- pypi · `aetherx-mcp`: 68/100, [markdown](https://verifymcp.io/servers/belegante-byte-aetherx-mcp/aetherx-mcp.md), [page](https://verifymcp.io/servers/belegante-byte-aetherx-mcp/aetherx-mcp)

## Channel facts

- Endpoint: `https://aetherx.aether-grid.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1701 tokens (~212/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Aether-X Port Congestion Oracle MCP server?

Aether-X Port Congestion Oracle is a hosted endpoint at https://aetherx.aether-grid.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http belegante-byte-aetherx-mcp 'https://aetherx.aether-grid.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "belegante-byte-aetherx-mcp": {
      "url": "https://aetherx.aether-grid.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "belegante-byte-aetherx-mcp": {
      "type": "http",
      "url": "https://aetherx.aether-grid.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.belegante-byte-aetherx-mcp]
url = "https://aetherx.aether-grid.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "belegante-byte-aetherx-mcp": {
      "type": "remote",
      "url": "https://aetherx.aether-grid.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add belegante-byte-aetherx-mcp --url 'https://aetherx.aether-grid.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  belegante-byte-aetherx-mcp:
    url: "https://aetherx.aether-grid.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "belegante-byte-aetherx-mcp": {
      "Transport": "http",
      "Url": "https://aetherx.aether-grid.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add belegante-byte-aetherx-mcp -t streamable-http -u 'https://aetherx.aether-grid.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "belegante-byte-aetherx-mcp": {
      "type": "http",
      "url": "https://aetherx.aether-grid.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 60, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 810 → 1701
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.2.1 → 1.1.0
- [functional] New tool “evaluate_charter_risk”
- [functional] New tool “evaluate_routing_alternatives”
- [functional] New tool “get_physical_events”
- [functional] New tool “get_port_state”

### 2026-09-19 (score 60)

First indexed and scored.

## MCP tools (8)

### `get_port_risk` (~196 tokens)

Assess CURRENT congestion and delay risk at a single seaport.

    Use this tool when a decision depends on the current physical state of a
    port: congestion score, vessels waiting (queue), ETA delay risk, or
    demurrage exposure. Call BEFORE making recommendations involving port
    selection, cargo routing, vessel scheduling, ETA risk, demurrage exposure,
    freight timing, or supply-chain disruption.

    Returns a live operational signal (not a static port-information lookup)
    with congestion score, real observed vessel state, estimated delay,
    expected/worst-case demurrage (USD), confidence, source provenance and
    validation window.

    Args:
        port_id: UN/LOCODE of the port, e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá), "CNSHA" (Shanghai).

Input parameters:

- `port_id` (string, required)

### `get_ports_risk` (~130 tokens)

Compare CURRENT congestion across several seaports in a single call.

    Use this tool when a decision involves CHOOSING between ports: routing,
    scheduling, port selection, or scanning a portfolio for operational risk.
    Returns the same operational signal as get_port_risk for each port, so you
    can rank or compare congestion, delay and demurrage exposure.

    Args:
        port_ids: list of UN/LOCODEs to compare, e.g. ["BRSSZ", "BRPNG", "CNSHA"].

Input parameters:

- `port_ids` (array, required)

Output parameters:

- `result` (array)

### `get_port_trend` (~133 tokens)

Get the short-horizon 24/48/72h congestion projection for a port.

    Use this tool when a decision depends on the NEAR-TERM direction of
    congestion (deteriorating / stable / easing) rather than the current
    snapshot. Complements get_port_risk. This is a SYNTHETIC projection,
    not a live forecast.

    Args:
        port_id: UN/LOCODE of the port, e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá).

Input parameters:

- `port_id` (string, required)

### `list_supported_ports` (~70 tokens)

List the 19 ports covered by the oracle (UN/LOCODE id, name, country).

    Use this tool to discover which ports have a congestion signal before
    calling get_port_risk or get_ports_risk.

    Returns: list of {port_id, port_name, country}.

Output parameters:

- `result` (array)

### `get_port_state` (~105 tokens)

[OBSERVATION TOOL] Return current verified multimodal physical state of a port.

    Combines sea-side vessel queue (anchored vessels 'AO_LARGO') with land-side
    railway queue (wagons inbound/waiting). Returns sources for full provenance.

    Args:
        port_id: UN/LOCODE e.g. "BRPNG" (Paranaguá), "BRSSZ" (Santos).

Input parameters:

- `port_id` (string, required)

### `get_physical_events` (~105 tokens)

[OBSERVATION TOOL] Return temporal physical events for a port as a ChangePacket (physical-event.v1).

    Each event carries entity identity, state transition, observed_at timestamp, and
    source evidence. Use this tool to understand WHAT changed and WHEN.

    Args:
        port_id: UN/LOCODE e.g. "BRPNG" (Paranaguá), "BRSSZ" (Santos).

Input parameters:

- `port_id` (string, required)

### `evaluate_charter_risk` (~245 tokens)

[DECISION TOOL] Evaluate charter risk and demurrage financial exposure under explicit assumptions.

    Returns a DecisionResult (decision-result.v1) with:
    - exposure.value: estimated exposure in USD
    - exposure.basis: calculation rationale
    - assumptions: all stated premises (demurrage rate, laytime)
    - physical_basis: list of verified physical observations supporting the estimate
    - uncertainties: explicit list of what is NOT known (charter party, actual laytime, cargo quantity)

    Args:
        port_id: UN/LOCODE e.g. "BRPNG" (Paranaguá).
        commodity: Commodity type e.g. "SOJA", "MILHO", "CONTEINERES".
        demurrage_rate_usd_day: Demurrage rate in USD/day (default: 32000).
        expected_laytime_days: Agreed laytime in days (default: 2.0).

Input parameters:

- `commodity` (string)
- `demurrage_rate_usd_day` (number)
- `expected_laytime_days` (number)
- `port_id` (string, required)

### `evaluate_routing_alternatives` (~170 tokens)

[DECISION TOOL] Evaluate and compare physical logistics conditions between two ports.

    Returns a DecisionResult (decision-result.v1) with:
    - comparison.delta_delay_days: estimated delay difference
    - comparison.lower_delay_port: port with lower observed congestion
    - exposure: per-port financial exposure estimates
    - physical_basis: verified physical observations for each port
    - uncertainties: explicit limitations of this comparison

    Args:
        port_a: First port UN/LOCODE e.g. "BRPNG".
        port_b: Second port UN/LOCODE e.g. "BRSSZ".
        commodity: Commodity type e.g. "SOJA".

Input parameters:

- `commodity` (string)
- `port_a` (string, required)
- `port_b` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/belegante-byte-aetherx-mcp/aetherx#diagnostics

## Score history

- 2026-09-20: 60
- 2026-09-19: 60

## Common questions

### What is the Aether-X Port Congestion Oracle MCP server?

Aether-X Port Congestion Oracle is an MCP server listed in the public MCP registry as io.github.belegante-byte/aetherx-mcp. Live port congestion signal, vessel queue, ETA delay and demurrage exposure for 19 ports. This page covers its hosted endpoint (https://aetherx.aether-grid.io/mcp).

### Is the Aether-X Port Congestion Oracle MCP server safe to use?

Aether-X Port Congestion Oracle scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Aether-X Port Congestion Oracle MCP server expose?

Aether-X Port Congestion Oracle exposes 8 tools: get_port_risk, get_ports_risk, get_port_trend, list_supported_ports, get_port_state, and 3 more. Their descriptions and schemas cost roughly 1,154 tokens of context every time the server is loaded.

### Does the Aether-X Port Congestion Oracle MCP server require authentication?

No. We connected to Aether-X Port Congestion Oracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Aether-X Port Congestion Oracle MCP server still maintained?

Aether-X Port Congestion Oracle is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://aetherx.aether-grid.io/mcp
- Repository: https://github.com/belegante-byte/aetherx-oracle-engine
- Website: https://aetherx.aether-grid.io/
- Changelog RSS feed: https://verifymcp.io/servers/belegante-byte-aetherx-mcp/aetherx.xml
- Changelog JSON feed: https://verifymcp.io/servers/belegante-byte-aetherx-mcp/aetherx.json
- HTML version of this page: https://verifymcp.io/servers/belegante-byte-aetherx-mcp/aetherx