Jev AI MCP
Related Servers
Alternatives to Jev AI MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables 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.51AGPL 3.0
- AlicenseBqualityBmaintenanceEnables coding agents to obtain probabilistic decisions from Jev AI via OpenRouter for classification, scoring, and validation, with tools like jev_check, jev_classify, jev_score, and jev_evaluate.5MIT
- AlicenseAqualityCmaintenanceEnables coding or reasoning agents to request structured judgments from TypeSafe's Jev model at decision points, including choices, scores, claim verification, and code reviews, with probabilities and confidence returned as data.5MIT
- AlicenseBqualityCmaintenanceEnables 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.4MIT
- AlicenseAqualityAmaintenanceEnables agents to get fast, calibrated probabilistic answers from Jev (Typesafe AI) to yes/no, scale, or choice questions about provided material, without using a generative model.1MIT
- AlicenseAqualityBmaintenanceProvides coding agents and CI with a typed decision layer that sends bounded state and questions to Jev, then returns deterministic actions for review, risk assessment, requirement checks, and verification.9MIT
TDQS
Scored across 6 tools
Each tool has a distinct purpose: classification, scoring, yes/no checking, gating, multi-question decisions, and saved judge evaluation. The descriptions cross-reference each other (e.g., 'Use jev_score for ordered levels'), which helps disambiguate, though jev_gate and jev_check could be confused in some safety contexts.
All tools follow a consistent 'jev_' prefix with a clear verb or noun indicating the operation: classify, score, check, gate, decide, saved_judge. The naming pattern is uniform and predictable.
Six tools is well-scoped for a decision/evaluation API. Each tool covers a distinct mode of interaction (single vs. batch, inline vs. saved judge), and none feel redundant or excessive.
The set covers the core decision types: classification, scoring, yes/no, gating, batch decisions, and saved judges. A minor gap is the lack of a tool to create/manage saved judges, but the server's stated purpose is evaluation, not judge management.