Jev Checkpoint
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPESAFE_API_KEY | Yes | Your TypeSafe API key. Get it from e.g. Openrouter: https://openrouter.ai/typesafe/jev-1.13 |
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 |
|---|---|
| classify_decisionB | Return an advisory, confidence-gated route for a bounded decision. This tool never executes the route. |
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 1 tool
With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly described and distinct from any other potential operation.
The tool name follows a clean verb_noun pattern (classify_decision). Even though there is only one tool, the name is conventional and consistent with common MCP naming styles.
A single tool feels thin for most servers, and this one is no exception. However, the narrow scope of 'advisory classification only' makes the low count somewhat reasonable, but it remains on the borderline.
The tool fully covers its stated purpose of returning an advisory, confidence-gated route for a bounded decision. The explicit note that it never executes the route defines the boundary clearly, so there are no obvious missing operations within that scope.