Dax Query MCP Server

dax-query-mcp PyPI v0.2.8

Published by wes-stone — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 6

high Shell/command execution in server code (dax_query_mcp/copilot_guard.py)MTC-SRC-002

In the server's implementation (`dax_query_mcp/copilot_guard.py:153`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ry: completed = subprocess.run( command, cwd=repo_root, capture_output=True,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dax_query_mcp/copilot_guard.py

high Shell/command execution in server code (dax_query_mcp/executor.py)MTC-SRC-002

In the server's implementation (`dax_query_mcp/executor.py:236`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: table() completed = subprocess.run( [ az_executable, "account", "get-acc

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dax_query_mcp/executor.py

high Shell/command execution in server code (dax_query_mcp/mcp_server.py)MTC-SRC-002

In the server's implementation (`dax_query_mcp/mcp_server.py:224`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: result = subprocess.run( ["git", "rev-parse", "--short", "HEAD"], cwd=repo_root,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dax_query_mcp/mcp_server.py

high Shell/command execution in server code (dax_query_mcp/scaffold.py)MTC-SRC-002

In the server's implementation (`dax_query_mcp/scaffold.py:187`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: e() completed = subprocess.run( [ az_executable, "account",

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dax_query_mcp/scaffold.py

low Shell/command execution in packaging/dev tooling (tests/test_mcp_server.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_mcp_server.py:2146`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: : str(script_path)} exec(script_path.read_text(encoding="utf-8"), namespace) monkeypatch.setattr("sys.argv", ["

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_mcp_server.py

low Shell/command execution in packaging/dev tooling (tests/test_scaffold.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_scaffold.py:218`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: t(encoding="utf-8") exec(script, namespace) with pytest.raises(RuntimeError, match="dataset-only executeQueries

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_scaffold.py

Tools 50

Each tool and what it can reach — statically extracted from the published source.

  • export_to_csvnetwork egress
  • check_ai_readinessno sensitive capability
  • check_context_stalenessno sensitive capability
  • clear_workstationno sensitive capability
  • copy_to_clipboardno sensitive capability
  • create_query_packno sensitive capability
  • describe_query_packno sensitive capability
  • diff_data_dictionaryno sensitive capability
  • export_query_packno sensitive capability
  • export_workstationno sensitive capability
Show 40 more tools ↓
  • generate_data_dictionaryno sensitive capability
  • get_connection_contextno sensitive capability
  • get_context_bundleno sensitive capability
  • get_data_dictionaryno sensitive capability
  • get_filter_suggestionsno sensitive capability
  • get_measure_detailno sensitive capability
  • get_query_builderno sensitive capability
  • get_query_builder_schemano sensitive capability
  • get_relationshipsno sensitive capability
  • get_schemano sensitive capability
  • get_table_detailno sensitive capability
  • inspect_connectionno sensitive capability
  • inspect_model_metadatano sensitive capability
  • list_connectionsno sensitive capability
  • list_queriesno sensitive capability
  • list_query_packno sensitive capability
  • list_validated_queriesno sensitive capability
  • list_workstationno sensitive capability
  • merge_data_dictionaryno sensitive capability
  • probe_tmschema_capabilitiesno sensitive capability
  • quick_chartno sensitive capability
  • remove_from_workstationno sensitive capability
  • review_data_dictionary_updateno sensitive capability
  • run_ad_hoc_queryno sensitive capability
  • run_connection_queryno sensitive capability
  • run_named_queryno sensitive capability
  • save_query_builderno sensitive capability
  • save_query_to_packno sensitive capability
  • save_to_workstationno sensitive capability
  • save_validated_queryno sensitive capability
  • scaffold_dax_workspaceno sensitive capability
  • scaffold_power_queryno sensitive capability
  • scaffold_streamlit_appno sensitive capability
  • search_columnsno sensitive capability
  • search_connection_contextno sensitive capability
  • search_measuresno sensitive capability
  • search_validated_queriesno sensitive capability
  • server_infono sensitive capability
  • validate_query_libraryno sensitive capability
  • validate_query_packno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.8 latest A 93/100 6 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/dax-query-mcp/badge.svg)](https://mcptrustchecker.com/registry/dax-query-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/dax-query-mcp"><img src="https://mcptrustchecker.com/registry/dax-query-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/dax-query-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan dax-query-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools