Skip to main content
Glama
thyn-ai

SQAI

Official
by thyn-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to SQAI

No user-submitted related servers found.

    Related Servers

    • governed-rag-mcp

      Rlealbarili
      A
      license
      A
      quality
      B
      maintenance
      Provides governed retrieval over MCP with hybrid search, strict confidence gating, and access control, exposing three read-only tools.
      3
      Apache 2.0

    • telemetry-mcp

      selamy-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for querying telemetry data from configurable backends. Provides tools to list sources, describe schemas, run bounded queries, and compute aggregates.
      MIT

    • Read-only Analytics MCP Server

      Catom8
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to execute validated read-only warehouse queries through a guarded SQL API, with enforced row limits and secret-safe audit metadata.
      MIT

    • people-ai

      stellal7
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables governed interaction with synthetic people data through MCP tools, providing per-caller scoped access, semantic-layer metrics, and read-only SQL with authorization checks.
      MIT

    • damoxing-datasource-mcp

      xiaochen201807
      F
      license
      Not graded
      quality
      A
      maintenance
      Provides a stdio MCP server for Codex to inspect and query configured datasources, with tools for health checks, read-only queries, metadata, and fixed physical sessions with audit trails.
      16 npm
      -
    • MCP DB Gateway by altsys

      MCP DB Gatewayofficial

      altsys
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides governed, read-only PostgreSQL access for AI agents via MCP. Enforces schema/table allowlists, query limits, and audit events.
      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

    A4.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: queryData executes, explainQuery dry-runs, getResult retrieves stored results, and listSources discovers sources/capabilities. Even the closely related queryData and explainQuery are unambiguously separated by execution versus planning. No two tools appear to do the same thing.

    Naming Consistency5/5

    All four tool names follow the same camelCase verb_noun pattern: queryData, getResult, explainQuery, listSources. The naming is uniform and predictable, making the API easy to navigate. There are no mixed conventions or vague verbs.

    Tool Count5/5

    Four tools is a well-scoped count for a read-only query and computation server. Each tool covers an essential stage of the workflow: discover, explain, execute, and retrieve. No tool feels redundant or missing from the core flow.

    Completeness5/5

    The tool surface fully covers the stated purpose: discovering data sources and computation modules, validating queries before execution, executing queries, and retrieving truncated results. The read-only nature means CRUD operations are not expected, so there are no obvious dead ends. The workflow is cohesive and self-contained.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources