Google Drive (ibarcarty) MCP Server

@ibarcarty/mcp-server-google-drive npm v1.4.0

Published by @ibarcarty — 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 Google Drive, Google Docs, Google Sheets, and Google Slides with full read/write operations, rich markdown-to-docs formatting, theming, shared drive support, and OAuth2 authentication

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

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 − 4 = 96. 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — 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 6

medium Tool "drive_create_file" can modify the filesystemMTC-CAP-002

Tool "drive_create_file" can write, overwrite or delete files (keyword "create_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool drive_create_file

medium Tool "drive_delete_file" can modify the filesystemMTC-CAP-002

Tool "drive_delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool drive_delete_file

medium Tool "drive_move_file" can modify the filesystemMTC-CAP-002

Tool "drive_move_file" can write, overwrite or delete files (keyword "move_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool drive_move_file

low Mutating tool "drive_create_file" declares no destructiveHintMTC-CAP-005

Tool "drive_create_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool drive_create_file

low Mutating tool "drive_delete_file" declares no destructiveHintMTC-CAP-005

Tool "drive_delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool drive_delete_file

low Mutating tool "drive_move_file" declares no destructiveHintMTC-CAP-005

Tool "drive_move_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool drive_move_file

Tools 33

Each tool and what it can reach — statically extracted from the published source.

  • drive_create_filewrites files
  • drive_delete_filewrites files
  • drive_list_filesreads sensitive data
  • drive_move_filewrites files
  • drive_read_filereads sensitive data
  • calendar_create_eventno sensitive capability
  • calendar_delete_eventno sensitive capability
  • calendar_list_eventsno sensitive capability
  • calendar_update_eventno sensitive capability
  • docs_append_textno sensitive capability
Show 23 more tools ↓
  • docs_apply_corporate_templateno sensitive capability
  • docs_apply_themeno sensitive capability
  • docs_insert_textno sensitive capability
  • docs_readno sensitive capability
  • docs_replace_textno sensitive capability
  • docs_write_markdownno sensitive capability
  • drive_copy_fileno sensitive capability
  • drive_create_folderno sensitive capability
  • drive_get_file_infono sensitive capability
  • drive_list_permissionsno sensitive capability
  • drive_remove_permissionno sensitive capability
  • drive_searchno sensitive capability
  • drive_shareno sensitive capability
  • drive_update_fileno sensitive capability
  • gmail_create_draftno sensitive capability
  • sheets_append_rowsno sensitive capability
  • sheets_clear_rangeno sensitive capability
  • sheets_read_rangeno sensitive capability
  • sheets_write_rangeno sensitive capability
  • slides_add_slideno sensitive capability
  • slides_add_textno sensitive capability
  • slides_readno sensitive capability
  • slides_replace_textno sensitive capability

What this scan could not see

Versions 4

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.

VersionScoreFindingsEngineScanned
v1.4.0 latest A 96/100 6 1.13.0 2026-09-07
v1.3.0 A 96/100 6 1.12.1 2026-08-20
v1.2.0 A 96/100 6 1.12.1 2026-08-16
v1.1.1 A 96/100 6 1.12.1 2026-08-12

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.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ibarcarty-mcp-server-google-drive/badge.svg)](https://mcptrustchecker.com/registry/ibarcarty-mcp-server-google-drive)
HTML
<a href="https://mcptrustchecker.com/registry/ibarcarty-mcp-server-google-drive"><img src="https://mcptrustchecker.com/registry/ibarcarty-mcp-server-google-drive/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ibarcarty-mcp-server-google-drive/badge.json via https://img.shields.io/endpoint?url=…

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 @ibarcarty/mcp-server-google-drive --online

Use the free API → How scoring works

Other implementations of Google Drive 9

Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →

More in Files & Storage