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

      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

    • jev-kit

      leighefford
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and local workflows to run Jev-powered tools that judge speeches line by line, audit drafts against goals, bisect hard-to-test bugs, simulate common-sense physics, score note pairs, and ask arbitrary typed questions cheaply.
      7
      60 npm
      1
      MIT

    • laya-mcp

      jerepaira
      A
      license
      A
      quality
      C
      maintenance
      Enables local, LLM-free probabilistic decisions (choice, classification, scoring, yes/no) with real probabilities in 100+ languages, as a drop-in replacement for jev-local tools.
      4
      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

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