mcp-google-drive
npm
v1.6.2
Published by longtran2404 — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.
In the server's implementation (`test-mcp-drive.cjs:1`): 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: child_process
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 test-mcp-drive.cjs
In the server's implementation (`test-mcp-drive.js:1`): 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: child_process
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 test-mcp-drive.js
In the server's implementation (`test-search.cjs:1`): 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: child_process
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 test-search.cjs
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.6.2 latest |
A 100/100 | 3 | 1.5.0 | 2026-07-22 |
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.
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 mcp-google-drive --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 9 side by side →
Provides secure access to Google Drive, Docs, Sheets, and Slides from MCP clients such as Claude Desktop.
Security scan results for the Google Drive (us-all) MCP server.
Security scan results for the Google Drive (botrun) MCP server.
Security scan results for the Google Drive (domdomegg) MCP server.
Security scan results for the Google Drive (ibarcarty) MCP server.
Security scan results for the Google Drive (hachiai) MCP server.
Security scan results for the Add MCP server.
Security scan results for the Agentmetal MCP server.
Security scan results for the Astro MCP server.
Security scan results for the Atp Mcp Adapter MCP server.
Security scan results for the Auralis Google MCP server.
Security scan results for the Aws MCP server.