universal-jev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPESAFE_API_KEY | No | API key for TypeSafe (alternative to OpenRouter API key) | |
| OPENROUTER_API_KEY | No | API key for OpenRouter (alternative to TypeSafe 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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jev_compactA | Verbatim context compaction: prunes old verbose tool results while preserving conversation messages 100% verbatim. |
| jev_decide_choiceB | Fast, calibrated multi-option classification with confidence and relative probabilities. |
| jev_decide_noulB | Calibrated boolean verification (Noul) returning true probability between 0.0 and 1.0. |
| jev_decide_scoreC | Calibrated rubric scoring across ordered levels (e.g. 0 to 3 severity/quality). |
| jev_guardB | Security and loop-detection guardrail before running risky commands or tool calls. |
| jev_statusB | Check Jev provider connectivity, model availability, and response latency. |
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 targets a distinct operation: compaction, guard, status, and three decision types that differ in output format (classification, boolean, score). The decide_* tools are clearly differentiated by their suffixes and descriptions, leaving no genuine ambiguity.
All tools use the 'jev_' prefix followed by snake_case verbs and descriptive modifiers (compact, decide_choice, decide_noul, decide_score, guard, status). The pattern is uniform and predictable, with no mixing of conventions.
Six tools is well within the ideal 3-15 range, providing a focused utility set without redundancy or bloat. Each tool earns its place for the server's stated purpose.
The tool surface covers core utility needs: compaction, guardrails, status monitoring, and three decision modalities. Minor gaps exist (e.g., no configuration tool or free-form generation), but these are likely outside the intended scope and do not create dead ends for typical workflows.