openrouter-jev-mcp
Related Servers
Alternatives to openrouter-jev-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to make fast, zero-output-token decisions by evaluating context, diffs, logs, or options through the OpenRouter Decisions API using TypeSafe Jev, returning calibrated probabilities for binary, categorical, or scoring questions.1136 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a Jev model for next-tool recommendations, exposing tools to check status and request tool-choice predictions, while logging all decisions for review.MIT
- AlicenseAqualityBmaintenanceEnables frontier coding agents to delegate routine probabilistic judgments to TypeSafe Jev, providing calibrated triage signals for failures, attempts, completion, context ranking, findings, risk, and generic evidence-grounded questions.7MIT
- AlicenseNot gradedqualityCmaintenanceProvides coding agents with typed classification, yes/no checks, scoring, ranking, and question-answering tools that return calibrated probabilities for fast, reliable decisions.MIT
- 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
TDQS
Scored across 5 tools
Each tool has a distinct evaluation purpose: single check, classification, scoring, batch evaluation, and health reporting. The only mild overlap is between jev_check and jev_evaluate, since evaluate can contain Noul questions, but the singular versus map distinction keeps them separable.
All tools share the jev_ prefix and use lowercase snake_case, creating a clear family resemblance. The main inconsistency is that four tools are verb-based (check, classify, score, evaluate) while jev_health is a noun, but the pattern remains predictable.
Five tools is a well-scoped set for an evaluation-oriented server: single operations plus a batch operation plus health. Each tool has a distinct role without unnecessary redundancy.
The tool surface covers the core evaluation lifecycle: primitive checks, categorical classification, ordered scoring, batched evaluation of mixed question types, and health/configuration readiness. No significant dead ends or missing core operations are apparent for the stated domain.