Skip to main content
Glama
belegante-byte

io.github.belegante-byte/aetherx-mcp

by belegante-byte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to io.github.belegante-byte/aetherx-mcp

No user-submitted related servers found.

    Related Servers

    • Trimtab AIS

      mrsingh86
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides real-time, machine-readable ship and port conditions for major US container gateways using AIS data, allowing AI agents to query vessel status, berthing events, and gateway conditions without API keys or signup.
      Apache 2.0

    • ShippingRates MCP Server

      vinaybhosle
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides container shipping intelligence for AI agents, enabling demurrage & detention calculations, local charges, inland haulage rates, and CFS tariffs across multiple shipping lines, with pay-per-request USDC payments via x402.
      -

    • ShippingRates

      vinaybhosle
      A
      license
      Not graded
      quality
      D
      maintenance
      Ocean container shipping intelligence for AI agents — D\&D tariffs, freight rates, vessel schedules, port congestion, inland haulage across 6 major carriers. 24 MCP tools.
      MIT

    • mcp-imf-portwatch

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides global maritime trade and chokepoint signals from IMF PortWatch, free and without authentication.
      5 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation4/5

    The two risk tools differ only in cardinality (single vs. batch), but the names and descriptions clearly indicate which to use. list_supported_ports is entirely distinct. Minor potential confusion when querying one port, but explicit pluralization disambiguates.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern: get_ for queries, list_ for enumeration. Pluralization is used appropriately (port vs. ports), making the naming predictable and readable.

    Tool Count4/5

    Three tools is minimal but appropriate for a read-only oracle with a fixed dataset. It covers listing, single query, and batch query without unnecessary bloat. Slightly thin, but well-scoped for the domain.

    Completeness5/5

    The tool set fully covers the domain: you can discover supported ports via list, query one port, or query many in parallel. There are no obvious dead ends or missing operations for the stated purpose of predictive congestion signals.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources