Dataiku (zhangzichao2008) MCP Server
@zhangzichao2008/mcp-dataiku
npm
v1.0.7
Published by @zhangzichao2008 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP Server for Dataiku DSS integration
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 − 1 = 99. 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:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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
Tools 43
Each tool and what it can reach — statically extracted from the published source.
add_scenario_triggerno sensitive capabilitybatch_update_objectsno sensitive capabilitybuild_datasetno sensitive capabilitycancel_running_jobsno sensitive capabilitycheck_dataset_metricsno sensitive capabilityclear_datasetno sensitive capabilityclone_scenariono sensitive capabilitycreate_datasetno sensitive capabilitycreate_recipeno sensitive capabilitycreate_scenariono sensitive capability
Show 33 more tools ↓
delete_datasetno sensitive capabilitydelete_recipeno sensitive capabilitydelete_scenariono sensitive capabilityduplicate_project_structureno sensitive capabilityexport_project_configno sensitive capabilityget_code_environmentsno sensitive capabilityget_connectionsno sensitive capabilityget_dataset_infono sensitive capabilityget_dataset_sampleno sensitive capabilityget_job_detailsno sensitive capabilityget_project_flowno sensitive capabilityget_project_variablesno sensitive capabilityget_recent_runsno sensitive capabilityget_recipe_codeno sensitive capabilityget_recipe_infono sensitive capabilityget_scenario_infono sensitive capabilityget_scenario_logsno sensitive capabilityget_scenario_run_historyno sensitive capabilityget_scenario_stepsno sensitive capabilityinspect_dataset_schemano sensitive capabilitylist_datasetsno sensitive capabilitylist_projectsno sensitive capabilitylist_recipesno sensitive capabilitylist_scenariosno sensitive capabilityremove_scenario_triggerno sensitive capabilityrun_recipeno sensitive capabilityrun_scenariono sensitive capabilitysearch_project_objectsno sensitive capabilitytest_recipe_dry_runno sensitive capabilityupdate_datasetno sensitive capabilityupdate_recipeno sensitive capabilityupdate_scenariono sensitive capabilityvalidate_recipe_syntaxno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (43 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.7 latest |
A 99/100 | 0 | 1.13.0 | 2026-09-07 |
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.
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 @zhangzichao2008/mcp-dataiku --onlineOther implementations of Dataiku 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in AI & Agents
Authenticated MCP transport with HTTP Signatures for AAuth agents
Local-first MCP server for parallel AI coding agents to claim file ownership before edits, preventing stomping on each other in the same worktree.
Agent-agnostic intercommunication system — sessions, messaging, channels, shared state, and real-time events
MCP server for AI agent task communication and delegation with diagnostic lifecycle visibility
Programmatic add/link/unlink for MCP servers across 23 AI coding agents (Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Zed, Cline, OpenCode, Goose, Kiro, Windsurf, and more). Functional API with dry-run support.
MCP server layer exposing agent-mesh orchestrator as an MCP agent