jevx-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEVX_API_KEY | Yes | Your Jev AI API key from https://jevx.org/settings/apikeys |
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 |
|---|---|
| validate_questionsA | Run the same shape checks the Jev API enforces, without spending credits or needing an API key. Use this first when writing questions by hand — a malformed question otherwise comes back as a deeply nested validation error. |
| decideA | Send a state (text or JSON) and up to 16 typed questions to Jev AI on jevx.org, and get back the choice, score or yes/no for each — with a calibrated probability on every option. Needs JEVX_API_KEY. Branch your own code on the returned probabilities, not just the top label; a noul of exactly 0.5 means the model declined to answer. |
| open_in_jevxC | The URL to try or continue a decision in the browser playground. |
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 3 tools
Each tool has a distinct role: validate_questions is a pre-flight shape check, decide is the core inference call, and open_in_jevx is a browser handoff utility. There is no meaningful overlap or chance of selecting the wrong tool for a given task.
All names are lowercase snake_case, but the patterns vary: validate_questions is verb_noun, decide is a bare verb, and open_in_jevx is a verb phrase with a product name. The names are readable and intuitive, yet they do not follow a single predictable convention.
At three tools, the server is tightly scoped to the Jev decision workflow: validate, run, and hand off to the playground. Every tool earns its place and the small count is appropriate for such a narrow API.
The core validate-decide-open flow is fully covered with no dead ends for typical usage. Minor gaps exist around decision management or account/credit introspection, but they are not required for the server's stated purpose.