com.mambabuilt/mcp-google-sheets-import-export
NPM · @MAMBALABSDEV/MCP-GOOGLE-SHEETS-IMPORT-EXPORT
Read a Google Sheet into rows or write rows to a sheet: append, replace, or upsert by key
Available components
Last scanned (18 hours ago)
Scores higher than 39% of npm servers
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 Security98
- 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
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 876 tokens (~876/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.84 ▲ functional
- 20 Nov 26 42
First indexed and scored.
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 21 Nov 2026 · Analysed npm/@mambalabsdev/mcp-google-sheets-import-export@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
google_sheets_import_export Read or write a Google Sheet ~876
Read a Google Sheet into rows, or write rows into a Google Sheet. Modes: read (one row per sheet row, keyed by the header row), append, replace (clear the tab, then write), and upsert (update rows whose key_column value already exists, add the rest). Writes need the buyer's own Google credential: a service account key JSON with the sheet shared to its client_email, or an OAuth refresh token with its client, or an OAuth access token. A sheet shared as anyone with the link reads with no credential. Pay per event on Apify: 0.01 USD per block of up to 100 rows written, 0.005 USD per block of up to 100 rows read.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | – | Optional, write modes. Only these keys are written, in this order. Default: every key in the rows, in first seen order. |
| dataset_id | string | – | Write modes. The Apify dataset whose items go into the sheet, for example the default dataset of another run. In an Apify integration, pass the triggering run's resource.defaultDatasetId variable. Fi… |
| header_row | boolean | – | true (default) or false. When true, read rows are keyed by the header row, and writes match your row keys to the header columns and add new columns at the end. When false, read rows are keyed by colu… |
| key_column | string | – | Upsert mode. The column whose value identifies a row, for example email or url. A row whose value is already in that column is overwritten in place; the rest are added. Rows with no value in it are s… |
| max_charge_usd | string | – | Optional. The run stops before a charge that would pass this amount, and never writes a block of rows it could not charge. Summary rows are always returned. |
| max_rows | number | – | Most rows to read or write in this run, 1 to 1,000,000 (default 100,000). |
| mode | string | – | read (default): the sheet becomes one dataset row per sheet row. append: add rows after the last row. replace: clear the tab, then write the rows. upsert: overwrite the rows whose key_column value is… |
| oauth_access_token | string | – | Instead of the above: a current OAuth access token with the spreadsheets scope. It expires in about an hour, so it suits a single run. |
| oauth_client_id | string | – | The client ID that issued the refresh token. |
| oauth_client_secret | string | – | The client secret that issued the refresh token. |
| oauth_refresh_token | string | – | Instead of a service account: a refresh token from your own Google OAuth client with the spreadsheets scope. Needs oauth_client_id and oauth_client_secret from the same client. |
| range | string | – | Optional, read mode. An A1 range without the tab name, for example A1:F500 or B:D. Default: the whole tab. |
| rows | array | – | Write modes, instead of a dataset. A JSON list of objects, one per sheet row, for example [{"name": "Ann", "email": "ann@example.com"}]. |
| service_account_json | string | – | Your own service account key file, pasted whole. Share the spreadsheet with its client_email as an Editor (Viewer to read). It is sent only to Google and is never stored, logged, or written to a row. |
| sheet | string | – | Optional. The tab name, or its gid number. Default: the gid in the URL, else the first tab. In a write mode a tab name that does not exist is created. |
| spreadsheet | string | – | The Google Sheets URL as copied from the browser, or the spreadsheet ID. A #gid= in the URL picks that tab. |
| value_input | string | – | raw (default): every value is stored exactly as given, so text starting with = is not run as a formula. user_entered: Google parses values as if typed, so formulas run and dates and numbers are conve… |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-google-sheets-import-export server?
com.mambabuilt/mcp-google-sheets-import-export runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-google-sheets-import-export. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-google-sheets-import-export
claude mcp add com-mambabuilt-mcp-google-sheets-import-export -- npx -y @mambalabsdev/mcp-google-sheets-import-export
What is the com.mambabuilt/mcp-google-sheets-import-export server?
com.mambabuilt/mcp-google-sheets-import-export is listed in the public MCP registry as com.mambabuilt/mcp-google-sheets-import-export. Read a Google Sheet into rows or write rows to a sheet: append, replace, or upsert by key. This page covers its npm package (@mambalabsdev/mcp-google-sheets-import-export).
Is the com.mambabuilt/mcp-google-sheets-import-export server safe to use?
com.mambabuilt/mcp-google-sheets-import-export scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 com.mambabuilt/mcp-google-sheets-import-export server expose?
com.mambabuilt/mcp-google-sheets-import-export exposes 1 tool: google_sheets_import_export. Their descriptions and schemas cost roughly 876 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-google-sheets-import-export server still maintained?
com.mambabuilt/mcp-google-sheets-import-export is still listed as active in the MCP registry. We last reached this channel on 21 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 com.mambabuilt/mcp-google-sheets-import-export server under?
com.mambabuilt/mcp-google-sheets-import-export declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the com.mambabuilt/mcp-google-sheets-import-export server?
VerifyMCP ran 15 checks on com.mambabuilt/mcp-google-sheets-import-export, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about com.mambabuilt/mcp-google-sheets-import-export: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.