io.github.clssck/dataiku-mcp

MCPattested
v1.1.1io.github.clssckUnknownUpdated 7mo agonpmGitHub

MCP server for Dataiku DSS project, flow, and operations APIs.

MCP server for Dataiku DSS REST APIs, focused on flow analysis and reliable day-to-day operations (projects, datasets, recipes, jobs, scenarios, folders, variables, connections, and code environments). Deterministic normalized flow maps () with recipe subtypes and connectivity. Summary-first outputs with explicit raw/detail toggles where needed. Broad test coverage (unit + live integration +…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
7mo agoLast update
Package
Authorio.github.clssck
LicenseUnknown
Version1.1.1
Sourcemcp-registry
npmdataiku-mcp
GitHubclssck/Dataiku_MCP
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 20e96a5
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv1.1.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 37 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

MCP server for Dataiku DSS REST APIs, focused on flow analysis and reliable day-to-day operations (projects, datasets, recipes, jobs, scenarios, folders, variables, connections, and code environments). Deterministic normalized flow maps () with recipe subtypes and connectivity. Summary-first outputs with explicit raw/detail toggles where needed. Broad test coverage (unit + live integration + optional destructive integration suite). Strong error taxonomy in responses: , , , , with retry hints.…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.