Skip to main content
Glama

Related Servers

Alternatives to aside-jev

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to obtain typed judgments from TypeSafe's Jev System One models, including yes/no probabilities, multiple-choice selections with distributions, and rubric-based scores, directly usable in code.
      5
      2
      AGPL 3.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agent skills to route state-evaluation requests to TypeSafe AI's Jev System One model, supporting typed questions, choice classification, binary probabilities, and rubric scoring with calibrated confidence.
      4
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables any agent to ask typed questions (Noul, Choice, Score) against Jev's decision model and receive structured answers with probabilities, confidence, and an auditable act/review/abstain decision.
      423 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to make fast, low-cost, typed decisions via a TypeSafe System One, providing routing, scoring, approval, and escalation through tools such as ask, choice, score, and noul.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to offload yes/no, multiple-choice, and scoring questions to TypeSafe's Jev, returning compact confidence-scored answers to save tokens and improve speed.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code agents to perform structured decision-making through TypeSafe Jev, supporting yes/no checks, route selection, scoring, and batched multi-question judgments with confidence values.
      1
      -

    TDQS

    C2.7/5.0

    Scored across 6 tools

    Disambiguation2/5

    Several tools have overlapping responsibilities: jev_choose and jev_step both involve selecting an action, while jev_validate and jev_step both claim to validate. The descriptions help somewhat, but an agent could easily pick the wrong tool when choosing, validating, or executing a step.

    Naming Consistency2/5

    All tools share a jev_ prefix, but the rest of the names follow no consistent pattern: single verbs like validate/choose, noun compounds like extension_status/system_one, and an inverted noun-verb in browser_run. This mixed style reduces predictability and makes the API harder to navigate.

    Tool Count4/5

    Six tools is a reasonable size for a Jev/Aside-focused server, covering validation, evaluation, browser execution, extension status, and action selection. The count is not bloated, though some tools could potentially be consolidated.

    Completeness3/5

    The core workflow areas are represented: validation, system-one assessment, browser automation, and status reading. However, there is no obvious way to list available app-owned action IDs or modify extension settings, and the relationship between choose/step/validate leaves some workflow gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues