jev-domain-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@jev-domain-mcp Review this patch and decide if it can be auto-merged."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
jev-domain-mcp
⚠️ Superseded by single-purpose servers. This aggregated "two tools in one server" repo is kept only as a reference example of the bundled approach. The recommended layout is one MCP = one function. Use these instead:
jev-review-mcp— code-review gate (review_patch)
jev-screen-mcp— content-moderation gate (screen_content)
Domain-specific MCP tools powered by TypeSafe Jev — the System One decision model. The agent gets typed decisions, not prose: each tool pre-builds the Jev questions (candidate sets, rubric, thresholds), so the host never needs to know Jev's API.
This fills the gap identified in the Jev ecosystem: the generic Jev MCP layer
is already crowded (burnigtm/jev-mcp, hangarbay/jev.mcp, mcp-typesafe),
but the domain apps in the gallery are standalone CLIs — none expose their
decision function as an MCP tool. This server wraps two of them.
Tools
Tool | Domain | What it decides |
| Dev workflow | Patch verdict (approve / request_changes / needs_discussion), safety probability, severity, auto_merge vs human_review |
| Content safety | Spam & toxicity probabilities, category, severity, allow / review / block |
Both return a confidence (calibration concentration, not truth) and an
action the agent can branch on directly.
Related MCP server: jev-mcp
Install
npm install
npm run buildSet your key (optional — without it the server runs in deterministic mock mode, no network):
export TYPESAFE_API_KEY=ts_xxx # live Jev calls
# or
export JEV_MCP_MOCK=1 # force deterministic mock (no key needed)Diagnostics:
node dist/index.js doctor
node dist/index.js doctor --jsonUse
Register the server with any MCP client (Cursor, Codex, Claude Code, WorkBuddy):
{
"mcpServers": {
"jev-domain": {
"command": "node",
"args": ["/absolute/path/to/jev-domain-mcp/dist/index.js"],
"env": { "TYPESAFE_API_KEY": "ts_xxx" }
}
}
}Then the agent can call review_patch and screen_content like any other tool.
How a tool works
state (diff / text) ──► Jev: one request, parallel typed questions ──► structured resultNoul→ 0..1 probability (is it safe? is it spam?)Choice→ pick from a fixed candidate set (verdict, category)Score→ ordinal rubric (severity)
The result includes probabilities + confidence, and an action derived
from a simple confidence gate. Low confidence always routes to a human /
stronger model — that is the whole point of a calibrated decision model.
Constraints (from Jev)
Pure text input: no image / audio / video.
State + all questions must fit ~64k tokens total; a single question ≤ 32k.
Do arithmetic / date math in host code, not in Jev.
Output is free; you pay only for input tokens.
License
MIT
Available Tools
2 toolsreview_patchA
Code-review gate powered by Jev (System One decision model). Given a git diff and optional context, returns a verdict (approve / request_changes / needs_discussion), a safety probability, a severity score, a calibrated confidence, and an action (auto_merge / human_review). Only execute auto_merge on high confidence.
Inputs: diff (required), context.
screen_contentA
Content-moderation & classification gate powered by Jev. Given text, returns spam and toxicity probabilities, a category, a severity score, a calibrated confidence, and an action (allow / review / block). Low confidence routes to review; clear, severe violations route to block.
Inputs: text (required), categories.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Typed AI decisions for agents: classify, route, screen evidence, score and batch-label text.
See, price, and control every tool call your AI agents make: policy checks, cost, and audit tools.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Find, vet, and run MCP tools through a secure audited gateway with prompt-injection risk scoring
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables governed tool-calling agents with policy decisions, optional human approval, hash-chained audit logging, and deterministic evaluation.MIT
- AlicenseAqualityBmaintenanceEnables typed, calibrated judgment calls through classify, score, check, and batched ask tools, each returning full probability distributions for programmatic decisions.5209 npm7MIT
- AlicenseAqualityBmaintenanceEnables coding agents to compact conversation contexts verbatim, make fast decisions through choice, boolean, and rubric scoring, and enforce command safety guardrails.6MIT
- AlicenseAqualityCmaintenanceProvides agents with fast, typed, calibrated decision tools for classification, scoring, yes/no checks, and gating risky tool calls.53MIT