kev-decision-mcp
Related Servers
Alternatives to kev-decision-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes four System 1 decision tools — categorical choice, rubric scoring, binary probability assertions, and a pre-execution guardrail — over stdio JSON-RPC. This enables agents to make sub-second routing, triage, and safety decisions without slow generative calls.MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to evaluate typed choice, score, and noul questions and list available models on configured backends such as Ollama nimble/tev/clef, TypeSafe jev, Kev, or Laya via two stdio tools.239 npmMIT
- AlicenseNot gradedqualityAmaintenanceExposes three stdio tools that return typed, calibrated judgments — yes/no, choice, and score — instead of prose, so MCP hosts can query a decision layer offline by default with any live egress reported on stderr.66 npmApache 2.0
- 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
- AlicenseNot gradedqualityAmaintenanceExposes three stdio tools that let an MCP host pose typed judgments — yes/no, choice, and score — and receive calibrated probabilities rather than prose, running offline against a mock unless a credential and live provider are explicitly configured, with every outbound transmission reported on stderr.66 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceExposes three stdio tools that answer typed questions — yes/no, choice, and score — with calibrated probabilities instead of prose, letting any MCP host query a judgment model without a chat interface. Runs fully offline on a synthetic mock by default, with named, per-feature egress disclosure and redaction only when a live provider is explicitly configured.66 npmApache 2.0
TDQS
Scored across 4 tools
Each tool has a distinct purpose: listing models, standard evaluation, order-sensitivity testing, and packed-vs-separate comparison. The three evaluation tools share a common foundation but are clearly differentiated by their constraints and outputs, though they could still be confused without careful reading.
All tools follow a consistent kev_<verb> snake_case pattern, making the set predictable and uniform. The verbs (list, evaluate, permute, separate) are domain-specific but consistently applied.
Four tools is well-scoped for a decision evaluation server. Each tool adds a distinct capability—model discovery, packed evaluation, order sensitivity, and independent evaluation—without redundancy or bloat.
The decision evaluation domain is fully covered: model metadata, packed evaluation supporting multiple question types, order-sensitivity checking, and independent evaluation for comparison. There are no obvious missing operations or dead ends for the stated purpose.