Jev AI MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_AI_MODEL | No | The model to use (default: jev-latest). | jev-latest |
| JEV_AI_API_KEY | Yes | Your API key from jev-ai.pro. Required for tool calls; the server can start without it but tools will fail. |
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_classifyA | Choose one labelled option for routing, categorization or intent detection. Returns choice, confidence and probabilities in answers.result. Use jev_score for ordered levels. Requires JEV_AI_API_KEY from https://jev-ai.pro/jev-api. Sends input to Jev AI and consumes account credits; rate limits apply. Returns model, answers and usage. No automatic retries. |
| jev_scoreA | Rate input on an ordered scale of 2–20 levels. Returns a possibly fractional zero-based score, legend and probabilities in answers.result. Use jev_check for yes/no. Requires JEV_AI_API_KEY from https://jev-ai.pro/jev-api. Sends input to Jev AI and consumes account credits; rate limits apply. Returns model, answers and usage. No automatic retries. |
| jev_checkA | Evaluate a yes/no condition. answers.result.noul is the probability of yes from 0 to 1, not a guaranteed truth or enforcement decision. Use jev_decide for multiple questions. Requires JEV_AI_API_KEY from https://jev-ai.pro/jev-api. Sends input to Jev AI and consumes account credits; rate limits apply. Returns model, answers and usage. No automatic retries. |
| jev_gateA | Assess an action before execution. Returns an advisory allow/confirm/block classification in answers.recommendation and a zero-based risk score in answers.risk. Does not execute or enforce actions; retain your own permission policy. Requires JEV_AI_API_KEY from https://jev-ai.pro/jev-api. Sends input to Jev AI and consumes account credits; rate limits apply. Returns model, answers and usage. No automatic retries. |
| jev_decideA | Evaluate 1–64 named questions in one API request. Each type is noul (yes/no), choice (label map) or score (ordered levels). Returns answers keyed by your question names. Prefer this for several decisions on the same input. Requires JEV_AI_API_KEY from https://jev-ai.pro/jev-api. Sends input to Jev AI and consumes account credits; rate limits apply. Returns model, answers and usage. No automatic retries. |
| jev_saved_judgeA | Evaluate new input with a judge saved in your Jev AI account. Does not change the judge. Optional revision detects changed rules with HTTP 409. Use jev_decide for inline rules. Requires JEV_AI_API_KEY from https://jev-ai.pro/jev-api. Sends input to Jev AI and consumes account credits; rate limits apply. Returns model, answers and usage. No automatic retries. |
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 6 tools
Each tool has a distinct purpose: classification, scoring, yes/no checking, gating, multi-question decisions, and saved judge evaluation. The descriptions cross-reference each other (e.g., 'Use jev_score for ordered levels'), which helps disambiguate, though jev_gate and jev_check could be confused in some safety contexts.
All tools follow a consistent 'jev_' prefix with a clear verb or noun indicating the operation: classify, score, check, gate, decide, saved_judge. The naming pattern is uniform and predictable.
Six tools is well-scoped for a decision/evaluation API. Each tool covers a distinct mode of interaction (single vs. batch, inline vs. saved judge), and none feel redundant or excessive.
The set covers the core decision types: classification, scoring, yes/no, gating, batch decisions, and saved judges. A minor gap is the lack of a tool to create/manage saved judges, but the server's stated purpose is evaluation, not judge management.