← Index

io.github.us-all/dbt

io.github.us-all/dbtv1.0.7Databases

dbt MCP — manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres)

In-path gate · all MCP tools

Using io.github.us-all/dbt in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-08-12 14:50 UTC
screened 2026-07-03tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidenceNo malicious instructions foundvia static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - Still current: the description we screened is unchanged, re-checked against the registry

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-05).

Contracts can change after screening, with no version bump. The gate pins io.github.us-all/dbt’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-us-all-dbt)](https://mcpindex.ai/server/io-github-us-all-dbt)
HTML
<a href="https://mcpindex.ai/server/io-github-us-all-dbt"><img src="https://mcpindex.ai/api/v1/badge/io-github-us-all-dbt" alt="mcpindex verdict" height="20" /></a>
Environment variables
DBT_PROJECT_DIR
required

Path to dbt project root (where dbt_project.yml lives).

DBT_TARGET_DIR

dbt target dir for manifest.json/run_results.json (default: $DBT_PROJECT_DIR/target).

DBT_RUN_HISTORY_DIR

Optional dir for archived run_results.json history (glob-scanned).

DQ_BACKEND

DQ result table backend: 'bigquery' (default) or 'postgres'.

DQ_RESULTS_TABLE

Fully qualified DQ checks table, e.g. 'project.data_ops.quality_checks'.

DQ_SCORE_TABLE

Fully qualified DQ score-daily table, e.g. 'project.data_ops.quality_score_daily'.

GOOGLE_APPLICATION_CREDENTIALS

Service account key path for BigQuery (ADC fallback supported).

BQ_PROJECT_ID

Explicit BigQuery project ID for DQ queries.

PG_CONNECTION_STRING
secret

Postgres connection string when DQ_BACKEND=postgres.

DBT_ALLOW_WRITE

Reserved for future write tools. Default read-only.

DQ_SCHEMA

DQ result-table schema preset: 'generic' (default) or 'us-all'. Use DQ_COL_* env vars to override individual columns on top of the preset.

DQ_COL_RUN_AT

Override for the timestamp/date column on the DQ checks table. Default depends on DQ_SCHEMA preset.

DQ_COL_CHECK_TYPE

Override for the check-type column on the DQ checks table. Default 'check_type'.

DQ_COL_STATUS

Override for the status column on the DQ checks table. Default 'status'.

DQ_COL_DATASET

Override for the dataset/source column on the DQ checks table. Default depends on preset.

DQ_COL_TABLE_NAME

Override for the table/target-name column on the DQ checks table. Default depends on preset.

DQ_COL_SEVERITY

Override for the severity/dimension column on the DQ checks table. Default depends on preset.

DQ_COL_FAILURE_COUNT

Override for the numeric failure-count column on the DQ checks table. Default depends on preset.

DQ_COL_MESSAGE

Override for the message column on the DQ checks table. Default depends on preset.

DQ_COL_CHECK_NAME

Override for the check_name column on the DQ checks table. Set to 'none'/'null'/'-' to synthesize check_name from check_type and table_name.

DQ_COL_SCORE_DATE

Override for the date column on the DQ score-daily table. Default depends on preset.

DQ_COL_SCOPE

Override for the scope column on the DQ score-daily table. Set to 'none'/'null'/'-' if the table has no per-scope rollup.

DQ_COL_TIER

Override for the tier column on the DQ score-daily table. Set to 'none'/'null'/'-' if the table has no tier dimension.

DQ_TIER1_TARGET_PCT

When no tier column is configured (us-all preset or DQ_COL_TIER=none), the overall_score threshold dq-tier-status compares against (default 99.5). Superseded by DBT_SLA_CONFIG_PATH tier_sla.1 if both are set.

DBT_SLA_CONFIG_PATH

Optional path to a YAML file that defines tier_sla (per-tier overall_score targets) and dbt_sla (test/freshness pass rates). When set, dq-tier-status and dq-tier-by-source read tier targets from this file, and dbt-sla-status compares run_results / sources pass rates against dbt_sla.test_pass_pct / freshness_pass_pct. Mtime cached.

DBT_TOOLS

Comma-separated category allowlist (dbt,quality,meta).

DBT_DISABLE

Comma-separated category disablelist.

MCP quality score · maturity, not trust · methodology
freshness
24
completeness
10
installability
25
documentation
15
stability
10
Alternatives in Databases