Skip to main content
Glama
Omniaeye
by Omniaeye

Related Servers

Alternatives to OMNIA MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to get fast, calibrated typed decisions from a shared Laya decision service: classifying text, scoring rubrics, answering batches of yes/no checks, and running question packs. Exposes guards and tool-call helpers that gate proposed tool calls, screen tool results for injected instructions, check replies and input for leaks or jailbreaks, and validate individual form fields and whole submissions with pass, fix, review, or reject outcomes.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to evaluate single records or batches with dynamically authored typed questions, returning structured decisions and probabilities.
      25 PyPI
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables typed decisions (yes/no, choice, score) with transparent preflight checks, honest confidence reporting, and health monitoring.
      87 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents and services to ask small decision models typed questions about text, JSON, images, or video, returning labels, scores, or yes/no answers over MCP tools or a Jev-compatible HTTP API.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Provides coding agents and CI with a typed decision layer that sends bounded state and questions to Jev, then returns deterministic actions for review, risk assessment, requirement checks, and verification.
      9
      347 npm
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct: evaluate handles single requests, evaluate_batch handles groups, get_decision reads persisted results, and capabilities reports configuration. There is minor potential confusion between evaluate and evaluate_batch, but the descriptions clarify the difference.

    Naming Consistency3/5

    Most tools follow an omnia_<verb>_<object> pattern, but omnia_capabilities is a bare noun and omnia_evaluate lacks an object, breaking the otherwise consistent style. All names share the omnia_ prefix and snake_case, so the inconsistency is moderate rather than chaotic.

    Tool Count5/5

    Four tools is a well-scoped size for this server's purpose. Each tool covers a distinct operation—single evaluation, batch evaluation, reading decisions, and capability reporting—without unnecessary bloat.

    Completeness4/5

    The surface covers the core evaluation lifecycle: evaluate single, evaluate batch, and read persisted decisions, plus capability discovery. A listing or search over persisted decisions would round it out, but the existing tools support the primary workflow without dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues