Remote MCP · Endpoint

Databricks MCP server

No. Databricks answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_databricks

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/databricks-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
17 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Your Databricks Lakehouse in natural language: run SQL on your SQL warehouses, track long-running qu
Repository
https://github.com/mcp-dir/databricks-mcp
Listing
From the official MCP registry (active).
Recent checks of Databricks
CheckedResultHandshake
1 hour agoHandshake completed89 ms
2 days agoHandshake completed92 ms
4 days agoHandshake completed124 ms
5 days agoHandshake completed48 ms
7 days agoHandshake completed568 ms
8 days agoHandshake completed237 ms
9 days agoHandshake completed72 ms
12 days agoHandshake completed34 ms
14 days agoHandshake completed39 ms
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed35 ms
18 days agoHandshake completed42 ms
19 days agoHandshake completed38 ms
20 days agoHandshake completed39 ms
20 days agoHandshake completed31 ms
21 days agoHandshake completed87 ms
23 days agoHandshake completed29 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Databricks and makes no claim about it beyond what these checks measured.