databricks-mcp-genie
PyPI
v1.0.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for Databricks with enhanced Genie AI integration - natural language data analysis
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 − 8 = 92. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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.
In the server's implementation (`.claude/skills/document-skills/xlsx/recalc.py:31`): 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: sts(macro_dir): subprocess.run(['soffice', '--headless', '--terminate_after_init'], captu
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 .claude/skills/document-skills/xlsx/recalc.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/document-skills/docx/ooxml/scripts/pack.py:103`): 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: y: result = subprocess.run( [ "soffice", "--headless
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 .claude/skills/document-skills/docx/ooxml/scripts/pack.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/document-skills/docx/ooxml/scripts/validation/redlining.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: result = subprocess.run( [ "git", "di
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 .claude/skills/document-skills/docx/ooxml/scripts/validation/redlining.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/document-skills/pptx/ooxml/scripts/pack.py:103`): 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: y: result = subprocess.run( [ "soffice", "--headless
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 .claude/skills/document-skills/pptx/ooxml/scripts/pack.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/document-skills/pptx/ooxml/scripts/validation/redlining.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: result = subprocess.run( [ "git", "di
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 .claude/skills/document-skills/pptx/ooxml/scripts/validation/redlining.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/document-skills/pptx/scripts/thumbnail.py:219`): 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: o PDF...") result = subprocess.run( [ "soffice", "--headless", "--conver
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 .claude/skills/document-skills/pptx/scripts/thumbnail.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/webapp-testing/scripts/with_server.py:69`): 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: & process = subprocess.Popen( server['cmd'], shell=True, std
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 .claude/skills/webapp-testing/scripts/with_server.py
Each tool and what it can reach — statically extracted from the published source.
cancel_runno sensitive capabilitycreate_catalogno sensitive capabilitycreate_jobno sensitive capabilitycreate_schemano sensitive capabilitycreate_tableno sensitive capabilitydbfs_putno sensitive capabilitydelete_jobno sensitive capabilityget_run_statusno sensitive capabilityget_table_lineageno sensitive capabilityinstall_libraryno sensitive capabilitylist_catalogsno sensitive capabilitylist_cluster_librariesno sensitive capabilitylist_clustersno sensitive capabilitylist_genie_spacesno sensitive capabilitylist_job_runsno sensitive capabilitylist_jobsno sensitive capabilitylist_reposno sensitive capabilitylist_schemasno sensitive capabilitylist_tablesno sensitive capabilityuninstall_libraryno sensitive capabilityupdate_repono sensitive capabilityScan 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 92/100 | 7 | 1.13.0 | 2026-08-25 |
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.
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 databricks-mcp-genie --online --registry pypi
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.