Koder Sheets MCP Server
koder-sheets-mcp
npm
v0.1.3
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for Google Sheets and Google Drive
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 − 5 = 95. 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 |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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 2
medium Tool "sheets_delete_file" can modify the filesystemMTC-CAP-002
Tool "sheets_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 sheets_delete_file
low Mutating tool "sheets_delete_file" declares no destructiveHintMTC-CAP-005
Tool "sheets_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 sheets_delete_file
Tools 30
Each tool and what it can reach — statically extracted from the published source.
sheets_delete_filewrites filessheets_add_chartno sensitive capabilitysheets_add_sheetno sensitive capabilitysheets_append_rowsno sensitive capabilitysheets_batch_writeno sensitive capabilitysheets_clear_rangeno sensitive capabilitysheets_copy_templateno sensitive capabilitysheets_create_folderno sensitive capabilitysheets_create_spreadsheetno sensitive capabilitysheets_delete_chartno sensitive capability
Show 20 more tools ↓
sheets_delete_sheetno sensitive capabilitysheets_duplicate_sheetno sensitive capabilitysheets_format_rangeno sensitive capabilitysheets_freezeno sensitive capabilitysheets_get_infono sensitive capabilitysheets_list_foldersno sensitive capabilitysheets_list_permissionsno sensitive capabilitysheets_list_spreadsheetsno sensitive capabilitysheets_make_publicno sensitive capabilitysheets_merge_cellsno sensitive capabilitysheets_oauth_revokeno sensitive capabilitysheets_oauth_startno sensitive capabilitysheets_oauth_statusno sensitive capabilitysheets_protect_rangeno sensitive capabilitysheets_read_rangeno sensitive capabilitysheets_rename_sheetno sensitive capabilitysheets_revoke_permissionno sensitive capabilitysheets_set_column_widthno sensitive capabilitysheets_share_fileno sensitive capabilitysheets_write_rangeno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (30 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 |
|---|---|---|---|---|
v0.1.3 latest |
A 95/100 | 2 | 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 koder-sheets-mcp --onlineMore 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.