Skip to main content
Glama
WayneCommand

laya-mcp

by WayneCommand
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to laya-mcp

No user-submitted related servers found.

    Related Servers

    • decidealot

      psyb0t
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local typed decision-making over MCP Streamable HTTP, running Laya and Von models to turn arbitrary state into choice, score, and yes/no answers with probabilities.
      3
      Do What The F*ck You Want To Public

    • 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.
      190 PyPI
      2
      Apache 2.0

    • Laya MCP Server

      AIAI-Laboratory
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run local, CPU-only inference for decision tasks such as choosing among labels, estimating yes/no probability, and scoring ordered descriptions. Exposes these capabilities through MCP tools, REST/Swagger endpoints, and a browser test console without GPUs, paid APIs, or databases.
      Apache 2.0

    • decision-lite

      cckyros
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that answers typed noul/choice/score questions about a given state with probability distributions and confidence, for routing, escalation, and gating decisions. It runs on pluggable backends (local Needle 3 or Laya models, or any OpenAI-compatible endpoint) and logs every decision so recorded ground truth can be used to track calibration.
      3
      MIT
    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.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: decide variants differ by input shape (typed questions, single statement, many labels), while route_request, list_presets, describe_questions, and server tools are separate concerns. However, should_escalate and decide_yes_no both produce gate-like boolean verdicts, and an agent could confuse when to use one versus the other despite the descriptions.

    Naming Consistency4/5

    All names use snake_case, and most follow a predictable verb_noun or verb pattern (decide_yes_no, decide_shortlist, route_request, list_presets, describe_questions, preload_warmup). Minor deviations are should_escalate (modal verb phrase) and server_status (noun phrase), but these are still readable and consistent enough.

    Tool Count5/5

    Nine tools is well-scoped for a decision/inference server. The surface covers decision making, routing, preset introspection, and server health without excessive redundancy.

    Completeness4/5

    The set covers core decision workflows (single yes/no, typed questions, shortlisting), routing, preset listing/description, status, and warmup. Minor gaps include no explicit tool to inspect or configure checkpoints beyond status, and no direct way to answer multiple independent statements in one call, but these are workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources