jev-domain-mcp
Related Servers
Alternatives to jev-domain-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityCmaintenanceProvides agents with fast, typed, calibrated decision tools for classification, scoring, yes/no checks, and gating risky tool calls.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to send natural language and JSON application state to a judge tool that returns typed judgments (yes/no probability, choice, or score) with model and usage metadata, and fails gracefully without blocking workflows.1Apache 2.0
- AlicenseAqualityBmaintenanceEnables typed, calibrated judgment calls through classify, score, check, and batched ask tools, each returning full probability distributions for programmatic decisions.5220 npm4MIT
- AlicenseNot gradedqualityBmaintenanceEnables governed tool-calling agents with policy decisions, optional human approval, hash-chained audit logging, and deterministic evaluation.MIT
- AlicenseAqualityBmaintenanceEnables coding agents to compact conversation contexts verbatim, make fast decisions through choice, boolean, and rubric scoring, and enforce command safety guardrails.6MIT
TDQS
Scored across 2 tools
review_patch and screen_content operate on entirely different inputs (git diffs vs. text) and produce different domain-specific verdicts. There is no realistic ambiguity about which tool to select for a given task.
Both tool names follow the same lowercase verb_noun pattern: review_patch and screen_content. The naming is concise, predictable, and clearly conveys the action being performed.
Two tools is at the low end of acceptable for an MCP server. Each tool is substantive, but the server feels thin for something labeled a 'domain' MCP and would benefit from additional related decision gates.
The two exposed gates are self-contained for their specific inputs, but the broader Jev decision-model domain is not fully mapped. There are no tools for configuration, audit feedback, or other content types, which could be notable gaps depending on the intended use.