Skip to main content
Glama
launchables-ai

Launchables MCP server

Official

Related Servers

Alternatives to Launchables MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to obtain typed, probabilistic decisions from text or structured state and up to four images—choosing among labeled options, scoring on ordered scales, and estimating whether propositions are true—for routing, triage, moderation, risk scoring, and similar agent workflows.
      5
      0
      MIT
    • 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
      C
      maintenance
      Enables agents to delegate decisions to a configurable model, returning recommended choices with percentage scores and profile-based routing.
      12 npm
      MIT
    • 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
      Not graded
      quality
      D
      maintenance
      Enables AI clients to run read-only yes/no checks, classifications, and ordered scores with probabilities, supporting triage, routing, sentiment, and lead-fit decisions through hosted or self-hosted MCP tools.
      41 npm
      AGPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Lets MCP clients ask typed questions — yes/no, choice, or score — about structured state, including images, and receive calibrated probabilities from System One decision models such as TypeSafe Jev and Cloudflare Clef. Supports TypeSafe, OpenRouter, and local providers selectable per request, with input validation and cost reporting.
      6
      392 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list_models enumerates available models, health checks API availability, and decide performs the core decision operation. There is no overlap between discovery, status, and inference.

    Naming Consistency3/5

    All names are snake_case and readable, but the conventions are mixed: list_models is verb_noun, health is a bare noun, and decide is a bare verb. The pattern is not predictable across tools.

    Tool Count4/5

    Three tools are reasonable for a narrow decision API: discovery, health, and inference. The surface is small but each tool earns its place, though it is on the thin side.

    Completeness4/5

    The core lifecycle is covered: list models, check health, and run decisions with multiple questions in one call. Minor gaps exist, such as no explicit usage/billing or model-detail endpoint, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues