jev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_MODEL | No | Jev model override | jev-latest |
| JEV_ENV_FILE | No | Alternate env file path (default is project .env) | .env |
| TYPESAFE_API_KEY | Yes | TypeSafe credential | |
| TYPESAFE_BASE_URL | No | API base URL | https://api.typesafe.ai |
| TYPESAFE_TIMEOUT_MS | No | Request timeout, 250–120000 ms | 15000 |
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 |
|---|---|
| jev_decideA | Use as an independent second opinion only after inspecting enough context when a bounded decision has 2-255 explicit alternatives and genuine uncertainty remains. The active host model keeps final authority; do not mechanically follow Jev or use it for open-ended coding/prose. |
| jev_routeB | Use as a second opinion for uncertain routing among a fixed set of tools, subsystems, workstreams, or handling paths only when deterministic evidence does not already decide the route. Never changes the user-selected host model. |
| jev_risk_scoreA | Use as an advisory second opinion for consequential or ambiguous-risk changes after inspecting relevant context. Returns low/medium/high/critical risk. It is never authorization to proceed and never overrides tests, deterministic evidence, primary-model reasoning, or review. |
| jev_gateA | Use as an advisory second opinion for an atomic yes/no gate when a probability threshold would materially change the next action. A passed gate is not authorization for destructive, irreversible, production, security, or data-loss-sensitive actions. |
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 4 tools
Each tool has a clearly distinct decision scope: jev_gate handles atomic yes/no gates, jev_decide handles bounded multi-alternative decisions, jev_route handles routing among fixed paths, and jev_risk_score produces risk levels. The descriptions reinforce these boundaries, so an agent can reliably select the right tool without overlap.
All tools share the jev_ prefix and use snake_case, which is predictable and readable. However, the suffixes mix verbs and nouns (decide, route vs. gate, risk_score), so the pattern is mostly rather than perfectly uniform.
Four tools is well-scoped for a focused advisory second-opinion server. Each tool covers a distinct decision category, and none appears redundant or trivial.
The surface covers the main advisory decision types: binary gate, bounded choice, routing, and risk scoring. Minor gaps exist around explaining or calibrating second opinions, but agents can work around them within the stated domain.