Aether-X Port Congestion Oracle
REMOTE · AETHERX.AETHER-GRID.IO · 2 COMPONENTS · SCANNED SEP 20
Live port congestion signal, vessel queue, ETA delay and demurrage exposure for 19 ports.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · aetherx.aether-grid.io
claude mcp add --transport http belegante-byte-aetherx-mcp 'https://aetherx.aether-grid.io/mcp'
{
"mcpServers": {
"belegante-byte-aetherx-mcp": {
"url": "https://aetherx.aether-grid.io/mcp"
}
}
} {
"servers": {
"belegante-byte-aetherx-mcp": {
"type": "http",
"url": "https://aetherx.aether-grid.io/mcp"
}
}
} [mcp_servers.belegante-byte-aetherx-mcp] url = "https://aetherx.aether-grid.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"belegante-byte-aetherx-mcp": {
"type": "remote",
"url": "https://aetherx.aether-grid.io/mcp",
"enabled": true
}
}
} openclaw mcp add belegante-byte-aetherx-mcp --url 'https://aetherx.aether-grid.io/mcp' --transport streamable-http
mcp_servers:
belegante-byte-aetherx-mcp:
url: "https://aetherx.aether-grid.io/mcp" {
"McpServers": {
"belegante-byte-aetherx-mcp": {
"Transport": "http",
"Url": "https://aetherx.aether-grid.io/mcp"
}
}
} assistant mcp add belegante-byte-aetherx-mcp -t streamable-http -u 'https://aetherx.aether-grid.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 810 → 1701 ▼ functional
- 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” functional
- 19 Sept 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://aetherx.aether-grid.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aetherx.aether-grid.io | CN=YE1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5ea90f74f26caf86fedf9b4a1c02c778dec |
| SANs: aetherx.aether-grid.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aetherx.aether-grid.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| aether-grid.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aetherx.aether-grid.io/mcp | Verified | 200 | |
| http (plaintext) | http://aetherx.aether-grid.io/mcp | HTTPS enforced | 301 | https://aetherx.aether-grid.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
evaluate_charter_risk ~245
[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).
| Name | Type | Req | Description |
|---|---|---|---|
| commodity | string | – | – |
| demurrage_rate_usd_day | number | – | – |
| expected_laytime_days | number | – | – |
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
evaluate_routing_alternatives ~170
[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".
| Name | Type | Req | Description |
|---|---|---|---|
| commodity | string | – | – |
| port_a | string | yes | – |
| port_b | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_physical_events ~105
[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).
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_port_risk ~196
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).
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_port_state ~105
[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).
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_port_trend ~133
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á).
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_ports_risk ~130
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"].
| Name | Type | Req | Description |
|---|---|---|---|
| port_ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_supported_ports ~70
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}.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
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.