A
licenseB
qualityB
maintenanceConnects Claude Code and Codex to Jev-compatible System One services for context compaction, completion verification, and decision tasks like screening, classification, and gating.
14
MIT
open-jev
by yogeshvar
Related Servers
Alternatives to open-jev
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceBridges Claude with a local Ollama coding model, letting Claude delegate bounded implementation tasks to the local model while retaining reasoning, review, and safety enforcement.122,285 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code or any MCP client to ask TypeSafe's Jev for calibrated, typed judgments (probabilities, choices, scores) instead of prose, with local caching and cost tracking.1MIT
- FlicenseNot gradedqualityBmaintenanceEnables OpenCode to route simple, medium, and complex requests through planner-critic-solver logic, with local token-saving cache and compression, and optional delegation of heavy math or science tasks to a GPU-backed service.-
- AlicenseAqualityBmaintenanceEnables frontier coding agents to delegate routine probabilistic judgments to TypeSafe Jev, providing calibrated triage signals for failures, attempts, completion, context ranking, findings, risk, and generic evidence-grounded questions.7MIT
- AlicenseNot gradedqualityBmaintenanceProvides Claude Code with local-first multimodal semantic search across documents, code, images, and video, plus multi-engine web research with active counter-evidence hunting and source-verified, extract-only briefings.4AGPL 3.0
TDQS
A3.7/5.0
Scored across 4 tools
Disambiguation4/5
Most tools are clearly distinct: health checks availability, plan generates a probe, and analyze runs the full pipeline. The slight overlap is between ask and analyze, since both involve asking the Open-Jev server questions, but ask is a direct query about a state while analyze runs the complete planner-to-Jev flow.
Naming Consistency5/5
All tool names follow the same jev_<verb> pattern with clear verbs: ask, plan, analyze, and health. This makes the toolset highly predictable and easy for an agent to navigate.
Tool Count5/5
Four tools is well-scoped for this focused server. Each tool covers a meaningful operation without redundancy or unnecessary surface area.
Completeness4/5
The core workflows are covered: checking health, inspecting a generated plan, asking direct questions, and running the full analysis pipeline. A minor gap is that there is no explicit tool to run a previously generated probe exactly, though analyze effectively covers the end-to-end use case.
Maintenance
ActivityMaintained
ResponsivenessNo issues