Skip to main content
Glama
louis-szeto

Open Jev Bridge

by louis-szeto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Open Jev Bridge

No user-submitted related servers found.

    Related Servers

    • jev-bridge

      lhviet
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      MIT

    • Jupiter Controller MCP

      nufelroknidev
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects 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

    • open-jev

      yogeshvar
      A
      license
      A
      quality
      C
      maintenance
      Routes 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.
      4
      MIT

    • harness-bridge

      rbutera
      A
      license
      A
      quality
      A
      maintenance
      Bridges Claude Code and OpenAI Codex through MCP, allowing cross-harness querying, code review, explanation, and implementation delegation.
      6
      5 npm
      1
      MIT

    • codex-app-server-mcp

      4714407
      A
      license
      A
      quality
      B
      maintenance
      Bridges MCP clients such as Claude Code and Cursor to independent Codex app-server sessions, letting them start, poll, steer, review, compact, cancel, and answer prompts for asynchronous Codex tasks over local stdio or a remote authenticated WebSocket. Runs read-only by default, with workspace-write sandboxing only when a user explicitly enables it, and reports job status, model listing, and progress back to the client.
      10
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources