A
licenseNot graded
qualityB
maintenanceConnects AI coding agents to the Jev decision model, enabling fast and cheap structured decisions such as task classification, strategy selection, complexity rating, and escalation decisions.
MIT
Open Jev Bridge
by louis-szeto
Related Servers
Alternatives to Open Jev Bridge
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityBmaintenanceEnables delegating bounded tasks from Codex to Claude Code, including read-only reviews, isolated branch edits, long-running background work, and approval handling.185 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects Claude Code to local Jupyter kernels for code execution, kernel management, and notebook execution, with security gating and output capture.PolyForm Noncommercial 1.0.0
- FlicenseBqualityNot gradedmaintenanceBridges Claude Code to a Cloud Orchestrator API, providing access to multi-AI consensus, web search, code execution sandboxes, long-term memory, knowledge graphs, deployment management, and 20+ integrated AI and developer tools.28-
- AlicenseAqualityCmaintenanceRoutes every Claude Code/Hermes prompt through a local LLM planner and Open-Jev probe, injecting calibrated probability context while failing open if local services are unavailable.4MIT
TDQS
B3.4/5.0
Scored across 14 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: from checking claims (belay) to ranking candidates (rerank) to validating queries (query). While some overlap in concept (compare vs decide vs verify), the descriptions clearly delineate their specific roles and inputs, leaving no ambiguity about which tool to use.
Naming Consistency5/5
All tools follow the consistent pattern 'system_one_' + a verb in lowercase snake_case (e.g., system_one_belay, system_one_compare). The prefix groups them coherently, and the verb accurately reflects each action, making the naming predictable and easy to navigate.
Tool Count5/5
With 14 tools, the server is well-scoped for a specialized verification and analysis system. Each tool addresses a distinct aspect of the domain (e.g., extraction, classification, reranking, review), and none feel redundant or extraneous. The count fits comfortably within the ideal range.
Completeness5/5
The tool surface covers a comprehensive set of operations for a safety-focused analysis server: status checking, raw queries, extraction, comparison, verification, classification, ranking, screening, review, and gate decisions. There are no obvious missing lifecycle operations, and the domain is not one that requires CRUD-style updates or deletions.
Maintenance
ActivityMaintained
ResponsivenessNo issues