Aether-X Port Delay Intelligence
REMOTE · AETHERX.AETHER-GRID.IO · 2 COMPONENTS
Port delay exposure with p50/p90 confidence intervals, demurrage impact and a free public feed.
Available components
Last scanned (12 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 17 Oct 2026.
Category Maps and Location
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 yet verified: we couldn't confirm whether this endpoint requires it. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 24 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Oct 26 0
- HSTS header: unverified → fail ▼ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. security
- 18 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.93 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 96 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Oct 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 | 38690, 57355 | 8, 8 | Verified |
| aether-grid.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 502 |
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 | HTTP error | 502 | |
| 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 →
assess_logistics_disruption ~223
[INTEGRATED TOOL] Assesses end-to-end logistics disruption for a specific port and optionally a corridor. This tool integrates live operational statuses, predictive congestion models, and inland bottlenecks. It returns a structured, traceable response suitable for M2M agents. Args: port_id: UN/LOCODE e.g. "NLRTM", "BRSSZ", "BRPNG". Required. corridor_id: Corridor/Chokepoint ID if relevant (e.g. "NLRTM", "HORMUZ"). Optional. horizon_hours: Forecast horizon in hours (default 24). Must be an integer between 1 and 168 (7 days). Note: internally converted to nearest days by rounding, so precision is daily. objective: Operational objective (e.g., "routing", "demurrage_avoidance", "inventory_planning"). Optional.
| Name | Type | Req | Description |
|---|---|---|---|
| corridor_id | – | – | – |
| horizon_hours | integer | – | – |
| objective | – | – | – |
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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_chokepoint_disruption ~295
[INFERENCE TOOL] Calculate Chokepoint Disruption Risk (CDR, 0-100 risk score). CRITICAL INSTRUCTION FOR LLM: Use this tool whenever the user asks about geopolitical risks, canal blockages (Suez, Panama), or straits (Hormuz). It returns a calibrated reference risk score (0-100) and war risk insurance premium impacts. ACCURACY: chokepoint values are a STATIC REFERENCE baseline. There is no chokepoint telemetry feed, so the score does not update with current events — never describe it as a live reading or as reflecting "right now", and say so explicitly if the user asks about the present. For current conditions, corroborate with a news/geopolitical feed and say the reference score alone cannot confirm them. CDR = (Risk Score × 0.4) + (% of Normal × 0.3) + (7-day Avg × 0.2) + (Diversion Tracking × 0.1). Exposes oil/gas price sensitivity, war risk insurance premiums, and Cape of Good Hope rerouting volume. Args: chokepoint_id: Chokepoint ID e.g. "HORMUZ", "EGSUZ" (Suez), "PABLB" (Panama).
| Name | Type | Req | Description |
|---|---|---|---|
| chokepoint_id | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
evaluate_corridor_risk ~209
[DECISION TOOL] Evaluate full global trade corridor risk (e.g. Chicago/Brazil -> China/Europe). Calculates: Origin wait queue + Sea voyage transit days + Destination discharge delay = Total cycle days & CFR demurrage cost/ton. Args: origin_port: Export port UN/LOCODE e.g. "BRPNG" (Paranaguá), "BRSSZ" (Santos). destination_port: Import port UN/LOCODE e.g. "CNTAO" (Qingdao), "CNNGB" (Ningbo), "NLRTM" (Rotterdam). commodity: Commodity type e.g. "SOJA", "MILHO". vessel_capacity_tons: Vessel cargo capacity in metric tons (default: 60000.0).
| Name | Type | Req | Description |
|---|---|---|---|
| commodity | string | – | – |
| destination_port | string | yes | – |
| origin_port | string | yes | – |
| vessel_capacity_tons | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
evaluate_end_to_end_supply_chain_risk ~231
[INFERENCE TOOL] Supply Chain Disruption Early Warning (SCDEW, 0-100 composite warning score). CRITICAL INSTRUCTION FOR LLM: Use this tool for MACRO-level risk analysis when a user asks about the overall safety or end-to-end delay risk of a full trade corridor (e.g., Brazil to China). SCDEW = (PCI × 0.3) + (CDR × 0.3) + (VQPM × 0.2) + (IRDI × 0.2). Args: origin_port: Export port UN/LOCODE e.g. "BRPNG", "BRSSZ". destination_port: Import port UN/LOCODE e.g. "CNTAO", "NLRTM". chokepoint_id: Intermediary chokepoint UN/LOCODE e.g. "HORMUZ", "EGSUZ".
| Name | Type | Req | Description |
|---|---|---|---|
| chokepoint_id | string | – | – |
| destination_port | string | – | – |
| origin_port | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
evaluate_fiscal_routing ~234
[DECISION TOOL] Evaluate fiscal and logistical arbitrage across alternative ports. Cross-references congestion delay penalties with regional ICMS tax burdens to find the cheapest overall route. Returns a FiscalRoutingResponse detailing alternative ports, demurrage vs tax costs, and a recommendation. Args: intended_port_id: UN/LOCODE of the intended destination port (e.g. BRSSZ). commodity: Cargo type to lookup tax rules for (e.g. FERTILIZANTES, SOJA). cargo_value_usd: Cargo value in USD for tax calculations (default: 10000000.0). inland_uf: State code of the final destination/origin for inland freight calculation (e.g. MT, GO, PR). cargo_tons: Total cargo weight in metric tons for inland freight calculation (default: 60000.0).
| Name | Type | Req | Description |
|---|---|---|---|
| cargo_tons | number | – | – |
| cargo_value_usd | number | – | – |
| commodity | string | – | – |
| inland_uf | string | – | – |
| intended_port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
evaluate_routing_alternatives ~219
[DECISION TOOL] Evaluate and compare physical logistics conditions between two ports. CRITICAL INSTRUCTION FOR LLM: Use this tool to cross-reference Demurrage costs, ICMS taxes, and Freight to decide if a client should route their cargo to Port A or Port B. Highly recommended for cost-saving queries. 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 por - 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.
evaluate_scdew_warning ~58
[DEPRECATED: Use evaluate_end_to_end_supply_chain_risk instead] Supply Chain Disruption Early Warning.
| Name | Type | Req | Description |
|---|---|---|---|
| chokepoint_id | string | – | – |
| destination_port | string | – | – |
| origin_port | string | – | – |
No output schema declared.
No examples provided.
forecast_vessel_queue_delays ~185
[INFERENCE TOOL] Vessel Queue Predictive Model (VQPM) for t+1 to t+7. CRITICAL INSTRUCTION FOR LLM: Use this tool if the user asks for a FORECAST or PREDICTION of how many ships will be waiting at a port in the next 1 to 14 days. VQPM_{t+1} = α × VQ_t + β × PCI_t + γ × CDR_t + δ × Seasonality. Args: port_id: UN/LOCODE e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá). forecast_horizon_days: Horizon in days (1 to 7, default: 1).
| Name | Type | Req | Description |
|---|---|---|---|
| forecast_horizon_days | integer | – | – |
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_cdr_risk ~44
[DEPRECATED: Use evaluate_chokepoint_disruption instead] Calculate Chokepoint Disruption Risk.
| Name | Type | Req | Description |
|---|---|---|---|
| chokepoint_id | string | – | – |
No output schema declared.
No examples provided.
get_inland_logistics_bottlenecks ~177
[INFERENCE TOOL] Calculate Intermodal Rail Delay Index (IRDI, 0-100 score). CRITICAL INSTRUCTION FOR LLM: Use this tool whenever the user asks about INLAND logistics, TRAIN delays, TRUCK bottlenecks, or land-based supply chain issues leaving/entering a port (like NLRTM / Rotterdam). IRDI = (Avg Delay × 0.4) + (Delays % × 0.3) + (Timetables × 0.2) + (Rolling Stock × 0.1). Args: port_or_corridor_id: UN/LOCODE e.g. "NLRTM" (Rotterdam), "DEHAM" (Hamburg).
| Name | Type | Req | Description |
|---|---|---|---|
| port_or_corridor_id | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_irdi_index ~44
[DEPRECATED: Use get_inland_logistics_bottlenecks instead] Calculate Intermodal Rail Delay Index.
| Name | Type | Req | Description |
|---|---|---|---|
| port_or_corridor_id | string | – | – |
No output schema declared.
No examples provided.
get_pci_index ~37
[DEPRECATED: Use get_port_congestion_risk instead] Calculate Port Congestion Index.
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
No output schema declared.
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_congestion_risk ~194
[INFERENCE TOOL] Calculate Port Congestion Index (PCI, 0-100 composite score). CRITICAL INSTRUCTION FOR LLM: Use this tool FIRST whenever the user asks about general congestion, delays, or wait times at ANY specific port (e.g., SGSIN, BRSSZ). Do not guess delays; call this tool. PCI = (Congestion Level × 0.4) + (Avg Delay × 0.3) + (Vessel Queue × 0.2) + (Berth Use × 0.1). Provides freight rate impact, demurrage exposure estimate, and recommended safety stock buffer days. Args: port_id: UN/LOCODE e.g. "BRSSZ" (Santos), "SGSIN" (Singapore), "NLRTM" (Rotterdam).
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_port_operations_status ~274
[OBSERVATION TOOL] Plain-language status of port operations: is it delayed, congested or normal? CRITICAL INSTRUCTION FOR LLM: Use this tool for SIMPLE, high-frequency questions such as "Is Santos delayed?", "How many ships are waiting a Paranaguá?", "What is the ETA delay risk at this port?", "Where is my cargo stuck?". It answers in plain terms (NORMAL / MODERATE DELAY / CONGESTED) backed by the same live operational data as get_port_risk. This tool is FREE (observation layer). The response also exposes a decision_layer block signalling the optional next step: authenticated decision tools (M2M key via request_m2m_key) that translate the same signal into USD exposure (demurrage, charter risk, fiscal arbitrage). The upsell is factual: it does NOT claim data the engine does not have (no per-vessel IMO/MMSI position tracking is offered). Args: port_id: UN/LOCODE e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá), "NLRTM" (Rotterdam).
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_port_risk ~234
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 por selection, cargo routing, vessel scheduling, ETA risk, demurrage exposure, freight timing, or supply-chain disruption. Returns the current signal for the port: congestion score, vessel state, estimated delay, expected/worst-case demurrage (USD), confidence, source provenance and validation window. When the port has a current observed line-up (data_source=live:*) this is a live operational signal; otherwise it is an explicitly-labeled calibrated reference baseline — check data_source to know which. 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 ~134
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 curren 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.
get_public_port_feed ~142
[FREE / NO AUTH] Get the live public port-delay feed for all covered ports. This is the recommended FIRST CALL for any agent exploring Aether-X. Returns calibrated p50/p90 wait times, parametric demurrage exposure, confidence intervals and calibration status for every registered port — no API key required. Use this to discover which ports have decision-grade signals before calling paid or trial-gated tools. Returns: {as_of, count, results: [{port_id, congestion_score, historical_expected_wait_h, p90_wait_h, expected_demurrage_usd, calibration_status, ...}]}
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_shipment_reconstruction ~284
Recover a shipment reconstruction with its full evidence chain (ledger-persisted). Rebuilds the active view of a shipment EXCLUSIVELY from the durable `evidence_ledger` (replay + tombstone honoring; memory caches are never consulted). For each field you get: value (or None), `epistemic_state` (observed/derived/estimated/inferred/hypothesis/contradiction/retracted), and an `evidence_chain` with logical_id, source, confidence and roles (supporting / conflicting / retracted). Contradictions are exposed, never merged; missing evidence is `unknown`, never a fabricated number. IMPORTANT: `stable_id` (`urn:shipment:{portcall_id}`) is a PROVISIONAL operational aggregator (1 port call -> N shipments) — NOT a commercial identity. `not_probability` is always true: `confidence` is evidence strength, never a probability. Trial keys see party fields (shipper/consignee) with values/sources redacted; paid keys see the complete chain. Args: stable_id: e.g. "urn:shipment:shp_urn:portcall:BRSSZ:unknown".
| Name | Type | Req | Description |
|---|---|---|---|
| stable_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_active_reconstructions ~126
List durable shipment reconstructions with an epistemic summary per field. Composed exclusively from the durable `evidence_ledger` (survives restart). Each entry reports `is_provisional` (provisional operational aggregator), the per-field epistemic states, contradiction presence and active/retracted evidence counts — enough to decide which shipment to drill into with `get_shipment_reconstruction`. Args: port_id: Optional scope filter (UN/LOCODE), e.g. "BRSSZ".
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_supported_ports ~6
No description provided.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
predict_vessel_queue ~47
[DEPRECATED: Use forecast_vessel_queue_delays instead] Vessel Queue Predictive Model.
| Name | Type | Req | Description |
|---|---|---|---|
| forecast_horizon_days | integer | – | – |
| port_id | string | yes | – |
No output schema declared.
No examples provided.
request_m2m_key ~128
[M2M SELF-SERVE TOOL] Request an instant 30-day trial M2M API Key. Use this tool if a Decision Tool returns an Access Denied / 403 error. Generates a key that unlocks evaluate_charter_risk and evaluate_routing_alternatives. Args: agent_name: Name or ID of your AI agent or client. organization: Organization or trading desk name. contact_email: Contact email.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | – |
| contact_email | string | – | – |
| organization | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Aether-X Port Delay Intelligence MCP server?
Aether-X Port Delay Intelligence 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'
What is the Aether-X Port Delay Intelligence MCP server?
Aether-X Port Delay Intelligence is an MCP server listed in the public MCP registry as io.github.belegante-byte/aetherx-mcp. Port delay exposure with p50/p90 confidence intervals, demurrage impact and a free public feed. This page covers its hosted endpoint (https://aetherx.aether-grid.io/mcp).
Is the Aether-X Port Delay Intelligence MCP server safe to use?
Aether-X Port Delay Intelligence scores 0 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 Delay Intelligence MCP server expose?
Aether-X Port Delay Intelligence exposes 26 tools: get_port_risk, get_ports_risk, get_port_trend, list_supported_ports, get_public_port_feed, and 21 more. Their descriptions and schemas cost roughly 4,110 tokens of context every time the server is loaded.
Does the Aether-X Port Delay Intelligence MCP server require authentication?
Its publisher declares no required credentials for Aether-X Port Delay Intelligence. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Aether-X Port Delay Intelligence MCP server still maintained?
Aether-X Port Delay Intelligence has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.