Gdocs (iamtemazhe) MCP Server
mcp-gdocs
npm
v1.3.0
Source verified
Published by iamtemazhe — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for Google Docs, Drive & Comments (OAuth + Service Account)
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 − 3 = 97. 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 |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
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 4
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
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
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
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
Tools 61
Each tool and what it can reach — statically extracted from the published source.
docs_get_commentingests untrusted inputdocs_get_document_infoingests untrusted inputdrive_delete_filewrites filesdrive_get_folder_infoingests untrusted inputdrive_get_revisioningests untrusted inputdrive_list_folder_contentsreads sensitive datadrive_move_filewrites filesdocs_add_commentno sensitive capabilitydocs_add_tabno sensitive capabilitydocs_append_textno sensitive capability
Show 51 more tools ↓
docs_apply_heading_styleno sensitive capabilitydocs_apply_paragraph_styleno sensitive capabilitydocs_apply_text_styleno sensitive capabilitydocs_batch_updateno sensitive capabilitydocs_create_footnoteno sensitive capabilitydocs_create_named_rangeno sensitive capabilitydocs_delete_commentno sensitive capabilitydocs_delete_named_rangeno sensitive capabilitydocs_delete_rangeno sensitive capabilitydocs_delete_table_columnno sensitive capabilitydocs_delete_table_rowno sensitive capabilitydocs_export_pdfno sensitive capabilitydocs_format_by_textno sensitive capabilitydocs_insert_imageno sensitive capabilitydocs_insert_local_imageno sensitive capabilitydocs_insert_page_breakno sensitive capabilitydocs_insert_table_columnno sensitive capabilitydocs_insert_table_rowno sensitive capabilitydocs_insert_table_with_datano sensitive capabilitydocs_insert_textno sensitive capabilitydocs_list_commentsno sensitive capabilitydocs_list_document_tabsno sensitive capabilitydocs_read_documentno sensitive capabilitydocs_rename_tabno sensitive capabilitydocs_replace_all_textno sensitive capabilitydocs_replace_document_contentno sensitive capabilitydocs_replace_named_range_contentno sensitive capabilitydocs_replace_with_markdown_file_nativeno sensitive capabilitydocs_replace_with_markdown_nativeno sensitive capabilitydocs_reply_to_commentno sensitive capabilitydocs_resolve_commentno sensitive capabilitydocs_update_footerno sensitive capabilitydocs_update_headerno sensitive capabilitydocs_update_table_cell_contentno sensitive capabilitydocs_update_table_cell_styleno sensitive capabilitydrive_copy_fileno sensitive capabilitydrive_create_documentno sensitive capabilitydrive_create_folderno sensitive capabilitydrive_create_from_markdownno sensitive capabilitydrive_create_from_markdown_fileno sensitive capabilitydrive_create_from_templateno sensitive capabilitydrive_export_fileno sensitive capabilitydrive_list_documentsno sensitive capabilitydrive_list_permissionsno sensitive capabilitydrive_list_revisionsno sensitive capabilitydrive_list_shared_drivesno sensitive capabilitydrive_remove_permissionno sensitive capabilitydrive_rename_fileno sensitive capabilitydrive_search_documentsno sensitive capabilitydrive_share_fileno sensitive capabilitydrive_update_permissionno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (61 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.3.0 latest |
A 97/100 | 4 | 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 mcp-gdocs --onlineOther implementations of Gdocs 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Files & Storage
Safe bulk Meta ads: launch 150+ campaigns from Drive folders with spend guardrails and validation.
CLI tool to add MCP servers to various AI coding clients
MCP compatibility adapter for Agent Tool Protocol
MCP server for multi-tenant DuckDB management with R2/S3 storage
A stdio-to-HTTP MCP proxy that transparently intercepts file parameters, reading local files and base64-encoding them before forwarding to the remote server.
Free buyer-side outcome verification and provider comparison for supplied agent receipts.