Skip to main content
Glama

jev-mcp-server

CI PyPI Python License: MIT Downloads

简体中文

MCP server for Jev, TypeSafe's System One model. It exposes the three official question types (choice, score, noul) plus compare, verify, batch classify, and a one-command installer that writes your client config for you.

What is Jev

Jev is a hosted decision model from TypeSafe. You send a structured question with enumerated options; it returns a typed answer with calibrated probabilities and a confidence value. It does not write prose and it does not explain itself. A single call costs roughly $0.00002 to $0.0001 and returns in about half a second, which is what makes it practical for the small, repeated judgments (triage, routing, grading, gating) that a frontier model is too slow and too expensive to run on every item.

You need a TypeSafe API key. There is no local model, no second LLM, and nothing else to install.

Related MCP server: jev-judge-mcp

Quickstart

# 1. Get a key: https://console.typesafe.ai/settings/keys

# 2. Install into your client (config is written for you):
uvx jev-mcp-server install claude-code    # or: pi | cursor | opencode | codex

# 3. Restart the client if it is running, then ask:
#    "Which of these rollout plans is safest? Show me the probability split."

No uv yet? curl -LsSf https://astral.sh/uv/install.sh | sh, or brew install uv, or pip install uv. A plain pip install jev-mcp-server works too; the installer subcommand is the same either way.

Most stdio MCP clients take this shape:

{
  "mcpServers": {
    "jev": {
      "command": "uvx",
      "args": ["jev-mcp-server"],
      "env": { "TYPESAFE_API_KEY": "apikey_xxx" }
    }
  }
}

Codex (~/.codex/config.toml):

[mcp_servers.jev]
command = "uvx"
args = ["jev-mcp-server"]

[mcp_servers.jev.env]
TYPESAFE_API_KEY = "apikey_xxx"

OpenCode (opencode.json, "mcp" section): {"jev": {"type": "local", "command": ["uvx", "jev-mcp-server"], "env": {"TYPESAFE_API_KEY": "apikey_xxx"}}}

Prefer not to put the key in config at all? Skip the env block and call the setup tool once from your agent. It verifies the key live and stores it with 0600 permissions.

Tools

Tool

Official type

What it does

Typical use

choice

choice

Pick 1 of 2-100 options; probabilities over all options, so near-ties are visible

Triage, routing, tie-breaking

score

score

Grade on an ordered 2-8 level rubric; fractional index (1.88 = between levels 1 and 2, leaning to 2)

Risk / severity / quality grading

noul

noul

Yes/no question with a 0-1 degree

"Is this change breaking?"

compare

choice (A/B)

Which of two candidates wins, with the visible probability split

Titles, plans, messages

verify

noul (claim/evidence)

Support degree of ONE claim against evidence you supply

Fact-check lines, log-vs-symptom

classify

choice (batch)

Up to 100 items against one shared category set, aggregated

Labeling queues, sorting inboxes

setup

(none)

Verify a key once, store it locally (0600)

Onboarding without env config

Examples

Real calls; responses quoted as returned (only usage and model trimmed).

choice: which change is most likely a breaking change for API consumers? Options: rename an existing config key, add an optional response field, change the log format.

{"choice": "rename_config_key", "confidence": 1.0,
 "probabilities": {"rename_config_key": 1.0, "add_optional_field": 0.0, "change_log_format": 0.0}}

score: regression risk of rewriting an auth middleware in place, no tests written yet, on a minor/moderate/severe rubric:

{"score": 1.98, "nearest_level": "severe", "confidence": 0.96}

verify: claim "all tests in the latest CI run passed", evidence "the CI log shows 3 failed tests out of 250":

{"noul": 0.01, "verdict": "not supported"}

When to use it

Good fit:

  • Enumerated options: triage, routing, tie-breaks, A/B calls

  • Rubric grading: risk, severity, review triage

  • Binary checks at volume: breaking-change gates, claim-vs-evidence checks

  • Batch labeling: 100 items against one label set for about $0.007

Poor fit:

  • Open-ended reasoning or long-context analysis

  • Anything that needs an explanation attached. Jev returns numbers; any "reason" your assistant adds is its own reading of those numbers, not output from the model

Cost and latency (measured)

Single calls, indicative only; cost at $42 per 1B input tokens.

Call

Latency

Input tokens

Cost

choice, 6 rich options + context

~0.6-0.7s

~1.7k

≈ $0.00007

noul / verify, short context

~0.4-0.6s

~0.3-0.5k

≈ $0.00002

classify, 100 items

~1 min sequential

~100× a single call

≈ $0.007

Configuration

Variable

Meaning

Default

TYPESAFE_API_KEY

API key; env var beats the file stored by setup

required

JEVMCP_BASE_URL

API endpoint override (experiment with relays)

https://api.typesafe.ai/v1/systemone

JEVMCP_MODEL

Model name

jev-latest

JEVMCP_CACHE

1/true/on enables the response cache

off

JEVMCP_CACHE_DIR / JEVMCP_CONFIG_DIR

Relocate cache / key storage

~/.cache/jev-mcp, ~/.config/jev-mcp

With JEVMCP_CACHE=1, identical question payloads are answered from disk at zero cost (usage.cached: true); classify deduplicates repeated items automatically.

FAQ

Why does Jev never explain its choice? By design; "decisions, not strings" is the product. The probability distribution is the output. Explanations would cost the latency and tokens this model exists to avoid.

Do I need another LLM or a local Jev install? No. Jev is a cloud API; there is no local model and no helper LLM. Your agent's main model decides when to call these tools and reads the numbers.

Why not just ask my main LLM? You can, and for one-off questions you probably should. The difference shows up in loops: an LLM's stated confidence is not calibrated, a call costs 100× more, and it takes seconds instead of milliseconds. Per item across a batch, that gap compounds.

Is there another Jev MCP? Yes. jkudish/jev-mcp (Node/npm) offers ten workflow-shaped tools, and a Go server exists. This one is the Python/uvx side: faithful official question types, one-command install, bilingual docs, MIT.

License

MIT

Available Tools

5 tools
choiceA

Ask Jev (TypeSafe System One) to pick ONE of 2-100 mutually exclusive options, with calibrated probabilities.

The official choice question type — for fast, cheap structured decisions: triage, routing, classification, prioritization, tie-breaking among enumerated candidates. Returns probabilities over ALL options (not just the winner), so near-ties are visible. NOT for open-ended generation or multi-step reasoning — use an LLM for those.

Args: question: The decision, e.g. "Which error class is most likely the root cause?" options: Mapping of short unique id -> one-line description. 2-100 options. context: Optional background facts that inform the decision. Keep it short.

Returns: JSON string: {choice, confidence, probabilities (sorted desc), runner_up, model, latency_ms, usage}

Inputs: options (required), question (required), context. Returns: result

classifyA

Batch-classify up to 100 items against ONE shared set of categories using Jev.

Runs the official choice question type once per item and aggregates the results — routing support tickets, labeling log lines, triaging inbox items against your own label set. Much cheaper and faster than an LLM for mechanical labeling.

Args: items: 1-100 non-empty strings to classify. options: Mapping of short unique id -> one-line category description. 2-100 options. question: Per-item question; the item itself is appended automatically. context: Optional background facts shared by all items.

Returns: JSON string: {results: [{item, choice, confidence, probabilities}], summary (counts per choice, sorted desc), model, total_latency_ms, usage: {input_tokens, output_tokens, calls, cached_calls}}

Inputs: items (required), options (required), context, question. Returns: result

noulA

Ask Jev (TypeSafe System One) a yes/no question; returns a 0-1 degree (>= 0.5 leans yes).

The official noul question type — fast, cheap binary checks: "is this change breaking?", "does this log line match the reported symptom?". No probability list, just the degree. NOT for questions that need multi-step reasoning — use an LLM for those.

Args: question: A yes/no question, e.g. "Is renaming a public config key a breaking change?" context: Optional background facts. Keep it short.

Returns: JSON string: {noul, verdict, model, latency_ms, usage}

Inputs: question (required), context. Returns: result

scoreA

Ask Jev (TypeSafe System One) to grade something on an ORDERED scale of 2-8 levels.

The official score question type — risk/severity/quality rubrics, e.g. levels ["minor", "moderate", "severe", "critical"]. Returns a fractional 0-based index into levels (1.88 = between levels[1] and levels[2], leaning to levels[2]), plus confidence and per-level probabilities.

Args: question: What to grade, e.g. "Regression risk of renaming public config key X". levels: 2-8 unique ordered scale points, low to high. context: Optional background facts. Keep it short.

Returns: JSON string: {score, nearest_level, confidence, probabilities (sorted desc), model, latency_ms, usage}

Inputs: levels (required), question (required), context. Returns: result

setupA

One-time onboarding: verify a TypeSafe API key with a live call, then store it locally.

Use when TYPESAFE_API_KEY is not set in the server environment: pass your key once (get one at https://console.typesafe.ai/settings/keys). It is verified against the live API, then saved to ~/.config/jev-mcp/key (permissions 0600) and never echoed back. An existing TYPESAFE_API_KEY env var always takes precedence over the stored file.

Args: api_key: Your TypeSafe API key (from console.typesafe.ai/settings/keys).

Returns: JSON string: {ok, stored_path, verified}

Inputs: api_key (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: setup handles key onboarding, while noul, choice, score, and classify map to different question types (binary, single-choice, ordered-scale, batch). The descriptions explicitly call out boundaries, such as noul being for yes/no only and classify being a batched version of choice.

    Naming Consistency4/5

    Tool names are all single lowercase words with no mixed conventions, which keeps them readable and predictable. The slight deviation is that setup describes an action while noul, choice, score, and classify follow the official TypeSafe question-type naming, but this is minor and does not cause confusion.

    Tool Count5/5

    Five tools is well-scoped for a focused Jev/TypeSafe MCP server: one setup tool plus four distinct query/question types. Each tool maps to a clear capability and none feel redundant or missing.

    Completeness5/5

    The tool surface covers the full apparent lifecycle of using Jev: setup for authentication and noul/choice/score/classify for the available question types. There are no obvious dead ends—setup returns verification, every query tool returns structured results, and classify aggregates batch outputs.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to call TypeSafe's JEV classifier and receive structured, typed judgments with probabilities for binary, choice, and scoring questions.
      1
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to consult TypeSafe's Jev through a judge tool, answering narrow typed questions with calibrated probabilities instead of prose.
      24 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP clients with typed, probabilistic decisions (choices, probabilities, scores) from TypeSafe's System One model, offering validated outputs and flexible provider support.
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to get machine-readable yes/no, choice, and score decisions from TypeSafe Jev, bridging fast classification to Cursor and other clients.
      MIT