Skip to main content
Glama
Sign In
Zelinqa MCP

Zelinqa MCP

Official
by Zelinqa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Zelinqa MCP

No user-submitted related servers found.

    Related Servers

    • Mellix MCP server

      Mellix MCP serverofficial

      mellix-ai
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to send situations and typed questions to Myles and receive calibrated probabilities, picks, and escalation guidance for routing, risk flagging, approvals, policy checks, and rating tasks.
      3
      471 npm
      Apache 2.0

    • voice-gate

      beejsbj
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to submit completed speech or typed text to a self-hosted decision engine and receive judgments such as ordinary speech, command, retained thought, uncertainty, or no action, along with session and decision inspection.
      3
      MIT

    • askhuman

      alevtdagen
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP hosts to request human input for decisions, approvals, clarifications, and notifications, with tools for asking, waiting, retrieving responses, and canceling requests through configured channels.
      Apache 2.0

    • mcp-surveys

      EzzySoft
      A
      license
      Not graded
      quality
      C
      maintenance
      Public MCP server for agent-created, human-friendly, short-lived surveys. Enables agents to ask structured questions and retrieve answers.
      2
      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.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clear distinct roles (start, status, feedback, forget, next_question), but adjust, add_context and next_question all send information 'without consuming a turn', creating subtle boundaries an agent could misselect between. The detailed descriptions largely resolve this.

    Naming Consistency4/5

    All names share a consistent zelinqa_ prefix and are readable, though there is minor mixing of verb forms (adjust, start, forget) with noun forms (status, feedback, next_question). The pattern is predictable enough.

    Tool Count5/5

    Seven tools is well within the ideal range and each maps to a distinct step in the conversation lifecycle. Nothing feels padded or missing at the count level.

    Completeness4/5

    The set covers the full guided-conversation lifecycle: start/recover, advance (next_question), inspect (status), enrich (adjust, add_context), report outcome (feedback), and release (forget). Minor gaps like an explicit conversation-list or end tool are workable around.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources