io.github.us-all/dbt

MCPcommunity
v1.0.3io.github.us-allUnknownUpdated 1mo agonpmGitHub

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

dbt MCP server — , , , , plus DQ result tables (BigQuery / Postgres) behind one stdio MCP. Built on . A read-only window into your dbt project for LLM clients. No triggering — just deep introspection, run-history analysis, source freshness, per-column test coverage, lineage walks, and (if you have a custom DQ result table) historical check trends and Tier SLA status. For DAG triggering / run…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.us-all
LicenseUnknown
Version1.0.3
Sourcemcp-registry
npm@us-all/dbt-mcp
GitHubus-all/dbt-mcp-server
Trust Status
A
95/100Trusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
✓npm provenance (Sigstore)+5/5
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 241e0ad
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv1.0.3 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

dbt MCP server — , , , , plus DQ result tables (BigQuery / Postgres) behind one stdio MCP. Built on . A read-only window into your dbt project for LLM clients. No triggering — just deep introspection, run-history analysis, source freshness, per-column test coverage, lineage walks, and (if you have a custom DQ result table) historical check trends and Tier SLA status. For DAG triggering / run history / log tails, install the companion @us-all/airflow-mcp alongside. 27 tools across 3 categories…

Keywords
mcp