mcp-registry/io.github.belegante-byte/aetherx-mcp · v1.5.0
As of 2026-10-17 18:44 UTC, the Belegante Byte Aetherx MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 31 outages in 90 days, with a median recovery of 7 minutes.
Live port congestion signal, vessel queue, ETA delay and demurrage exposure for 19 ports.
Point your MCP client at this streamable-http endpoint: https://aetherx.aether-grid.io/mcp
1 tool(s) have no description.
Describe what each tool does, when to use it and what it returns in one or two sentences. Models choose tools almost entirely from this text.
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.
26 of 26 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
47 parameter(s) across 24 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Reachable 98.9% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~1,809 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 24 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.belegante-byte%2Faetherx-mcp/fixes
{
"name": "get_cdr_risk",
"description": "[DEPRECATED: Use evaluate_chokepoint_disruption instead] Calculate Chokepoint Disruption Risk.",
"inputSchema": {
"type": "object",
"title": "get_cdr_riskArguments",
"properties": {
"chokepoint_id": {
"type": "string",
"title": "Chokepoint Id",
"default": "HORMUZ"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_inland_logistics_bottlenecks",
"description": "[INFERENCE TOOL] Calculate Intermodal Rail Delay Index (IRDI, 0-100 score).\n\n 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).\n\n IRDI = (Avg Delay × 0.4) + (Delays % × 0.3) + (Timetables × 0.2) + (Rolling Stock × 0.1).\n\n Args:\n port_or_corridor_id: UN/LOCODE e.g. \"NLRTM\" (Rotterdam), \"DEHAM\" (Hamburg).\n ",
"inputSchema": {
"type": "object",
"title": "get_inland_logistics_bottlenecksArguments",
"properties": {
"port_or_corridor_id": {
"type": "string",
"title": "Port Or Corridor Id",
"default": "NLRTM"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_irdi_index",
"description": "[DEPRECATED: Use get_inland_logistics_bottlenecks instead] Calculate Intermodal Rail Delay Index.",
"inputSchema": {
"type": "object",
"title": "get_irdi_indexArguments",
"properties": {
"port_or_corridor_id": {
"type": "string",
"title": "Port Or Corridor Id",
"default": "NLRTM"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.belegante-byte/aetherx-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.belegante-byte/aetherx-mcp"}) over MCP.
evaluate_fiscal_routing ~288 tokensassess_logistics_disruption ~278 tokensevaluate_corridor_risk ~273 tokensevaluate_charter_risk ~267 tokensevaluate_end_to_end_supply_chain_risk ~254 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.belegante-byte%2Faetherx-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.belegante-byte%2Faetherx-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.belegante-byte%2Faetherx-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.belegante-byte%2Faetherx-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.belegante-byte%2Faetherx-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9796c3816b67994b…, first seen 2026-10-17, included at leaf 2449 of 18,508. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable other servers · most reliable ml servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 18:44 UTC, the Belegante Byte Aetherx MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 31 outages in 90 days, with a median recovery of 7 minutes.
Belegante Byte Aetherx MCP server advertises 26 tools, including assess_logistics_disruption, evaluate_charter_risk, evaluate_chokepoint_disruption, evaluate_corridor_risk, evaluate_end_to_end_supply_chain_risk.
Point your MCP client at this streamable-http endpoint: https://aetherx.aether-grid.io/mcp
Glimind scanned all 26 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.