Skip to main content
Glama

Related Servers

Alternatives to jev-delegate

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to obtain probabilistic decisions from Jev AI via OpenRouter for classification, scoring, and validation, with tools like jev_check, jev_classify, jev_score, and jev_evaluate.
      5
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables IBM Bob to retrieve only task-relevant workspace files by classifying them with Jev, reducing context bloat and Bobcoins usage. It exposes tools for ranked file retrieval, file content access, workspace listing, and workspace summaries.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Connect AI agents to Jev AI (jev-ai.pro) for classification, scoring, yes/no checks, advisory action assessment, batched typed decisions and saved judges. Returns structured answers and probabilities using your Jev AI API key.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and local workflows to run Jev-powered tools that judge speeches line by line, audit drafts against goals, bisect hard-to-test bugs, simulate common-sense physics, score note pairs, and ask arbitrary typed questions cheaply.
      7
      12 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Codex to rank available tools and skills, rerank code and documentation search results, and triage saved output artifacts using Jev-based relevance scoring while leaving final decisions to Codex.
      1
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to query files, logs, and search results through TypeSafe Jev's typed, probabilistic answers, so they retrieve only the needed conclusion instead of raw context. Supports classification, scoring, yes/no checks, extraction, page ranking, and injection screening.
      11
      392 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are completely distinct: one focuses on searching and ranking relevant matches from raw search results, while the other assigns labels to items. There is no overlap in purpose, and an agent can easily select the correct tool based on the task.

    Naming Consistency4/5

    Both tools use an imperative verb phrase, but 'search_and_rank' is a compound verb while 'classify_items' follows a verb_noun pattern. The slight inconsistency is minor and does not hinder readability, but a more uniform pattern (e.g., 'search_and_rank_items') would be ideal.

    Tool Count3/5

    With only two tools, the server feels thin for a delegation service. However, the narrow scope of search ranking and classification justifies a small count, making it borderline rather than excessive. Each tool serves a clear purpose, so the count is acceptable but leaves little room for additional functionality.

    Completeness4/5

    The tool surface covers the core functions implied by the server name: search-and-rank and classification. Minor gaps exist (e.g., no summarization or generation tool), but the stated purpose is well-addressed, and an agent can complete common tasks without hitting dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues