openjev-router
Related Servers
Alternatives to openjev-router
No user-submitted related servers found.
Related Servers
- 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 gradedqualityAmaintenanceEnables any MCP host to obtain typed judgments — yes/no, choice, and score — with calibrated probabilities instead of prose, exposed as three tools over stdio. It runs fully offline with synthetic answers by default, and only transmits state to TypeSafe or OpenRouter when live routing is explicitly configured, reporting exactly what leaves at startup.66 npmApache 2.0
- AlicenseAqualityCmaintenanceAn MCP server that answers typed noul/choice/score questions about a given state with probability distributions and confidence, for routing, escalation, and gating decisions. It runs on pluggable backends (local Needle 3 or Laya models, or any OpenAI-compatible endpoint) and logs every decision so recorded ground truth can be used to track calibration.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a locally running Kev decision model through MCP tools, returning calibrated probabilities for typed questions such as yes/no, choice, and score.Apache 2.0
- AlicenseAqualityBmaintenanceEnables coding agents to request calibrated probability judgments over typed questions—yes/no, named choices, or ordered scores—about a described situation, returning one probability per option rather than free text. Runs Cloudflare's Clef model locally on Apple Silicon Macs, with images or video frames optionally attached, and answers delivered as a single MCP tool call.178 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceExposes three stdio tools that ask typed judgment questions — yes/no, choice, and score — and return calibrated probabilities instead of prose, over any MCP-speaking host. Runs on an offline mock by default, with every network transmission named before it happens and credential-gated live routes to TypeSafe or OpenRouter.66 npmApache 2.0
TDQS
Scored across 4 tools
Each tool has a distinct purpose: decision_status reports system state, while the three decide_* tools handle different decision types (choice among options, binary assertion, and tiered scoring). No overlap or ambiguity between them.
Three tools follow the consistent 'decide_' prefix with action verbs, but decision_status deviates with a noun-based name. This is a minor inconsistency, but the pattern is still recognizable.
With 4 tools, the server is well-scoped for a decision-routing purpose. Each tool covers a necessary aspect without redundancy or bloat.
The surface covers status, choice selection, boolean judgment, and scoring, which aligns with the server's purpose. A possible gap is a tool for explaining or justifying decisions, but the provided functionality is solid.