Skip to main content
Glama

Related Servers

Alternatives to mcp-ocei-oracle

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      62 live, cryptographically signed data tools for AI agents and robots: weather, natural hazards, flights, shipping, space, CVEs, sanctions, software versions, sea ice and more. Every datapoint carries source, licence, timestamp and an Ed25519 signature.
      17 npm
      MIT
    • F
      license
      B
      quality
      C
      maintenance
      Enables AI agents to query verifiable physical-world ground truth for any point on Earth — water availability, seismic and space-weather hazard, ground stability, and resource indications — with every answer backed by a Bitcoin-anchored provenance record that can be independently verified. It also lets agents check whether an Earth-science hypothesis has already been tested, list documented nulls and retractions, and run bounded controlled tests that return UNTESTABLE rather than fabricate a result.
      11
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and developers to retrieve deterministic, SHA-256-verifiable planetary positions, celestial event calendars, Western and Vedic astrology charts, and market-timing data from NASA/JPL DE440, with pay-per-call access.
      1
      MIT

    TDQS

    B3.3/5.0

    Scored across 3 tools

    Disambiguation3/5

    The three tools cover related but overlapping decisions: evaluate_orbital_compute_regime already assesses orbital vs. terrestrial viability, while compute_arbitrage_dispatch and solve_optimal_workload_allocation both output routing/allocation decisions (the former a coarse 3-way directive, the latter a percentage split). An agent could plausibly reach for either of the latter two, or start with the evaluator, without a clear rule for ordering. Descriptions help, but boundaries between 'dispatch' and 'allocate' remain fuzzy.

    Naming Consistency4/5

    All three names are snake_case and verb-led (evaluate_, compute_, solve_), giving a predictable pattern. Minor deviation: compute_arbitrage_dispatch reads awkwardly (verb + noun-phrase 'arbitrage_dispatch') compared to the cleaner verb_object form of the other two, but the convention is still recognizably consistent.

    Tool Count4/5

    Three tools is tightly scoped to a narrow analytical domain (orbital compute economics), and each maps to a distinct decision stage: evaluation, real-time arbitrage, and allocation optimization. It is on the lean side for the breadth of physics and economics mentioned, but nothing feels gratuitous.

    Completeness4/5

    The surface covers the core lifecycle — assess the regime, decide routing from spot prices, and solve for an optimal split — with no obvious dead ends for the stated purpose. Gaps are minor: there is no tool to inspect or override model constants/thresholds, nor a what-if/sensitivity or report-explanation operation, which an agent may want after getting scores.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues