mcpbeat Sign in

Aether-X Port Delay Intelligence MCP Server

by belegante-byte Your server? Claim it
not responding

Aether-X Port Delay Intelligence is listed as active in the registry but did not answer our last check. 350 installs a week from pypi. It exposes 26 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 98 · avg 39 · +59% w/w
a month agotoday
Uptime history 55 days of history · worst day 0%
55 days agonow
1.1%
Uptime 24h
2 of 174 checks
26
Tools
read from the server
179 ms
Response time
average over 24h
350
Installs / week
npm and PyPI

What changed 64

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 September 2026. No other catalogue keeps this.

4 Oct 3 tools appeared get_public_port_feed, get_shipment_reconstruction, list_active_reconstructions
3 Oct 2 tool descriptions were rewritten list_supported_ports, request_m2m_key
3 Oct a tool changed version2 times that day
2 Oct 5 tool descriptions were rewritten evaluate_chokepoint_disruption, evaluate_routing_alternatives, get_port_operations_status and 2 more
2 Oct a tool appeared assess_logistics_disruption
29 Sep 7 tool descriptions were rewritten12 times that day evaluate_routing_alternatives, evaluate_scdew_warning, get_cdr_risk and 4 more
29 Sep 7 tools appeared evaluate_chokepoint_disruption, evaluate_end_to_end_supply_chain_risk, evaluate_fiscal_routing and 4 more
28 Sep a tool changed version
20 Sep 11 tools appeared evaluate_charter_risk, evaluate_corridor_risk, evaluate_routing_alternatives and 8 more
20 Sep a tool changed version4 times that day
and 25 more, back to 18 September 2026

Aether-X Port Delay Intelligence does not always answer

Over the last week it answered 0.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add aetherx-mcp --transport http https://aether-x-oracle-production.up.railway.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://aether-x-oracle-production.up.railway.app/mcp
~/.codex/config.toml
[mcp_servers.aetherx-mcp]
url = "https://aether-x-oracle-production.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "aetherx-mcp": {
      "url": "https://aether-x-oracle-production.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "aetherx-mcp": {
      "type": "http",
      "url": "https://aether-x-oracle-production.up.railway.app/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 26

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

evaluate
evaluate_charter_risk
[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).
evaluate_chokepoint_disruption
[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).
evaluate_corridor_risk
[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).
evaluate_end_to_end_supply_chain_risk
[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".
evaluate_fiscal_routing
[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).
evaluate_routing_alternatives
[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".
evaluate_scdew_warning
[DEPRECATED: Use evaluate_end_to_end_supply_chain_risk instead] Supply Chain Disruption Early Warning.
port
get_port_congestion_risk
[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).
get_port_operations_status
[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).
get_port_risk
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).
get_port_state
[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).
get_port_trend
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á).
active
list_active_reconstructions
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".
assess
assess_logistics_disruption
[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.
cdr
get_cdr_risk
[DEPRECATED: Use evaluate_chokepoint_disruption instead] Calculate Chokepoint Disruption Risk.
forecast
forecast_vessel_queue_delays
[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).
inland
get_inland_logistics_bottlenecks
[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).
irdi
get_irdi_index
[DEPRECATED: Use get_inland_logistics_bottlenecks instead] Calculate Intermodal Rail Delay Index.
pci
get_pci_index
[DEPRECATED: Use get_port_congestion_risk instead] Calculate Port Congestion Index.
physical
get_physical_events
[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).
ports
get_ports_risk
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"].
predict
predict_vessel_queue
[DEPRECATED: Use forecast_vessel_queue_delays instead] Vessel Queue Predictive Model.
public
get_public_port_feed
[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, ...}]}
request
request_m2m_key
[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.
shipment
get_shipment_reconstruction
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".
supported
list_supported_ports
no description provided

Endpoints

URLTransportStateLatencyChecked
https://aether-x-oracle-production.up.railway.app/mcp streamable-http answering 15326 ms 10 min ago
https://aetherx.aether-grid.io/mcp streamable-http answering 15399 ms 10 min ago

Alternatives to Aether-X Port Delay Intelligence

same job, measured the same way
Revnuvo Company Intelligence
by hardeyhemy

Observed company technologies, changes and signals for AI agents, with evidence and confidence.

9 tools answering
Coderegistry
by hellosg

Enterprise code intelligence for M&A, security audits, and tech debt. Hosted server with 200k free.

23 tools answering
Lead Intelligence
by timzinin-api

Pay-per-call lead intelligence tools with free MCP discovery and x402 payments.

8 tools answering
Neurohive
by adelelo13

Multi-agent memory intelligence with expertise tracking and conflict detection

55 installs/wk local only
Symbols
by jordan-horner

Fast polyglot source code intelligence: symbols, imports, dependencies, and impact analysis.

local only
Atlas Data Exchange
by atlasipholdingsllc-app

Infrastructure and hazard intelligence with provenance, spatial confidence and quality contracts.

10 tools answering
V
Velarion Company Intelligence
by velarion

Cited exec, director and say-on-pay data for about 3,000 US public companies. Free tier, no card.

12 tools answering
US Brand Intelligence
by timzinin-api

Pay-per-call US brand evidence and signal workflows with free MCP discovery and x402 payments.

21 tools answering

Aether-X Port Delay Intelligence — questions

Answers built from our own checks of this server.

What can Aether-X Port Delay Intelligence do?
It exposes 26 tools, read directly from the server on our last check. Among them: assess_logistics_disruption, evaluate_charter_risk, evaluate_chokepoint_disruption, evaluate_corridor_risk, evaluate_end_to_end_supply_chain_risk, evaluate_fiscal_routing and 20 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Aether-X Port Delay Intelligence mostly used for?
Its tools cluster around evaluate and port. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Aether-X Port Delay Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 2 of 174 checks got a reply (1.1%), average response time 179 ms. The bar chart above shows every period we have measured.
Is Aether-X Port Delay Intelligence still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Aether-X Port Delay Intelligence as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Aether-X Port Delay Intelligence?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Aether-X Port Delay Intelligence need an API key?
No. Aether-X Port Delay Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 26 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Aether-X Port Delay Intelligence?
It answers our handshake in 179 ms on average, which is faster than 74% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Aether-X Port Delay Intelligence?
The pypi package aetherx-mcp was installed 350 times in the last week. Week over week that is +59%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.