MCP servers › com.techfabric.databricks › field-guide

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

com.techfabric.databricks/field-guide

TechFabric's Databricks Field Guide: search, explore concepts, quizzes, code review, cost. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-24version 1.7.2streamable HTTP15 tools

Summary

com.techfabric.databricks/field-guide is a remote MCP server listed in the official MCP registry at version 1.7.2. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 15 tools, 60 resources and 12 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 15
Last tested: 2026-10-24

Add to your client

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-24

Mode

read-only (no tool calls)

Latest version

1.7.2, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)

First listed version

2026-10-19 (earliest version still in the registry; older removed versions would be earlier)

Version history

19 versions listed, 2026-10-19 to 2026-10-24; 19 in the 90 days before the 2026-10-24 snapshot.

Most recent 12 versions

1.7.2 · 2026-10-24
1.7.1 · 2026-10-24
1.7.0 · 2026-10-24
1.6.1 · 2026-10-24
1.6.0 · 2026-10-24
1.5.2 · 2026-10-24
1.5.1 · 2026-10-24
1.5.0 · 2026-10-23
1.4.3 · 2026-10-23
1.4.2 · 2026-10-23
1.4.1 · 2026-10-23
1.4.0 · 2026-10-22

(versions still listed in the registry only)

Registry data

snapshot 2026-10-24

Package and repository

checked 2026-10-24

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

Version 1.3.2 (published 2026-10-22) → 1.7.2 (published 2026-10-24), between the registry lists of 2026-10-23 and 2026-10-24.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24; release notes from the GitHub Releases API, checked 2026-10-24.

What it is

What does this server offer?

Observed inventory

15tools

60resources

12prompts

None of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.

search_guideon 3 other servers
“Search the guide's chapters, margin notes and events for a Databricks question.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- querystringrequired“The question or topic in plain words, e.g.”
- kindstring“Only chapters, margin notes (dated news with our position), feature pages or events”
- limitinteger“How many results (default 10)”
get_chapteron 7 other servers
“One chapter (or margin note) of the guide as clean Markdown with its code blocks intact, or one section of it: with its outline, its code blocks listed separately, its FAQs, when it last changed, and…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- slugstringrequired“A chapter's slug (lakebase, unity-catalog, start-here), a note's slug, or a guide URL or path.”
- sectionstring“One section only: its anchor (from search_guide, list_chapters or the outline) or its heading.”
get_code_exampleson 2 other servers
“The SQL, Python, CLI and config blocks in the guide that match a topic, each with the explanation around it, the section it is from (URL with anchor), and the docs links that section cites.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
- topicstringrequired“What the code should do or touch, e.g.”
- langstring“Only this language: sql, python, bash, yaml, json, hcl ...”
- chapterstring“Only examples from this chapter or note: its slug (lakebase, unity-catalog), path or URL.”
- limitinteger“How many examples (default 8)”
whats_newon 34 other servers
“Recent Databricks changes the guide tracks, newest first: margin notes (dated news with our position), release-stage changes from the feature register (with links to Databricks' documentation and rel…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- sincestring“Changes on or after this day, YYYY-MM-DD (default: the last 30 days)”
- limitinteger“How many items (default 30)”
list_chapterson 5 other servers
“Every chapter in the guide's order, with its part, summary, dates, URL, Markdown URL and its main sections; and the margin notes.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
review_databricks_code
“Check one file of SQL, Python (PySpark, a notebook's source) or YAML (a Databricks Asset Bundle, job, cluster or warehouse config) against the Field Guide's own best-practice rules, deterministically…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- codestringrequired“The file's contents: SQL, Python (PySpark, a notebook's source) or YAML (a Databricks Asset Bundle, job, cluster or warehouse config).”
- langstring“sql, python or yaml.”
- filenamestring“The file's path in the repository, e.g.”
estimate_coston 48 other servers
“Estimate a Databricks workload's monthly cost from the figures the Field Guide states (list prices per DBU by compute type, DBUs an hour by SQL warehouse size and classic instance type, model serving…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
22 inputs, 1 required
- workloadstringrequired“jobs, all_purpose (interactive notebooks), sql_warehouse, apps, genie, lakebase, model_serving or storage”
- computestring“jobs and all_purpose: serverless or classic; sql_warehouse: serverless, pro, classic”
- sizestring“apps: medium (the default), large or xlarge; sql_warehouse: the t-shirt size, 2x-small, x-small, small, medium, large, x-large, 2x-large, 3x-large, 4x-large (D…”
- dbus_per_hournumber“DBUs the compute uses an hour, when the guide has no figure for its shape (a serverless job, an instance type it does not list): from system.billing.usage or D…”
- clustersinteger“sql_warehouse: clusters running (default 1)”
- max_clustersinteger“sql_warehouse: the most clusters it scales out to; the estimate ranges from clusters to max_clusters”
- instance_typestring“jobs or all_purpose, classic: the AWS instance type (m5.xlarge, m5.2xlarge, m6i.xlarge, m7i.xlarge, r5.xlarge, c5.2xlarge, i3.xlarge, i3.2xlarge are in the gui…”
- instancesinteger“jobs or all_purpose, classic: instances in the cluster, the driver counted as one; model_serving cpu: Medium configurations”
- servingstring“model_serving: pay_per_token, provisioned_throughput, gpu or cpu (omit for every price the guide states)”
- modelstring“model_serving, pay_per_token or provisioned_throughput: the model, as in 'Llama 3.3 70B' or 'claude-sonnet-5.5'”
- input_tokens_millionsnumber“model_serving, pay_per_token: input tokens a month, in millions”
- output_tokens_millionsnumber“model_serving, pay_per_token: output tokens a month, in millions”
- model_unitsinteger“model_serving, provisioned_throughput: model units (default 50, the block the rates are quoted for; a reservation takes multiples of 50 and bills every hour of…”
- reservationstring“model_serving, provisioned_throughput: on_demand, 1_month or 3_month”
- dbus_per_monthnumber“Or the DBUs a month outright”
- hours_per_daynumber
- days_per_monthnumber“Days it runs a month (default 30 with hours_per_day)”
- hours_per_monthnumber
- usersinteger“genie: the people using it”
- dbus_per_usernumber“genie: each user's Genie DBUs a month”
- storage_gbnumber“storage: GB held”
- always_onboolean“lakebase: an always-on 0.5 CU floor (the one Lakebase figure the guide quotes)”
explore_concept
“Interactive: explains one Databricks concept step by step from the Field Guide's chapters: delta-transaction-log, liquid-clustering-vs-zorder, spark-shuffle-and-stages, unity-catalog-privilege-inheri…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- conceptstring“The concept: delta-transaction-log, liquid-clustering-vs-zorder, spark-shuffle-and-stages, unity-catalog-privilege-inheritance, photon-vs-classic-cost, cluster…”
quiz_meon 1 other server
“Interactive: quizzes the reader.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs
- chapterstring“A chapter's slug (unity-catalog, lakebase), path or URL; list_chapters has them.”
- sectionstring“One section of that chapter: its anchor or heading.”
- examstring“Instead of a chapter: practice for a certification exam's domain (needs domain): data-engineer-associate, data-engineer-professional, data-analyst-associate, m…”
- domainstring“The exam's domain id, as exam_prep lists them”
- answersarray“The reader's answers, in question order, to score them: a letter (A to H) or an option's exact words, "" or "-" for none.”
learn_path
“Interactive: a curated learning path through the Field Guide, by role or goal (data-engineer-fundamentals, analytics-engineer, ml-engineer, platform-admin, snowflake-to-databricks, cost-control): its…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- pathstring“The path: data-engineer-fundamentals, analytics-engineer, ml-engineer, platform-admin, snowflake-to-databricks, cost-control.”
- donearray“The steps the reader has done, by number or id (from an earlier result): progress lives with the reader, not the server”
exam_prep
“Interactive: certification prep for Databricks' exams (data-engineer-associate, data-engineer-professional, data-analyst-associate, machine-learning-associate): each domain with its weight as Databri…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- examstring“The exam: data-engineer-associate, data-engineer-professional, data-analyst-associate, machine-learning-associate.”
- domainstring“One of the exam's domains (its id, from the result), for its practice questions”
flashcards
“Interactive: flashcards for a Databricks exam domain (data-engineer-associate, data-engineer-professional, data-analyst-associate, machine-learning-associate; exam_prep lists the domains) or a chapte…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- examstring“An exam (data-engineer-associate, data-engineer-professional, data-analyst-associate, machine-learning-associate), with one of its domains”
- domainstring“The exam's domain id, as exam_prep lists them”
- chapterstring“Or a chapter: its slug or URL”

Show 3 more tools

visualizeon 1 other server
“Interactive: draws your answer as a card the reader can use, from an A2UI v0.9.1 document you write: a comparison of options with a verdict, a plan as steps or a timeline, a cost or sizing calculator…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- documentstringrequired“An A2UI v0.9.1 document: messages as JSONL, one a line (createSurface, updateDataModel, updateComponents), or a JSON array of them.”
- titlestring“The card's title, in plain words”
- sourcesarray“The Field Guide URLs (with #anchor) whose facts the document uses, from search_guide or get_chapter.”
decideon 11 other servers
“Interactive: walks a Databricks decision one question at a time (which-compute, serverless-or-classic, lakebase-or-delta, genie-or-dashboard, streaming-or-batch): every answer rests on the guide's ow…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- questionstring“The decision, in plain words or by id: which-compute, serverless-or-classic, lakebase-or-delta, genie-or-dashboard, streaming-or-batch.”
- choicesarray“The reader's choices so far, as option numbers from the first question: the result then carries where they are, or the answer”
explore_diagram
“Interactive: a chapter's own diagrams, played step by step: each flowchart edge or sequence message in order, each node linking the section of the chapter it is about.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- chapterstringrequired“A chapter's slug (lakebase, medallion-architecture), path or URL; list_chapters has them”
- sectionstring“Only the diagrams in this section: its anchor or heading”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 96% of 56
Tools with a description: 100% of 15
Typical description length: 572 characters

The tool set

Counted from the listing

Tools: 15
Size of the list: about 13,868 tokens for an agent to load (characters ÷ 4)
Naming: 12 of 15 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://databricks.techfabric.com/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "field-guide": {
      "url": "https://databricks.techfabric.com/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "field-guide": {
      "type": "http",
      "url": "https://databricks.techfabric.com/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"field-guide","type":"http","url":"https://databricks.techfabric.com/mcp"}'

Claude Code

claude mcp add --transport http field-guide https://databricks.techfabric.com/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://databricks.techfabric.com/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint databricks.techfabric.com/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/Fabric-Pro/databricks-field-guide-mcp	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: com.techfabric.databricks
GitHub owner: an organization (Fabric-Pro)

Repository: github.com/Fabric-Pro/databricks-field-guide-mcp
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-24; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about com.techfabric.databricks/field-guide

Answered from the data above

Is com.techfabric.databricks/field-guide safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.techfabric.databricks/field-guide need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.techfabric.databricks/field-guide been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Does com.techfabric.databricks/field-guide publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of com.techfabric.databricks/field-guide?

In github.com/Fabric-Pro/databricks-field-guide-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,532 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 15 tools, 60 resources, 12 prompts.
12,202 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it. · from version 1.3.2 (same website)

Programming language

not stated

GitHub detects no source language in this repository (docs-only or empty)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

completions, prompts, resources, tools, extensions

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.techfabric.databricks/field-guide: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/com.techfabric.databricks/field-guide

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.techfabric.databricks/field-guide)](https://protocolprobe.com/mcp/servers/com.techfabric.databricks/field-guide)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology