A
licenseB
qualityB
maintenanceEnables 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.
2
8 npm
MIT
kev-decision-mcp
Related Servers
Alternatives to kev-decision-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceServes three judgment tools over MCP stdio that return typed answers — yes/no, choice, and score — with calibrated probabilities instead of prose. It runs fully offline by default, requiring an explicit live provider and credential before any state leaves the host.66 npmApache 2.0
- FlicenseAqualityCmaintenanceEnables an LLM client to perform basic arithmetic on two numbers — addition, subtraction, multiplication, and division — plus reverse a supplied text string, through five simple tools exposed over stdio. Inputs and structured text results follow JSON schemas, with invalid operations such as division by zero surfaced as tool errors.5-
- AlicenseNot gradedqualityAmaintenanceExposes three stdio tools (jev_ask, jev_rank, jev_check) that return typed judgments—yes/no, choice, and score answers with calibrated probabilities—instead of prose. It runs on an offline mock by default, resolving a live TypeSafe or OpenRouter credential only when configured, and reports all egress on stderr.66 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceExposes three stdio tools that answer typed questions — noul (yes/no), choice, and score — with calibrated probabilities instead of prose, running fully offline on a synthetic mock unless a live credential is explicitly supplied.66 npmApache 2.0
faraztools-mcpofficial
AlicenseAqualityCmaintenanceEnables AI clients to call small utility tools like echo and Markdown-to-PDF conversion, running locally over stdio.2MIT
TDQS
A4.2/5.0
Scored across 4 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness5/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues