Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JEV_MCP_LIVENoSet to '1' to run live TypeSafe pytest tests.
JEV_MCP_CONFIGNoPath to an explicit YAML configuration file.
TYPESAFE_MODELNoModel name for Jev. Default: jev-latestjev-latest
JEV_MCP_PROFILENoProfile to use: 'autonomous', 'interactive', or 'custom'.
JEV_MCP_DATA_DIRNoDirectory for cache and telemetry data. Default: ~/.local/share/jev-mcp/~/.local/share/jev-mcp/
JEV_MCP_PROVIDERNoProvider to use: 'typesafe' or 'mock'. Default: typesafe.typesafe
TYPESAFE_API_KEYYesRequired for live Jev. Your TypeSafe API key. Never commit this to source control.
JEV_MCP_LOG_LEVELNoLogging level for stderr (e.g., DEBUG, INFO, WARNING).
TYPESAFE_BASE_URLNoBase URL for the TypeSafe API. Default: https://api.typesafe.aihttps://api.typesafe.ai
JEV_MCP_SHADOW_MODENoEnable shadow mode: 'true' or 'false'. Default: true (shadow mode is on by default).true
JEV_MCP_ALLOW_FAULTSNoMust be set to '1' to enable fault injection (for testing only).
TYPESAFE_ALLOWED_HOSTSNoComma-separated list of additional HTTPS hosts allowed for the provider. Default is only api.typesafe.ai.
TYPESAFE_DEFAULT_MODELNoAlternative environment variable for the model name. Default: jev-latestjev-latest
TYPESAFE_TIMEOUT_SECONDSNoProvider timeout in seconds. Must be between 1 and 120. Default: 3030

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
jev_triage_failureA

Cheap probabilistic triage for test/build/lint/typecheck failures. Use before broad reasoning when the relationship or scope of a failure is unclear. Returns structured likelihood signals; does not diagnose or fix the problem.

jev_compare_attemptsA

Cheap comparison of two unsuccessful implementation attempts. Use when repeated work may be spending frontier inference on the same failed strategy. Returns stuck/progress signals and an advisory control signal; does not choose the next fix.

jev_check_completionA

Cheap requirement/evidence coverage check before an expensive full-task review. Use on large tasks with explicit requirements. Returns per-requirement likelihoods and which items warrant review. Never certifies correctness, safety, or merge readiness.

jev_rank_contextA

Cheap ranking of repository context candidates before deeper frontier inspection. Use when discovery produced many plausible files or symbols. Ranks only; never deletes or permanently excludes candidates.

jev_classify_findingsA

Cheap normalization of review findings from tests, linters, humans, or frontier reviewers. Use to triage a large finding set before expensive reasoning. Returns likelihood signals only. Does not confirm that a vulnerability or defect exists.

jev_assess_riskA

Cheap change-risk triage to decide whether a more expensive frontier review appears warranted. Returns sensitivity likelihoods only. These are not security conclusions and do not certify safety.

jev_judgeB

Generic bounded judgment primitive. Ask one evidence-grounded yes/no proposition per question and receive calibrated probabilities. Rejects generative requests such as writing code, designing architecture, or fixing bugs. Jev evaluates supplied evidence; it does not invent it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 7 tools

Disambiguation4/5

Each tool targets a distinct stage in a review/diagnosis workflow: change risk, failure triage, attempt comparison, completion checks, context ranking, findings classification, and generic judgment. A few tools share the same cheap-likelihood framing, but their input types and intended uses are clearly differentiated.

Naming Consistency5/5

All tools follow the consistent jev_ prefix with a verb_noun pattern (assess_risk, triage_failure, compare_attempts, check_completion, rank_context, classify_findings, judge). There is no mixed casing or stylistic drift.

Tool Count5/5

Seven tools is well-scoped for a probabilistic triage suite, with each tool earning its place as a distinct decision-support primitive. The count is neither too thin nor overloaded.

Completeness5/5

For the stated domain of cheap probabilistic triage, the set covers the major pre-review decision points and even provides a generic judge fallback for arbitrary yes/no propositions. Potential gaps like diagnosing or fixing are intentionally excluded rather than left as dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues