Skip to main content
Glama
dockndevai

mcp-laya

by dockndevai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-laya

No user-submitted related servers found.

    Related Servers

    • laya-mcp

      fuleinist
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to run fast, local, non-autoregressive System-1 decisions on text, including classification, triage, routing, and safety gating, via six typed tools with probabilistic outputs.
      20
      8
      Apache 2.0

    • poordjaevin

      Icaro0310
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes local MCP tools for typed, calibrated LLM decisions — gating risky actions, yes/no judging, classification, ordinal rating, and multi-question decisions in one pass. Runs on the model Devin's CLI already provides via ACP (or a fully offline local backend), so agents get calibrated confidence with no extra API key, no Ollama, and no waitlist.
      137 PyPI
      6
      MIT

    • Evidence Gate

      AnotherMeatsack
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to run local, model-backed decisions on short passages and routing choices, and to check whether exactly supplied text supports a scientific claim, returning the full probability distribution, review-policy status, and provenance details. All evaluation stays on the local machine with no cloud inference, and flagged results are surfaced for human review rather than treated as conclusions.
      MIT

    • Laya Agent Kit

      Maxwell00000086
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to perform typed decisions (choice, score, noul) over text, emails, tickets, or JSON documents, with automatic language routing and source ranking across 100+ languages via a single forward pass.
      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.5/5.0

    Scored across 8 tools

    Disambiguation3/5

    classify, score, and check are single-question wrappers around decide's choice/score/noul modes, so an agent choosing between decide and a specialized tool may face ambiguity for a one-off task. Their descriptions clearly separate the single-vs-multiple use cases, but the underlying semantics overlap.

    Naming Consistency4/5

    All tool names are lowercase and start with an imperative verb, with compound names following verb_noun (detect_language, explain_routing, list_models). The single-word verbs (decide, classify, score, check, triage) are a minor stylistic deviation from the compound pattern but remain predictable.

    Tool Count4/5

    Eight tools is a reasonable size for a decision-model server and stays inside the ideal 3-15 range. The count is slightly padded, though, because classify/score/check are specialized versions of decide's three question types.

    Completeness4/5

    The set covers general and specialized decisions, ready-made triage presets, language detection, routing explanation, and model listing—no obvious dead ends for inference workflows. Minor gaps include no queryable preset list or way to register custom presets, but these can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources