Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google_sheets

NPM · @PIPEWORX/MCP-GOOGLE_SHEETS · 2 COMPONENTS

Google Sheets MCP Pack

+3 this week 84 Trust /100

Last scanned (3 hours ago)

Scores higher than 82% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-google_sheets). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 443 tokens (~88/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +27
    • Known CVEs: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 2 Nov 26 −26
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: pass → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 81

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-google_sheets@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-google_sheets
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-google_sheets/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637335408
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d4ba4a26dacfa6a36db4ff143702fc6b83f6b15057f626e655e6b0e8b6f0ba8e649a60f3790539e5e1501db7d263a61398e192558b2fc690b49825fee

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~389 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
sheets_append ~106

Append new rows to the end of a Google Sheet table. Specify sheet name and row data to add.

NameTypeReqDescription
rangestringyesA1 notation range to append after (e.g., "Sheet1!A1")
spreadsheet_idstringyesSpreadsheet ID
value_input_optionstring–How to interpret input. USER_ENTERED (default) parses formulas/dates/numbers. RAW stores literal strings.
valuesarrayyesArray of rows to append

No output schema declared.

No examples provided.

sheets_create ~42

Create a new Google Spreadsheet. Optionally set title and initial sheet names. Returns spreadsheet ID and sharing URL.

NameTypeReqDescription
titlestringyesTitle for the new spreadsheet

No output schema declared.

No examples provided.

sheets_get_spreadsheet ~44

Explore a spreadsheet's structure. Returns title, sheet/tab names, and properties. Use before reading or writing data.

NameTypeReqDescription
spreadsheet_idstringyesSpreadsheet ID

No output schema declared.

No examples provided.

sheets_read ~76

Read data from a Google Sheet range. Specify sheet name and range (e.g., 'A1:C10'). Returns rows as arrays of cell values.

NameTypeReqDescription
rangestringyesA1 notation range (e.g., "Sheet1!A1:D10")
spreadsheet_idstringyesSpreadsheet ID (from the URL)

No output schema declared.

No examples provided.

sheets_write ~121

Write data to a Google Sheet range, overwriting existing values. Specify sheet name, range (e.g., 'A1:C10'), and row data.

NameTypeReqDescription
rangestringyesA1 notation range (e.g., "Sheet1!A1")
spreadsheet_idstringyesSpreadsheet ID
value_input_optionstring–How to interpret input. USER_ENTERED (default) parses formulas/dates/numbers. RAW stores literal strings.
valuesarrayyesArray of rows, each row is an array of cell values

No output schema declared.

No examples provided.

Install

How do I install the Google_sheets MCP server?

Google_sheets runs locally as an npm package, launched with npx -y @pipeworx/mcp-google_sheets. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-google_sheets

# add to Claude Code
claude mcp add pipeworx-io-google-sheets -- npx -y @pipeworx/mcp-google_sheets
Common questions

What is the Google_sheets MCP server?

Google_sheets is an MCP server listed in the public MCP registry as io.github.pipeworx-io/google_sheets. Google Sheets MCP Pack. This page covers its npm package (@pipeworx/mcp-google_sheets).

Is the Google_sheets MCP server safe to use?

Google_sheets scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Google_sheets MCP server expose?

Google_sheets exposes 5 tools: sheets_read, sheets_write, sheets_append, sheets_get_spreadsheet, sheets_create. Their descriptions and schemas cost roughly 389 tokens of context every time the server is loaded.

Is the Google_sheets MCP server still maintained?

Google_sheets is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Google_sheets MCP server under?

Google_sheets declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.