Skip to main content
Glama
fuleinist

laya-mcp

by fuleinist

Related Servers

Alternatives to laya-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides fast, offline typed decision tools (classify, score, check, triage) to agents via the Model Context Protocol, enabling safe local inference across 100+ languages with calibrated confidence and no text generation.
      8
      80 PyPI
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables agents to make calibrated decisions via six MCP tools for classification, relevance ranking, claim verification, action gating, next-step control, and model listing, using Jev's System One model without generating text.
      6
      24
      MIT
    • 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.
      7
      MIT

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools have distinct purposes, but laya_route and route_step clearly overlap as routing tools, even though the descriptions try to differentiate them. laya_triage and laya_classify could also be confused in some contexts, though the batch-vs-single distinction helps.

    Naming Consistency3/5

    Six tools follow a consistent laya_<verb> pattern, but route_step and verify_step break the convention by dropping the prefix and using verb_noun instead. The names are readable and meaningful, but the mixed style is noticeable.

    Tool Count4/5

    Eight tools is within the ideal range and the set covers the major decision-engine capabilities. The main redundancy is the two routing tools, which slightly weakens the 'every tool earns its place' criterion but does not make the set bloated.

    Completeness4/5

    The tool surface covers the core decision, classification, routing, safety, verification, and health operations well. Minor gaps exist, such as no tool for refitting temperatures or managing the catalog, but these are not blocking for the primary inference and advisory workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive