Skip to main content
Glama
weidacn

Jev AI MCP

by weidacn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Jev AI MCP

No user-submitted related servers found.

    Related Servers

    • JevMCP

      NicolasRisso
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to offload yes/no, multiple-choice, and scoring questions to TypeSafe's Jev, returning compact confidence-scored answers to save tokens and improve speed.
      1
      MIT

    • jev-mcp

      rajasekharponakala
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to obtain typed judgments from TypeSafe's Jev System One models, including yes/no probabilities, multiple-choice selections with distributions, and rubric-based scores, directly usable in code.
      5
      2
      AGPL 3.0

    • openrouter-jev-mcp

      ctmx
      A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to obtain probabilistic decisions from Jev AI via OpenRouter for classification, scoring, and validation, with tools like jev_check, jev_classify, jev_score, and jev_evaluate.
      5
      3
      MIT

    • jev-agent-mcp

      thedv91
      A
      license
      A
      quality
      C
      maintenance
      Enables coding or reasoning agents to request structured judgments from TypeSafe's Jev model at decision points, including choices, scores, claim verification, and code reviews, with probabilities and confidence returned as data.
      5
      9 npm
      MIT

    • Jev MCP Proxy

      altregubov
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agent skills to route state-evaluation requests to TypeSafe AI's Jev System One model, supporting typed questions, choice classification, binary probabilities, and rubric scoring with calibrated confidence.
      4
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct purpose: classification, scoring, yes/no checking, gating, multi-question decisions, and saved judge evaluation. The descriptions cross-reference each other (e.g., 'Use jev_score for ordered levels'), which helps disambiguate, though jev_gate and jev_check could be confused in some safety contexts.

    Naming Consistency5/5

    All tools follow a consistent 'jev_' prefix with a clear verb or noun indicating the operation: classify, score, check, gate, decide, saved_judge. The naming pattern is uniform and predictable.

    Tool Count5/5

    Six tools is well-scoped for a decision/evaluation API. Each tool covers a distinct mode of interaction (single vs. batch, inline vs. saved judge), and none feel redundant or excessive.

    Completeness4/5

    The set covers the core decision types: classification, scoring, yes/no, gating, batch decisions, and saved judges. A minor gap is the lack of a tool to create/manage saved judges, but the server's stated purpose is evaluation, not judge management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources