Skip to main content
Glama
ChristofMilius

openjev-router

by ChristofMilius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to openjev-router

No user-submitted related servers found.

    Related Servers

    • kev-mcp

      Busy-Office
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a locally running Kev decision model through MCP tools, returning calibrated probabilities for typed questions such as yes/no, choice, and score.
      Apache 2.0

    • llmstudio-mcp

      dam2452
      F
      license
      A
      quality
      C
      maintenance
      MCP server that connects LLM agents to a local LM Studio instance, enabling model management, OpenAI-compatible chat completions, text completions, and embeddings through a set of tools.
      9
      1
      -

    • mcp-confidence

      shaxzodbek-uzb
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to route responses as accept, verify, or ask-a-human based on token logprobs, and provides an MCP server for delegating generation to local models with confidence bands.
      MIT

    • jev-super-agent

      Kadihx
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to make offline, zero-cost decisions using schema-safe Choice/Score/Noul primitives, a confidence gatekeeper, planning, adversarial red-teaming, research, and RLVR-based self-improvement via 21 MCP tools.
      24
      2
      MIT

    • laya-mcp

      PerryLink
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides an MCP interface to the Laya decision model, enabling typed queries (yes/no, multiple choice, score) with preflight token-budget reporting, honest confidence calibration, and structured error handling.
      490 PyPI
      1
      Apache 2.0
    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

    A3.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: decision_status reports system state, while the three decide_* tools handle different decision types (choice among options, binary assertion, and tiered scoring). No overlap or ambiguity between them.

    Naming Consistency4/5

    Three tools follow the consistent 'decide_' prefix with action verbs, but decision_status deviates with a noun-based name. This is a minor inconsistency, but the pattern is still recognizable.

    Tool Count5/5

    With 4 tools, the server is well-scoped for a decision-routing purpose. Each tool covers a necessary aspect without redundancy or bloat.

    Completeness4/5

    The surface covers status, choice selection, boolean judgment, and scoring, which aligns with the server's purpose. A possible gap is a tool for explaining or justifying decisions, but the provided functionality is solid.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources