Skip to main content
Glama
Brainwires

jev-mcp

by Brainwires
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to jev-mcp

No user-submitted related servers found.

    Related Servers

    • laya-mcp

      fuleinist
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to run fast, local, non-autoregressive System-1 decisions on text, including classification, triage, routing, and safety gating, via six typed tools with probabilistic outputs.
      20
      8
      Apache 2.0

    • poordjaevin

      Icaro0310
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes local MCP tools for typed, calibrated LLM decisions — gating risky actions, yes/no judging, classification, ordinal rating, and multi-question decisions in one pass. Runs on the model Devin's CLI already provides via ACP (or a fully offline local backend), so agents get calibrated confidence with no extra API key, no Ollama, and no waitlist.
      6
      MIT

    • jev-mcp

      jkudish
      A
      license
      A
      quality
      A
      maintenance
      Enables agents to verify claims against cited evidence, screen content for prompt injection and relevance before reading it, and rank candidates by meaning, all with calibrated probability verdicts.
      12
      5,701 npm
      506
      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.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: evaluate is a general-purpose judgment batcher, rank scores candidate texts, verify checks claims against evidence, gate_action flags risky actions, next_step guides agent loops, and list_models manages model selection. There is no meaningful overlap even among the three decision-oriented tools because they operate on different inputs and produce different verdict types.

    Naming Consistency5/5

    All tools share a consistent lowercase snake_case pattern with the jev_ prefix followed by an imperative verb or verb_noun (evaluate, rank, verify, gate_action, next_step, list_models). The convention is uniform and predictable, making it easy for an agent to infer tool purpose from the name alone.

    Tool Count5/5

    Six tools is a well-scoped set for a judgment-model server: a general evaluation API plus four specialized judgment variants and one meta-tool for model listing. Each tool earns its place and there is no sign of bloat or redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle of using a calibrated judgment model: general evaluation, ranking, verification, action pre-flight, next-step guidance, and model discovery. The descriptions explicitly frame jev_evaluate as the catch-all, with the other tools as targeted specializations, so no obvious capability gap remains.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources