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.

Colab Drive MCP

PYPI · COLAB-DRIVE-MCP

Synchronize Colab notebook files through Google Drive without executing notebook code.

Available components

−15 this week 76 Trust /100

Last scanned (17 hours ago)

Scores higher than 73% of PyPI servers

Category Documents and Files

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 33 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to YummyTastyCode/colab-drive-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 148 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 732 tokens (~45/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_local_cell" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 17 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.

  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 30 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 23 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +1
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

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

  • 13 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
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 4 Nov 2026 · Analysed pypi/colab-drive-mcp@0.1.3

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo YummyTastyCode/colab-drive-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/YummyTastyCode/colab-drive-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.1.3
Rekor log index 1756785166
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:5109528a5a5071e8d2021e1aa793f435d1304511092b9390938e3bb5d2a72878

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 33 packages
Packages resolved 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~582 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
add_local_cell ~44

Add a cell to a local notebook.

NameTypeReqDescription
cell_typestringyes–
index–––
pathstringyes–
sourcestringyes–

No output schema declared.

No examples provided.

authorize_google_drive ~22

Open an explicit Google OAuth flow and save the resulting local token.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clear_local_outputs ~26

Clear outputs and execution counts from a local notebook.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

copy_drive_notebook ~36

Copy a notebook file in Google Drive without executing it.

NameTypeReqDescription
file_idstringyes–
namestringyes–

No output schema declared.

No examples provided.

create_local_notebook ~41

Create a new Colab-compatible local notebook.

NameTypeReqDescription
kernel_namestring––
pathstringyes–
titlestring––

No output schema declared.

No examples provided.

delete_local_cell ~31

Delete a cell from a local notebook.

NameTypeReqDescription
indexintegeryes–
pathstringyes–

No output schema declared.

No examples provided.

get_colab_url ~35

Return a Colab URL for a Drive notebook; this does not open a browser.

NameTypeReqDescription
file_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_google_drive_status ~21

Check Google Drive setup and authorization without opening a browser.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_local_notebook ~43

Read a local notebook summary and its cells.

NameTypeReqDescription
include_sourceboolean––
max_source_charsinteger––
pathstringyes–

No output schema declared.

No examples provided.

get_notebook_sync_status ~39

Compare Drive and local notebook state; cannot detect Colab runtime activity.

NameTypeReqDescription
file_idstringyes–
local_path–––

No output schema declared.

No examples provided.

list_drive_notebooks ~35

List synchronized notebook files visible through the configured Drive access.

NameTypeReqDescription
limitinteger––
querystring––
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_local_notebooks ~38

List local .ipynb notebooks under COLAB_MCP_ROOT.

NameTypeReqDescription
limitinteger––
querystring––
NameTypeReqDescription
resultarrayyes–

No examples provided.

pull_drive_notebook ~42

Synchronize a Drive notebook file into COLAB_MCP_ROOT without executing it.

NameTypeReqDescription
file_idstringyes–
local_pathstringyes–

No output schema declared.

No examples provided.

push_local_notebook ~44

Synchronize a local notebook file to Drive without executing it.

NameTypeReqDescription
drive_namestring––
file_id–––
local_pathstringyes–

No output schema declared.

No examples provided.

search_local_cells ~39

Search cell sources in a local notebook.

NameTypeReqDescription
case_sensitiveboolean––
pathstringyes–
querystringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

update_local_cell ~46

Replace a cell's source and optionally its type.

NameTypeReqDescription
cell_type–––
indexintegeryes–
pathstringyes–
sourcestringyes–

No output schema declared.

No examples provided.

Install

How do I install the Colab Drive MCP server?

Colab Drive MCP runs locally as a PyPI package, launched with uvx colab-drive-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · colab-drive-mcp

# add to Claude Code
claude mcp add yummytastycode-colab-drive-mcp -- uvx colab-drive-mcp
Common questions

What is the Colab Drive MCP server?

Colab Drive MCP is listed in the public MCP registry as io.github.YummyTastyCode/colab-drive-mcp. Synchronize Colab notebook files through Google Drive without executing notebook code. This page covers its PyPI package (colab-drive-mcp).

Is the Colab Drive MCP server safe to use?

Colab Drive MCP scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 Colab Drive MCP server expose?

Colab Drive MCP exposes 16 tools: list_local_notebooks, get_local_notebook, create_local_notebook, add_local_cell, update_local_cell, and 11 more. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.

Is the Colab Drive MCP server still maintained?

Colab Drive MCP is still listed as active in the MCP registry. We last reached this channel on 4 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 Colab Drive MCP server under?

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