Skip to main content
Glama

Related Servers

Alternatives to scherlok

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Agentic data quality MCP server — runs structured validation rules against warehouses (DuckDB, BigQuery, Athena, Databricks, Postgres), diagnoses failures with LLM root cause analysis, and proposes SQL remediations. Full audit trail of every AI decision.
      6
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      AI-driven MCP server that audits, profiles, detects schema drift, and auto-generates documentation for dbt projects, enabling natural language interaction with your dbt project's health.
      134
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server for data quality that finds suspicious data, explains findings with evidence, tracks drift, and supports human-approved, reversible repair workflows. Deterministic by default, with AI optional.
      108 PyPI
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Open-source agentic schema layer. Define metrics once in YAML, query governed data from any warehouse (Snowflake, BigQuery, Databricks, PostgreSQL, DuckDB) via MCP.
      28
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server that provides comprehensive dbt project quality assessment for any GitHub repository, enabling AI agents to analyze dbt models, check metadata coverage, and map data lineage.
      9
      MIT

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: check is CI pass/fail, history retrieves past anomalies, investigate profiles and sets baseline, list_tables discovers tables, status gives health, watch detects anomalies against baseline. No overlap in functionality.

    Naming Consistency4/5

    All tool names are short, imperative verbs except for 'history' which is a noun. However, the naming is consistent in style and easy to understand, with no mixing of conventions like camelCase or snake_case.

    Tool Count5/5

    6 tools is appropriate for a data quality monitoring server. Each tool covers a necessary step in the workflow (discovery, profiling, detection, CI, history, status) without unnecessary bloat.

    Completeness4/5

    The tool set covers the core monitoring lifecycle: table discovery, profiling, baseline setting, anomaly detection, CI check, history, and status. Minor gaps exist, such as no tool for resetting baselines or managing anomalies, but these are manageable.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week