Skip to main content
Glama

Related Servers

Alternatives to fleet-geo

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server provides a stateful, resettable, verifiable API runtime that gates every tool call, enabling agents to run long workflows against provider-shaped environments without live provider write access. It records decisions, side effects, and outcome evidence for replayable, verifiable benchmark runs.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      This server enables agents to identify users and organizations, inspect versioned datasets and model lineage, start training jobs, run and read evaluations, verify deployments, and execute typed workflows through authenticated MCP endpoints.
      12
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables AI agents to investigate targets text-first, retrieve compact paged results with retained originals, use cropped images only for visual gaps, rank next actions through local Q-learning, export findings as OKF, and reconstruct approved web observations into frontend code. It runs locally over MCP stdio with schema discovery, exact upstream tool forwarding, provenance, and optional human feedback.
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server implementing a multi-phase backend for structured model interactions, bounded compilation, exact-hash confirmation, and Codex-run provenance, with trust-separation hardening.
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for achieving peak inference performance by detecting drift between code and runtime behavior, comparing against benchmarks, and providing optimization templates.
      8
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly different objects: locate_model (model→location card), trace_endpoint (hostname→serving chain), lookup_prefix (IP→ASN/region), fleet_status (batch roll-up). The closest pairs are trace_endpoint vs lookup_prefix (hostname vs address, both emitting ASN/RDAP/cloud region) and inspect_edge vs observe_endpoints (both probes, different planes), but the descriptions explicitly disambiguate by input type and plane.

    Naming Consistency4/5

    All names are snake_case and almost all follow verb_noun (inspect_edge, record_fact, probe_latency, locate_model, trace_endpoint, lookup_prefix, explain_rules). The one deviation is fleet_status, a noun-only name, which breaks the pattern slightly but remains readable in context.

    Tool Count5/5

    Ten tools is well within the sweet spot and each maps to a distinct investigation step (edge, control, origin, legal, catalog write, discovery, falsification, meta). No tool feels redundant filler, and none of the planes is served by more than one or two tools.

    Completeness4/5

    Coverage is strong across the four planes: inspect_edge (edge), observe_endpoints (control), trace_endpoint/lookup_prefix/locate_model (origin), record_fact (catalog write), plus fleet_status and explain_rules. The notable gap is the catalog read/delete side — record_fact writes facts but there is no tool to list, inspect, or retract a fact, so bad entries cannot be corrected without re-recording.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues