Skip to main content
Glama
mekala27-45

readback

by mekala27-45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to readback

No user-submitted related servers found.

    Related Servers

    • dst by get-dst

      dstofficial

      get-dst
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query governed data warehouses through plain language, returning grounded answers with SQL, confidence grades, and signed receipts while enforcing access, testing, and audit controls.
      437 PyPI
      16
      Apache 2.0

    • Finance MCP Server

      DanieloTony
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an LLM to inspect a relational database schema and answer financial questions by running validated, read-only SQL queries against a synthetic SQLite dataset.
      MIT

    • mnemiq

      agenticfabriq
      A
      license
      A
      quality
      B
      maintenance
      Answers natural-language questions against Postgres, Oracle, Snowflake, Databricks, DuckDB and SQLite via db_read(question) and get_schema(), each separately grantable. The model only proposes SQL — shape, access, dialect and query plan are checked deterministically before any rows are read, and the server refuses rather than returning an unverified answer.
      3
      81
      Apache 2.0

    • metrics-mcp

      razornne
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to query curated metrics through a registry-backed semantic layer, preventing ad-hoc SQL and enforcing consistent definitions. Every numeric claim is verified against the underlying query result before it is allowed to be sent.
      4
      MIT

    • agentic-analytics-engine

      NirmalKumar31
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language-driven analytics over CSV/Parquet or built-in data by decomposing questions into analytical tasks, running them via deterministic DuckDB and SciPy tools, and publishing only claims verified against the underlying rows.
      MIT
    • Lagaam by lagaam-ai

      Lagaamofficial

      lagaam-ai
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to query Trino and Apache Pinot lakehouses under enforced governance, where every SQL statement is AST-validated, table-allowlisted, priced from the engine's own plan before it runs, and blocked or admitted against scan-byte and intermediate-row budgets. It also grounds agents with schema discovery tools, returns verified results with warnings instead of misleading answers, and records every tool call on an audit trail.
      3
      1
      Apache 2.0
    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/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct role in the workflow (orient via warehouses, find via search_catalog/lookup, inspect via describe, query via run_sql, cite via published, verify via readback), and descriptions explicitly state call order. The only soft overlaps are search_catalog also returning published manifest values and describe vs. search_catalog both surfacing definitions, but the ranked-search vs. exact-key distinction is articulated well enough to steer selection.

    Naming Consistency3/5

    Conventions are mixed: verb_noun for search_catalog and run_sql, bare verbs for describe and lookup, and nouns/adjectives for warehouses, published and readback. Names are individually readable and domain-idiomatic, but there is no predictable pattern an agent can generalize from.

    Tool Count5/5

    Seven tools is well within the sweet spot, and each one covers a genuine stage of the read-verify pipeline rather than duplicating another. Nothing looks like padding or an afterthought.

    Completeness4/5

    The lifecycle is covered end to end: discovery (warehouses, search_catalog, describe, lookup), retrieval (run_sql, published), and verification (readback). Minor gaps remain, such as no direct way to enumerate all tables or columns in a warehouse schema without first naming them through search, which forces extra round trips.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources