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
      33 PyPI
      6
      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.
      105
      MIT
    • A
      license
      B
      quality
      B
      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.
      25
      205 PyPI
      2
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to audit dbt project health, profile warehouse data, detect schema drift, and auto-generate documentation through natural language. It combines coverage scoring, test suggestions, and non-destructive YAML updates in a single MCP server.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to audit project health, profile data, detect schema drift, and auto-generate documentation for dbt projects through natural language. It also provides coverage scoring, test suggestions, and safe schema.yml updates via MCP.
      -

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: list_tables for discovery, investigate for baselines, watch for drift detection, and reconcile for source/target checks. The main overlap is among check, watch, and verify, which all perform anomaly detection and can return pass/fail gates, but the descriptions explicitly distinguish their persistence and read-only semantics.

    Naming Consistency3/5

    Names are readable and consistently snake_case, but conventions are mixed: list_tables uses verb_noun, several tools are bare verbs (check, investigate, watch, verify, reconcile), and two are nouns (history, status). The set is understandable but not predictably patterned.

    Tool Count5/5

    Eight tools is well-scoped for a data monitoring server, and each tool appears to earn its place across discovery, baseline creation, detection, gating, history, reconciliation, and status.

    Completeness4/5

    The core lifecycle is covered: discover tables, establish baselines, detect anomalies, run gates, inspect history, reconcile outputs, and check status. The notable gap is the lack of an accept-baseline tool even though multiple descriptions reference `scherlok accept` for resolving persistent CRITICAL anomalies, forcing a human/CLI workaround.

    Maintenance

    ActivityActive
    ResponsivenessLimited data