Skip to main content
Glama

Related Servers

Alternatives to jevx-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      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.
      103
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      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
      A
      quality
      A
      maintenance
      Lets MCP clients ask typed questions — yes/no, choice, or score — about structured state, including images, and receive calibrated probabilities from System One decision models such as TypeSafe Jev and Cloudflare Clef. Supports TypeSafe, OpenRouter, and local providers selectable per request, with input validation and cost reporting.
      6
      346 npm
      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.
      346 npm
      MIT
    • A
      license
      A
      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.
      1
      8
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents and services to ask small decision models typed questions about text, JSON, images, or video, returning labels, scores, or yes/no answers over MCP tools or a Jev-compatible HTTP API.
      Apache 2.0

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues