jev-mcp
Related Servers
Alternatives to jev-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.8Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to call fast, typed System One decision tools for yes/no, choice, and score tasks across cloud and on-device backends, with calibrated probabilities, multimodal image input, routing/fallback, and data-destination safeguards.MIT
- AlicenseNot gradedqualityBmaintenanceProvides coding agents with typed classification, yes/no checks, scoring, ranking, and question-answering tools that return calibrated probabilities for fast, reliable decisions.729 npm61MIT
- AlicenseAqualityCmaintenanceProvides agents with fast, typed, calibrated decision tools for classification, scoring, yes/no checks, and gating risky tool calls.53MIT
- AlicenseNot gradedqualityBmaintenanceExposes 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.52 PyPI6MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to hand fast, no-text-output decisions to Jev, reducing latency and token usage while escalating uncertain cases back to the LLM.1,205 npm83MIT
TDQS
Scored across 7 tools
Each tool targets a distinct judgment primitive: evaluate (generic typed questions), rank (ordered relative ordering over a batch), pick (single choice among known candidates), verify (claim support against evidence), gate_action (safety pre-flight), next_step (loop control), and list_models (enumeration). The main soft spot is jev_evaluate, which is an intentionally broad catch-all that could absorb most of the other use cases; the description mitigates this with an explicit 'use only when no other jev_* tool fits' rule, so overlaps are recoverable rather than confusing.
All seven names share a jev_ prefix and snake_case, and most begin with a clear verb (evaluate, rank, pick, verify, list_models). The deviations are jev_gate_action and jev_next_step, which read as noun phrases rather than verb_noun, but they remain predictable and readable.
Seven tools is a tight, well-scoped set for a judgment/inference backend, each covering a clearly separate decision shape. Nothing looks redundant or padded.
The surface covers the core lifecycle of a judgment layer: ask (evaluate), retrieve and narrow (rank, pick), check claims (verify), guard actions (gate_action), control loops (next_step), and introspect models (list_models). Minor gaps exist — no explicit structured-extraction/classification-over-many-items tool, no cost or budget introspection, and no batch multi-evidence variant of verify — but agents can compose the existing tools to work around these.