Skip to main content
Glama
PyModel

jev-mcp-python

by PyModel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jev-mcp-python

No user-submitted related servers found.

    Related Servers

    • jev-mcp

      blakestone-x
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to perform typed judgments—classify, score, check, match, and screen—over closed answer sets with confidence scores, without text generation.
      7
      4
      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

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

    • jev-domain-mcp

      jiawei686
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to call typed code-review and content-moderation decision tools, returning structured verdicts, probabilities, and confidence-gated actions.
      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.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct verb and purpose: verify claims, screen for injection, find best match, classify, decide, rerank, compare, extract, review, and gate. Even similar tools like jev_find and jev_rerank are clearly differentiated (one picks a single best, the other orders all), and jev_review vs jev_gate are explicitly separated by the presence of claim verification.

    Naming Consistency5/5

    All tools follow a consistent 'jev_' prefix with a lowercase descriptive verb (verify, screen, find, classify, decide, rerank, compare, extract, review, gate). The naming pattern is uniform and predictable, making it easy for an agent to infer function from the name.

    Tool Count5/5

    10 tools is well within the ideal 3-15 range. Each tool covers a distinct capability within the Jev evaluation domain, and none feel redundant or unnecessary. The count is appropriately scoped for the server's purpose.

    Completeness5/5

    The tool set provides comprehensive coverage of evaluation tasks: claim verification, prompt-injection screening, semantic search, classification, decision-making, reranking, pairwise comparison, structured extraction, patch review, and gated review with claim verification. Cross-references between tools (e.g., using jev_gate for patches with claims, jev_review without) indicate a well-thought-out and complete surface with no obvious gaps for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources