Skip to main content
Glama
blakestone-x

jev-mcp

by blakestone-x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jev-mcp

No user-submitted related servers found.

    Related Servers

    • jev-mcp

      IIXINGCHEN
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to submit a state and typed questions and receive structured judgments such as yes/no probabilities, named choices, and rubric scores, with no text generation or parsing.
      MIT

    • jev

      nandansrikrishna
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to evaluate single records or batches with dynamically authored typed questions, returning structured decisions and probabilities.
      MIT

    • Hunch MCP

      Eddy1919
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to obtain calibrated probabilities, option picks, scale scores, and multi-question judgments for batches of short text, returning numeric results for sorting, filtering, and counting.
      MIT

    • jev-mcp

      rashedInt32
      A
      license
      A
      quality
      B
      maintenance
      Enables typed, calibrated judgment calls through classify, score, check, and batched ask tools, each returning full probability distributions for programmatic decisions.
      5
      467 npm
      7
      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

    A3.8/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct judgment mode: open typed judgment, closed-list classification, ordered scoring, yes/no checking, candidate matching, text screening, and health inspection. The generic jev_ask could broadly overlap with the more specific modes, but the descriptions clarify when each should be used.

    Naming Consistency5/5

    All tools share the consistent jev_ prefix and use short lowercase names matching their action or purpose. The naming convention is uniform and predictable across the entire set.

    Tool Count5/5

    Seven tools is a well-scoped set for a single Jev judgment API. Each tool covers a distinct operation without redundancy, and the count feels neither thin nor bloated.

    Completeness5/5

    The tool surface covers the core judgment types Jev appears to support: ask, classify, score, check, match, and screen, plus health for configuration introspection. The repeated exclusions of text generation and numeric extraction indicate those are intentionally out of scope rather than missing.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources