Skip to main content
Glama

Related Servers

Alternatives to Drex MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable agents to query the NanoJev decision service in natural language for boolean, choice, and score evaluations across decision-loop stages such as feasibility checks, action selection, risk assessment, and look-ahead planning.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP hosts to send a context, question, and named choices to Jev System One, returning the selected choice, confidence, and per-choice probabilities.
      1,141 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a locally running Kev decision model through MCP tools, returning calibrated probabilities for typed questions such as yes/no, choice, and score.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables any agent to ask typed questions (Noul, Choice, Score) against Jev's decision model and receive structured answers with probabilities, confidence, and an auditable act/review/abstain decision.
      145 npm
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is zero possibility of confusion or overlap. The single tool's purpose is clearly stated and cannot be mistaken for any other tool.

    Naming Consistency4/5

    The name 'drex_decide' follows a clear server-prefix + verb convention and is readable and predictable. With only one tool there is no pattern to compare against, but the naming itself is sound and consistent with the server identity.

    Tool Count3/5

    A single tool feels thin, but the server's stated scope — returning a closed decision with a probability distribution — is narrow enough that one tool can plausibly fulfill it. Borderline, but not egregiously under-scoped.

    Completeness4/5

    The core decision-making operation is covered, and the description clearly demarcates that acting on the decision is the caller's responsibility. Minor gaps exist (e.g., no way to configure Drex's behavior or provide structured context), but the primary workflow is functional.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues