Dataiku MCP
NPM · DATAIKU-MCP · SCANNED AUG 3
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency84
- 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 159 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability49
- AI-judged instruction clarity (fair).Partial
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · dataiku-mcp
claude mcp add clssck-dataiku-mcp -- npx -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": {
"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.
- 2 Aug 26 +22
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Provenance: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- The attested source repository moved: clssck/Dataiku_MCP security
- License: unverified → fail ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- 31 Jul 26 −19
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 29 Jul 26 +56
- Known CVEs: unverified → partial ▲ security
- Provenance: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- The attested source repository moved: clssck/Dataiku_MCP security
- License: unverified → fail ▼ functional
- Security disclosure: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → fair ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −20
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- 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
- Discovery method:
- attestation_endpoint
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.