Databricks (PyPI) MCP Server

databricks-mcp-server PyPI v0.4.4

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.

A Model Context Protocol (MCP) server for Databricks

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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
Moderate
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/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 − 5 = 95. 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
−3 capability blast radius (moderate) — 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.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 38

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

  • execute_sqlreads sensitive data
  • list_filesreads sensitive data
  • cancel_runno sensitive capability
  • create_catalogno sensitive capability
  • create_clusterno sensitive capability
  • create_jobno sensitive capability
  • create_repono sensitive capability
  • create_schemano sensitive capability
  • create_tableno sensitive capability
  • dbfs_deleteno sensitive capability
Show 28 more tools ↓
  • dbfs_putno sensitive capability
  • delete_jobno sensitive capability
  • delete_workspace_objectno sensitive capability
  • export_notebookno sensitive capability
  • get_clusterno sensitive capability
  • get_run_statusno sensitive capability
  • get_table_lineageno sensitive capability
  • get_workspace_file_contentno sensitive capability
  • get_workspace_file_infono sensitive capability
  • import_notebookno sensitive capability
  • install_libraryno sensitive capability
  • list_catalogsno sensitive capability
  • list_cluster_librariesno sensitive capability
  • list_clustersno sensitive capability
  • list_job_runsno sensitive capability
  • list_jobsno sensitive capability
  • list_notebooksno sensitive capability
  • list_reposno sensitive capability
  • list_schemasno sensitive capability
  • list_tablesno sensitive capability
  • pull_repono sensitive capability
  • run_jobno sensitive capability
  • run_notebookno sensitive capability
  • start_clusterno sensitive capability
  • sync_repo_and_run_notebookno sensitive capability
  • terminate_clusterno sensitive capability
  • uninstall_libraryno sensitive capability
  • update_repono 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.4.4 latest A 95/100 0 1.13.0 2026-08-25

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/databricks-mcp-server-2/badge.svg)](https://mcptrustchecker.com/registry/databricks-mcp-server-2)
HTML
<a href="https://mcptrustchecker.com/registry/databricks-mcp-server-2"><img src="https://mcptrustchecker.com/registry/databricks-mcp-server-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/databricks-mcp-server-2/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 databricks-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of Databricks 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Cloud & DevOps