jev-review-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-review-mcpreview this diff and tell me if it's safe to merge"
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-review-mcp
Code-review gate as a single-purpose MCP tool, powered by Jev (TypeSafe's System One decision model). One MCP, one job.
Real-world cost on OpenRouter — 4.9M tokens · $0.19 over 7 days:
Turns a git diff into a typed decision — no prose, no Jev API knowledge needed from the host agent.
What it does
review_patch(diff, context?) returns a structured verdict instead of free-form text:
Field | Type | Meaning |
|
| Overall call on the patch |
| number (0–1) | P(safe to merge without human review) |
| number (0–4) | Index into the severity scale |
|
| Human-readable severity |
| number (0–1) | Model's calibrated certainty on the verdict |
|
| What the agent should do next |
| boolean | Convenience flag = ( |
Decision gate: action is auto_merge only when verdict === "approve" and safe_prob > 0.8 and confidence >= 0.6. Every other case is human_review.
⚠️ Only execute
auto_mergeon highconfidence. A highsafe_probalone is never permission to merge — gate onconfidence.
Related MCP server: secret-scanner
Install & build
npm install
npm run buildThe compiled server is at dist/index.js.
Add to your MCP client
{
"mcpServers": {
"jev-review": {
"command": "node",
"args": ["/absolute/path/jev-review-mcp/dist/index.js"],
"env": { "TYPESAFE_API_KEY": "ts_xxx" }
}
}
}No key? It still runs in mock mode (JEV_MCP_MOCK=1, or simply no TYPESAFE_API_KEY) so you can try it offline.
Example call
{
"diff": "diff --git a/src/app.ts b/src/app.ts\n- const x = secret\n+ const x = process.env.SECRET",
"context": "Move hardcoded secret to an env var"
}returns something like:
{
"verdict": "request_changes",
"safe_prob": 0.2,
"severity_score": 4,
"severity_label": "critical",
"confidence": 0.7,
"action": "human_review",
"recommended": false
}Model endpoint
Works with any Jev-compatible endpoint. Default is the TypeSafe API
(https://api.typesafe.ai/v1/systemone); override with JEV_BASE_URL
(e.g. an OpenRouter-compatible route) and set TYPESAFE_API_KEY to your
provider key.
Environment variables
Variable | Default | Description |
| — | TypeSafe Jev key. Absent ⇒ mock mode |
|
| Set |
|
| Model id sent to the endpoint |
|
| API base URL |
|
| Per-call timeout (ms) |
Mock mode
With no key (or JEV_MCP_MOCK=1) the server answers deterministically from
keyword heuristics — useful for demos, tests, and offline development. A single
derived risk signal drives every field, so the mock stays internally consistent
(risky diff → low safe_prob, high severity, human_review).
Diagnostics
node dist/index.js doctor # human-readable
node dist/index.js doctor --json # machine-readablePrints mock/live mode, key presence, model, and base URL.
Test
npm testRuns a smoke test against the compiled output in deterministic mock mode.
Notes
Jev is a decision model: pure text in → typed decision out. It does not read images or generate prose.
Diffs are truncated at 60k characters to stay within Jev's ~64k-token budget.
Keep the human in the loop: route anything that is not a high-confidence
auto_mergeto a person.
License
MIT
Related MCP Connectors
Security reviews for coding agents: diffs checked against your org policy and live infrastructure.
Risk-scan a diff, flag AI-generated-code tells, find secrets. 5 of 7 tools need no account.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Guardian agent for AI coding: four frontier models review risky diffs and commits before they ship.
Related MCP Servers
FlicenseAqualityDmaintenanceEnables AI agents to review code diffs for bugs, security issues, and bad patterns, and generate fixes.4-- AlicenseAqualityBmaintenanceEnables scanning diffs or code blobs for leaked secrets, returning a verdict with severity and masked findings, all processed locally with no data sent externally.1MIT
- AlicenseAqualityCmaintenanceAnalyzes GitHub Pull Request diffs for security vulnerabilities and data leaks, using a deterministic filter to skip trivial changes and an AI-powered analysis for logic changes.1MIT

Selvageofficial
AlicenseNot gradedqualityCmaintenanceEnables AI-powered code review of Git diffs through natural language, supporting multiple AI models and Git workflows.36Apache 2.0