Skip to main content
Glama
Kadihx
by Kadihx

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JEV_LLM_MODELNoSystem-2 model nameqwen2.5:7b-instruct
JEV_MEMORY_PATHNoPath to persistent memory file<repo>/.jev-skill-memory.json
JEV_GATE_EXECUTENoThreshold for direct execution0.85
JEV_LLM_BASE_URLNoBase URL for System-2 LLM (Ollama, vLLM, etc.)http://localhost:11434/v1
OPENJEV_BASE_URLNoBase URL for local OpenJev/vLLMhttp://localhost:8000/v1
JEV_GATE_ESCALATENoThreshold for escalation0.6
TYPESAFE_JEV_NATIVENoSet to '1' to enable native Jev mode
JEV_BACKEND_PROVIDERNoBackend provider: auto, typesafe_jev, openjev_local, laya_local, heuristicauto
TYPESAFE_JEV_API_KEYNoAPI key for hosted Jev backend
VERCEL_AI_GATEWAY_KEYNoVercel AI Gateway key as alternative to TYPESAFE_JEV_API_KEY

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
jev_evaluateA

Evaluate a batch of decisions in ONE parallel pass: choice (<=255 options), score (fractional scale) and noul (calibrated probability). Extra questions do not increase latency or cost.

jev_decideA

Route one decision through the 'BELKİ' gatekeeper: confidence above the tuned threshold executes directly ($0 LLM), mid range triggers speculative sub-decisions, low confidence escalates to System 2.

jev_planA

Produce a steeled plan: System-2 hypothesis + hostile anti-thesis, scored by the Jev loop on feasibility, failure risk, cost and maintainability. Works offline with deterministic fallbacks.

jev_redteamB

Generate concrete anti-theses against a thesis, score their severity/evidence with the Jev loop and arbitrate the safest route with residual risks and mitigations.

jev_auditA

Scan a project directory and score five dimensions (architecture, security, marketing, legal, budget) with findings, evidence and ranked fix actions.

jev_researchA

Sweep web (Wikipedia/Brave), academic (arXiv), code (GitHub/npm) and social (HN/X) channels in parallel, re-rank with Jev relevance and synthesize a cited brief. Free/keyless sources by default.

jev_compactB

Delete irrelevant log/grep/diff lines at $0 cost WITHOUT summarizing: kept lines are byte-identical. File paths, commands, error codes, URLs and diff headers are always preserved.

jev_github_mineA

Audit a repository license (permissive vs copyleft/unknown) and, for restricted licenses, extract an architecture-only clean-room spec with a 5-gram similarity guard proving originality.

jev_label_datasetA

Label raw rows with Jev primitives in one fan-out pass and write a JSONL dataset into artifacts/datasets for distillation.

jev_preference_pairsB

Score every candidate answer with the Jev Score primitive and emit chosen/rejected JSONL pairs for local DPO training.

jev_distill_recipeA

Emit a concrete LoRA distillation recipe (axolotl/unsloth + vLLM) for Qwen2.5-0.5B or a ModernBERT-421M decision head; optionally write the axolotl YAML into artifacts/training.

jev_verifyA

Run verification commands (default: npx tsc --noEmit, npm test) in a working directory, record +1/-1 reward into the skill memory and auto-tune the gatekeeper thresholds.

jev_memoryA

Inspect and steer the arena-style skill memory: calibration buckets, verified win rate, threshold auto-tuning and manual outcome recording.

jev_dispatchA

Read shared memory + task intent and pick the next agent role (researcher / planner / implementer / reviewer / writer / auditor) with a ready handoff payload.

jev_guardrailB

Classify a tool call before execution: dangerous pattern blacklist + Jev Noul danger and Score severity produce an allow / ask / block verdict with reasons.

jev_privacy_sanitizeA

Mask PII and secrets (emails, cards, IBAN, Turkish ID, API keys, bearer tokens, private keys, env assignments) locally before anything is sent to an external model.

jev_rerankA

Re-rank retrieved passages with Jev Noul relevance and keep the top-K, dropping the noise.

jev_edge_qaA

Generate a deterministic edge-case test matrix (input, concurrency, dependency, auth, state, time, billing) for a feature spec.

jev_pr_gateA

Check a unified diff for breaking export removals, hardcoded secrets, console leftovers, new TODOs and dependency manifest changes; returns allow/ask/block.

jev_featuresA

List the 20 enterprise features with honest implemented/scaffolded status and their hosting tool.

hub_crawlA

Politely crawl the 11 curated sources (Farnam Street, LessWrong, Derek Sivers, Julian Shapiro, Internet Archive, Open Library, Project Gutenberg, Wikibooks, PhilArchive, PsyArXiv, CORE) into the local SQLite+FTS5 research hub. Respects robots.txt and each source's off-hours crawl window unless force=true.

hub_queryA

FTS5 search over the crawled research hub, re-ranked by Jev Noul relevance into VERIFIED/PROBABLE/REJECTED tiers, then synthesized into a cited, step-by-step answer that grounds claims in mental models and cognitive-science findings over popular advice.

hub_statsA

Report document counts, word totals and last-crawl timestamps per source in the research hub.

jev_backend_infoA

Report the resolved backend chain, pricing, gatekeeper policy, presets, memory summary and workspace paths so agents can self-diagnose the setup.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 24 tools

Disambiguation4/5

Most tools target a clearly distinct resource or stage, and the descriptions are detailed enough to separate them. A few pairs (jev_evaluate/jev_decide, jev_research/jev_rerank, jev_plan/jev_redteam) share conceptual machinery, but their intended workflows are still distinguishable.

Naming Consistency3/5

The common 'jev_' prefix and snake_case style provide a consistent family feel, but the underlying pattern is mixed: some tools are verbs (jev_decide, jev_verify), some verb_noun (jev_label_dataset, jev_distill_recipe), and some nouns or noun phrases (jev_memory, jev_features, jev_preference_pairs). The separate 'hub_' prefix also breaks the single naming scheme.

Tool Count3/5

At 24 tools, the set sits squarely in the heavy range and includes several highly specialized or self-diagnostic tools (jev_features, jev_backend_info, hub_stats). It is not egregious because the server appears to be a broad all-in-one agent platform, but the count still feels larger than a tightly scoped MCP server.

Completeness4/5

The tool set covers major agent workflows well: research, decision-making, planning, red-teaming, dataset preparation, safety checks, and verification. Minor gaps exist—there is no explicit implementation/execution tool and no training execution step beyond emitting recipes—but these are likely handled outside this server or are intentional boundaries.

Maintenance

ActivityMaintained
ResponsivenessNo issues