Skip to main content
Glama
pedroknigge

mcp_jev

by pedroknigge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp_jev

No user-submitted related servers found.

    Related Servers

    • 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
      MIT

    • mewcp-jev

      AStheTECH
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables structured, rubric-based evaluation of text or structured state using TypeSafe AI's Jev System One API, supporting yes/no, single-choice, and rubric-scored questions in parallel.
      Apache 2.0

    • Jev MCP

      chungsubeen0
      A
      license
      A
      quality
      B
      maintenance
      Enables frontier coding agents to delegate routine probabilistic judgments to TypeSafe Jev, providing calibrated triage signals for failures, attempts, completion, context ranking, findings, risk, and generic evidence-grounded questions.
      7
      MIT

    • jev-eval-mcp

      BYK
      A
      license
      A
      quality
      A
      maintenance
      Enables prototyping, running, and evaluating typed judgment questions against TypeSafe's Jev model, including accuracy, calibration, and threshold analysis.
      3
      1
      MIT

    • jev-mcp

      arunav25
      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
    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.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct role: listing packs, describing a pack, running a pack, running custom questions, and health checking. The only potential confusion is between run_pack and run_questions since both invoke the same TypeSafe System One path, but their descriptions clearly separate pack-based from custom typed workflows.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern: list_packs, run_questions, describe_pack, run_pack. The one outlier is the one-word health tool 'ping', which breaks the pattern but is a common and recognizable convention.

    Tool Count5/5

    Five tools is a well-scoped size for a focused server that handles pack listing, description, execution, custom question runs, and health checks. Each tool has a clear purpose and none feel redundant.

    Completeness5/5

    The server covers the full intended workflow: discover packs via list_packs, understand via describe_pack, execute via run_pack, handle non-pack cases via run_questions, and verify health via ping. Since the pack catalog is closed and free-form ask is intentionally excluded, there are no significant gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources