Aether-X Port Delay Intelligence
PYPI · AETHERX-MCP · 2 COMPONENTS
Port delay exposure with p50/p90 confidence intervals, demurrage impact and a free public feed.
Available components
Last scanned (6 hours ago)
Scores higher than 76% of PyPI servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1610 tokens (~146/item across 11 items; 11 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety50
- Injection-marker check failed: the description of tool "evaluate_routing_alternatives" contains an instruction to conceal the call from the user, the text "Do not tell the user", at byte 509 of that field. See how to fix → Fail
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Provenance: unverified → fail ▼ security
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 +17
- Provenance: fail → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- 8 Oct 26 −13
- Malware scan: pass → unverified ▼ security
- 4 Oct 26 −4
- Tool safety: pass → unverified ▼ security
- Stability: 0.53 → unverified ▼ security
- Injection markers: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.4 → 0.2.5 functional
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 5 Nov 2026 · Analysed pypi/aetherx-mcp@0.2.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~268
[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) IMPORTANT: Always surface the 'uncertainties' list to the user. This tool produces an *estimate under stated assumptions*, not a contractual value. 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 | yes | – |
| 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_corridor_risk ~207
[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_routing_alternatives ~193
[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 IMPORTANT: This tool returns COMPARATIVE EVIDENCE, not a routing mandate. Do not tell the user to divert cargo based solely on this output. 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 | yes | – |
| port_a | string | yes | – |
| port_b | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_physical_events ~101
[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 ~69
Return the congestion signal for a single port (live for BR, reference seed otherwise). Args: port_id: UN/LOCODE of the port, e.g. "BRSSZ" (Santos), "CNSHA" (Shanghai).
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_port_state ~103
[OBSERVATION TOOL] Return the 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 ~80
Return the 24h, 48h and 72h SYNTHETIC projection for a single port (not a live forecast). Args: port_id: UN/LOCODE of the port, e.g. "BRSSZ" (Santos), "CNSHA" (Shanghai).
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_ports_risk ~68
Return congestion signals for several ports in parallel (live for BR, reference seed otherwise). Args: port_ids: list of UN/LOCODEs, e.g. ["BRSSZ", "CNSHA", "NLRTM"].
| Name | Type | Req | Description |
|---|---|---|---|
| port_ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_verified_queue ~97
Return the verified multimodal physical queue for a port, combining sea-side vessels and land-side logistics (trains/wagons). Only works for live ports. Returns INSUFFICIENT_OBSERVATION for others. Args: port_id: UN/LOCODE of the port, e.g. "BRPNG" (Paranaguá) or "BRSSZ" (Santos).
| Name | Type | Req | Description |
|---|---|---|---|
| port_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_supported_ports ~29
List the 35 ports & global chokepoints in the oracle (id, name, country).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
request_m2m_key ~125
[M2M SELF-SERVE TOOL] Request an instant 7-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 runs locally as a PyPI package, launched with uvx aetherx-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · aetherx-mcp
claude mcp add belegante-byte-aetherx-mcp -- uvx aetherx-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 PyPI package (aetherx-mcp).
Is the Aether-X Port Delay Intelligence MCP server safe to use?
Aether-X Port Delay Intelligence scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 11 tools: get_verified_queue, get_port_risk, get_ports_risk, get_port_trend, list_supported_ports, and 6 more. Their descriptions and schemas cost roughly 1,340 tokens of context every time the server is loaded.
Is the Aether-X Port Delay Intelligence MCP server still maintained?
Aether-X Port Delay Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Aether-X Port Delay Intelligence MCP server under?
Aether-X Port Delay Intelligence declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.