Dataiku MCP
NPM · DATAIKU-MCP · SCANNED SEP 21
MCP server for Dataiku DSS project, flow, and operations APIs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to clssck/Dataiku_MCP). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 208 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 280 tokens (~31/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Dataiku MCP server?
Dataiku MCP runs locally as an npm package, launched with npx -y dataiku-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dataiku-mcp
claude mcp add clssck-dataiku-mcp -- npx -y dataiku-mcp
{
"mcpServers": {
"clssck-dataiku-mcp": {
"command": "npx",
"args": [
"-y",
"dataiku-mcp"
]
}
}
} {
"servers": {
"clssck-dataiku-mcp": {
"command": "npx",
"args": [
"-y",
"dataiku-mcp"
]
}
}
} codex mcp add clssck-dataiku-mcp -- npx -y dataiku-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"clssck-dataiku-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"dataiku-mcp"
],
"enabled": true
}
}
} openclaw mcp add clssck-dataiku-mcp --command npx --arg -y --arg dataiku-mcp
mcp_servers:
clssck-dataiku-mcp:
command: "npx"
args: ["-y", "dataiku-mcp"] {
"McpServers": {
"clssck-dataiku-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"dataiku-mcp"
]
}
}
} assistant mcp add clssck-dataiku-mcp -t stdio -c npx -a -y dataiku-mcp
{
"mcpServers": {
"clssck-dataiku-mcp": {
"command": "npx",
"args": [
"-y",
"dataiku-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −4
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.83 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/dataiku-mcp@1.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | clssck/Dataiku_MCP |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/clssck/Dataiku_MCP/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 985085948 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bc1e0c68b25cb46d21dae453d184042e391da17cbbbf11ed301b4512bb358d5e131f530d0b76b5922f70f60e39eec856316dc8254fd5c6a6f55c7cfef |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
code_env ~28
Code env ops: list/get. get returns package summaries; set full=true for full package lists.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
connection ~37
Connection discovery (action: infer). Default mode=fast uses DSS connection names; mode=rich scans project datasets for inferred type/schema/managed details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dataset ~37
Dataset ops: list/get/schema/preview/metadata/download/create/update/delete. get is summary-first; set includeDefinition=true to include full JSON definition.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
job ~37
Job ops: list/get/log/build/buildAndWait/wait/abort. get is summary-first; set includeDefinition=true to include full JSON definition.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
managed_folder ~21
Managed folder ops: list/get/contents/download/upload/delete_file.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project ~34
Project ops: list/get/metadata/flow/map. map returns normalized connectivity in structuredContent.map; includeRaw adds original graph payload.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recipe ~31
Recipe ops: list/get/create/update/delete/download. get is summary-first; set includePayload=true to include payload snippets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scenario ~31
Scenario ops: list/run/status/get/create/update/delete. get is summary-first; use includeScript/includeDefinition for details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
variable ~24
Project variable ops: get/set. set merges provided standard/local keys with existing values.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Dataiku MCP server?
Dataiku MCP is listed in the public MCP registry as io.github.clssck/dataiku-mcp. MCP server for Dataiku DSS project, flow, and operations APIs. This page covers its npm package (dataiku-mcp).
Is the Dataiku MCP server safe to use?
Dataiku MCP scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Dataiku MCP server expose?
Dataiku MCP exposes 9 tools: project, dataset, recipe, job, scenario, and 4 more. Their descriptions and schemas cost roughly 280 tokens of context every time the server is loaded.
Is the Dataiku MCP server still maintained?
Dataiku MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.