us-all/dbt-mcp-server (us-all/dbt-mcp-server) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
23 days ago

us-all/dbt-mcp-server

A read-only MCP server that exposes dbt project artifacts and data quality result tables (BigQuery/Postgres) to LLM clients, enabling deep introspection, run-history analysis, source freshness, test coverage, and lineage walks.

→ us-all/dbt-mcp-server· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

us-all

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configBQ_PROJECT_IDno Explicit BQ project (otherwise inferred from ADC)
configDBT_ALLOW_WRITEno Reserved for future write tools (none currently)
configDBT_DISABLEToggle with DBT_TOOLS=dbt (allowlist) or =quality (denylist).
configDBT_PROJECT_DIR/path/to/dbt-project \
configDBT_RUN_HISTORY_DIRno Optional dir for archived run_results.json history
configDBT_SLA_CONFIG_PATHDQ_TIER1_TARGET_PCT no Tier 1 SLA threshold for dq-tier-status when no tier column is configured (default 99.5). Superseded by tier_sla.1 if both are set.
configDBT_TARGET_DIRno Defaults to $DBT_PROJECT_DIR/target
configDBT_TOOLSToggle with =dbt (allowlist) or DBT_DISABLE=quality (denylist).
configDQ_BACKENDno bigquery (default) or postgres
configDQ_RESULTS_TABLEmy-project.data_ops.quality_checks \
configDQ_SCHEMAno generic (default) or us-all — base schema preset for the quality category
configDQ_SCORE_TABLEno FQN of the score-daily table; required for score-only tools
configDQ_TIER1_TARGET_PCTno Tier 1 SLA threshold for dq-tier-status when no tier column is configured (default 99.5). Superseded by DBT_SLA_CONFIG_PATH tier_sla.1 if both are set.
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPG_CONNECTION_STRING
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

27/27 tools missing one or more hints — dbt-list-models (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dbt-get-model (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dbt-list-tests (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +24 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

21/27 tools referenced in tests (78%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/us-all-dbt-mcp-server-e4rvas)](https://m8ven.ai/mcp/us-all-dbt-mcp-server-e4rvas)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3af1107534ad8c4bbb9e707ce1893e0bf95bbffa
code hash: 8a910e93c83c3da8d1c362274daf3174be8bda34a681e5a0901915e96d06d8e9
verified: 8/6/2026, 5:28:24 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client