jev-mcp
Related Servers
Alternatives to jev-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides coding agents with typed classification, yes/no checks, scoring, ranking, and question-answering tools that return calibrated probabilities for fast, reliable decisions.889 npm44MIT
- AlicenseAqualityCmaintenanceEnables agents to call typed code-review and content-moderation decision tools, returning structured verdicts, probabilities, and confidence-gated actions.2MIT
- AlicenseAqualityBmaintenanceEnables typed, calibrated judgment calls through classify, score, check, and batched ask tools, each returning full probability distributions for programmatic decisions.5470 npm7MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to get fast, calibrated typed decisions from a shared Laya decision service: classifying text, scoring rubrics, answering batches of yes/no checks, and running question packs. Exposes guards and tool-call helpers that gate proposed tool calls, screen tool results for injected instructions, check replies and input for leaks or jailbreaks, and validate individual form fields and whole submissions with pass, fix, review, or reject outcomes.Apache 2.0
- AlicenseAqualityBmaintenanceProvides fast, offline typed decision tools (classify, score, check, triage) to agents via the Model Context Protocol, enabling safe local inference across 100+ languages with calibrated confidence and no text generation.878 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceEnables typed decisions (yes/no, choice, score) with transparent preflight checks, honest confidence reporting, and health monitoring.102 npmApache 2.0
TDQS
Scored across 5 tools
Each tool targets a distinct decision primitive: categorical selection, ordinal scoring, binary yes/no, action screening, and a combined multi-question call. The only mild ambiguity is that jev_decidee is a superset of the individual question types, and jev_checck and jev_gate both deal with safety-related decisions, but their outputs are clearly different.
All tools follow the same jev_<verb> convention with lowercase snake_case names and no mixed styles. The verb choice is consistent with each tool's single responsibility, making the set predictable.
Five tools is a well-scoped size for this server: four primitives plus one combined/everytive endpoint. Each tool earns its place and there is no padding or bloat.
The suite covers the visible decision types (choice, score, yes/no, gate) and the decide tool adds a batched path that also supports the noul type. There are no obvious dead ends or missing operations for the stated purpose.