jev-review-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_MODEL | No | Model id sent to the endpoint. | jev-latest |
| JEV_BASE_URL | No | API base URL. | https://api.typesafe.ai/v1/systemone |
| JEV_MCP_MOCK | No | Set 1 to force the deterministic offline mock. | 0 |
| TYPESAFE_API_KEY | No | TypeSafe Jev key. Absent ⇒ mock mode. | |
| JEV_MCP_TIMEOUT_MS | No | Per-call timeout (ms). | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap. The purpose of review_patch is clearly distinct and self-contained.
The sole tool name follows the verb_noun pattern (review_patch), which is clear and predictable. Consistency is trivially maintained with one tool.
A single tool is minimal for a server, though it is focused on one specific gate action. This feels slightly thin but not unreasonable for a narrow purpose.
The domain is a code-review gate, and review_patch covers the core workflow of evaluating a patch and returning a verdict. Missing features like configuration or review history are minor gaps that agents could work around.