Skip to main content
Glama
ycy726619

codex-choice-mcp

by ycy726619

Related Servers

Alternatives to codex-choice-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Serves three judgment tools over MCP stdio that return typed answers — yes/no, choice, and score — with calibrated probabilities instead of prose. It runs fully offline by default, requiring an explicit live provider and credential before any state leaves the host.
      66 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes three typed-judgment tools over MCP stdio, letting a host ask yes/no, choice, and score questions and receive calibrated probabilities rather than prose. Runs entirely offline against a mock provider by default, with live TypeSafe or OpenRouter routes and a disclosed, per-feature egress contract when explicitly enabled.
      66 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A minimal, zero-dependency MCP server that enables defining and running tools over stdio transport, without extra features like HTTP or resources.
      90 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a shared MCP SDK wrapper for building MCP servers with stdio transport, tool registration, JSON-safe responses, and environment helpers.
      43 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes three stdio tools that ask typed judgment questions — yes/no, choice, and score — and return calibrated probabilities instead of prose, over any MCP-speaking host. Runs on an offline mock by default, with every network transmission named before it happens and credential-gated live routes to TypeSafe or OpenRouter.
      66 npm
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion between tools. The agent can clearly identify its purpose.

    Naming Consistency5/5

    With a single tool, there is no inconsistency to evaluate. The name 'request_choice' follows a clear verb_noun pattern.

    Tool Count3/5

    The tool count of 1 is borderline thin for a server. While it may be acceptable for a very focused utility, it lacks breadth for more complex choice management scenarios.

    Completeness4/5

    The tool covers the core action of requesting a choice and returning stable option IDs. However, missing capabilities like listing, updating, or canceling choices suggest minor gaps for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues