Skip to main content
Glama

Related Servers

Alternatives to jevx-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts to query Jev's typed decision model—yes/no, choice, and score—with calibrated probabilities, while defaulting to an offline mock and disclosing all egress unless explicitly enabled.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to get machine-readable yes/no, choice, and score decisions from TypeSafe Jev, bridging fast classification to Cursor and other clients.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to call TypeSafe's JEV classifier and receive structured, typed judgments with probabilities for binary, choice, and scoring questions.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to consult TypeSafe's Jev through a judge tool, answering narrow typed questions with calibrated probabilities instead of prose.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable agents to run TypeSafe's Jev judgment model as typed yes/no, choice, and score tools, with calibrated probabilities, confidence thresholds, escalation for uncertain or non-judgment tasks, and an optional action gate that fails open.
      MIT
    • A
      license
      Not graded
      quality
      C
      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.
      MIT

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct role: validate_questions is a pre-flight shape check, decide is the core inference call, and open_in_jevx is a browser handoff utility. There is no meaningful overlap or chance of selecting the wrong tool for a given task.

    Naming Consistency3/5

    All names are lowercase snake_case, but the patterns vary: validate_questions is verb_noun, decide is a bare verb, and open_in_jevx is a verb phrase with a product name. The names are readable and intuitive, yet they do not follow a single predictable convention.

    Tool Count5/5

    At three tools, the server is tightly scoped to the Jev decision workflow: validate, run, and hand off to the playground. Every tool earns its place and the small count is appropriate for such a narrow API.

    Completeness4/5

    The core validate-decide-open flow is fully covered with no dead ends for typical usage. Minor gaps exist around decision management or account/credit introspection, but they are not required for the server's stated purpose.