Dataproc MCP Server
@dipseth/dataproc-mcp-server
npm
v4.7.0
Published by @dipseth — 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.
A production-ready Model Context Protocol (MCP) server for Google Cloud Dataproc operations. Provides intelligent defaults, comprehensive tooling, and seamless integration with Roo (VS Code) for big data workflows.
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 − 7.5 = 93. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 93 − 7 = 86. 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −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 13
high Shell/command execution in server code (build/config/credentials.js)MTC-SRC-002
In the server's implementation (`build/config/credentials.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: port { execSync } from 'child_process'; import { getServerConfig } from './server.js'; import axios from 'axios'; let au
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/config/credentials.js
high Shell/command execution in server code (build/services/qdrant-manager.js)MTC-SRC-002
In the server's implementation (`build/services/qdrant-manager.js:5`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { promises as fs } from 'fs'; import path from 'path'; import { createSer
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/services/qdrant-manager.js
medium Hardcoded egress to an external endpoint (build/server/auth/githubOAuthProvider.js)MTC-SRC-003
In the server's implementation (`build/server/auth/githubOAuthProvider.js:19`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const response = await axios.get('https://api.github.com/user', { headers: { Author
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/server/auth/githubOAuthProvider.js
medium Hardcoded egress to an external endpoint (build/server/auth/mcpOAuthMetadata.js)MTC-SRC-003
In the server's implementation (`build/server/auth/mcpOAuthMetadata.js:105`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: t tokenResponse = await fetch('https://github.com/login/oauth/access_token', { method: 'POST',
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/server/auth/mcpOAuthMetadata.js
medium Untrusted input concatenated into a command sink (build/config/credentials.js)MTC-SRC-009
In the server's implementation (`build/config/credentials.js:555`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: backAccount}`); execSync(`gcloud config set account ${fallbackAccount}`, { encoding: 'utf8' }); // Get t
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/config/credentials.js
low Shell/command execution in packaging/dev tooling (scripts/build-standalone.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/build-standalone.js:110`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { fileURLToPath } from 'url'; const __filename = fileURLToPath(import.me
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/build-standalone.js
low Shell/command execution in packaging/dev tooling (scripts/generate-ssl-cert.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/generate-ssl-cert.js:11`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: port { execSync } from 'child_process'; import { existsSync, mkdirSync } from 'fs'; import { join, dirname } from 'path'
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/generate-ssl-cert.js
low Shell/command execution in packaging/dev tooling (scripts/pre-flight-check.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/pre-flight-check.js:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: port { execSync } from 'child_process'; import { fileURLToPath } from 'url'; const __filename = fileURLToPath(import.me
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/pre-flight-check.js
low Shell/command execution in packaging/dev tooling (scripts/prepare-release.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/prepare-release.js:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: port { execSync } from 'child_process'; import { fileURLToPath } from 'url'; const __filename = fileURLToPath(import.me
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/prepare-release.js
low Shell/command execution in packaging/dev tooling (scripts/run-tests-built.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/run-tests-built.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: st { spawn } = require('child_process'); const path = require('path'); const testPattern = process.argv[2]; const timeo
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/run-tests-built.js
low Shell/command execution in packaging/dev tooling (scripts/run-tests-safe.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/run-tests-safe.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: st { spawn } = require('child_process'); const command = process.argv[2]; const args = process.argv.slice(3); if (!com
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/run-tests-safe.js
low Shell/command execution in packaging/dev tooling (scripts/stop-server.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/stop-server.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { exec } from 'child_process'; import { promisify } from 'util'; const execAsync = promisify(exec); async fun
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/stop-server.js
low Package runs install-time scripts (postinstall)MTC-SUP-010
"@dipseth/dataproc-mcp-server" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node scripts/postinstall.js
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @dipseth/dataproc-mcp-server
Tools 1
Each tool and what it can reach — statically extracted from the published source.
Default Configurationno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (1 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 |
|---|---|---|---|---|
v4.7.0 latest |
B 86/100 | 13 | 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 @dipseth/dataproc-mcp-server --onlineMore in Other
A Model Context Protocol server implementation for AdGuard Home that enables AI agents to query and manage DNS records, filtering rules and more
Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.
MCP server with Airtable integration
A free one-minute reset for people, delivered by AI, with no account or personal data.
Access SEC filings efficiently, save time and tokens, and get cited answers.
A smart [MCP](https://modelcontextprotocol.io) server for [AniList](https://anilist.co) that gets your anime/manga taste - not just API calls.