io.github.CloudCorpRecords/driveport
NPM · @RENETURCIOS/DRIVEPORT · 2 COMPONENTS
Google Drive files: search, list, read, upload, download, folders and trash, as MCP tools.
Available components
Last scanned (6 hours ago)
Scores higher than 34% of npm servers
Category Documents and Files
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 464 tokens (~58/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 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.
- 1 Nov 26 65
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 5 Nov 2026 · Analysed npm/@reneturcios/driveport@0.1.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
create_folder ~59
Create a new folder in Google Drive.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the new folder. |
| parent_id | string | – | Optional ID of the parent folder to create the new folder inside; the folder is created at the Drive root when omitted. |
No output schema declared.
No examples provided.
download_file ~73
Download a file from Google Drive, optionally exporting it to another MIME type.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | ID of the Google Drive file to download. |
| mime_type | string | – | Optional MIME type to export the file as; when given, the file is exported in that format, otherwise it is downloaded as-is. |
No output schema declared.
No examples provided.
get_file_metadata ~39
Get metadata for a file in Google Drive by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | ID of the Google Drive file to get metadata for. |
No output schema declared.
No examples provided.
list_files ~65
List files in Google Drive, optionally filtered by a query.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | number | – | Maximum number of files to return in the list (the Drive pageSize parameter). |
| query | string | – | Optional Drive query string to filter the files listed (sent as the q parameter). |
No output schema declared.
No examples provided.
read_file ~39
Read the contents of a file in Google Drive as text.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | ID of the Google Drive file to read the contents of. |
No output schema declared.
No examples provided.
search_files ~49
Search for files in Google Drive using a Drive query string.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Drive query string used to filter the files to return, in Google Drive query syntax (sent as the q parameter). |
No output schema declared.
No examples provided.
trash_file ~37
Move a file in Google Drive to the trash.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | ID of the Google Drive file to move to the trash. |
No output schema declared.
No examples provided.
upload_file ~103
Upload a new file with text content to Google Drive.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Text content to upload as the file's body. |
| mime_type | string | – | Optional MIME type for the new file; defaults to text/plain when omitted. |
| name | string | yes | Name for the new file in Google Drive. |
| parent_id | string | – | Optional ID of the parent folder to place the new file in; the file is placed at the Drive root when omitted. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/driveport MCP server?
io.github.CloudCorpRecords/driveport runs locally as an npm package, launched with npx -y @reneturcios/driveport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/driveport
claude mcp add cloudcorprecords-driveport -- npx -y @reneturcios/driveport
What is the io.github.CloudCorpRecords/driveport MCP server?
io.github.CloudCorpRecords/driveport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/driveport. Google Drive files: search, list, read, upload, download, folders and trash, as MCP tools. This page covers its npm package (@reneturcios/driveport).
Is the io.github.CloudCorpRecords/driveport MCP server safe to use?
io.github.CloudCorpRecords/driveport scores 67 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 io.github.CloudCorpRecords/driveport MCP server expose?
io.github.CloudCorpRecords/driveport exposes 8 tools: search_files, list_files, get_file_metadata, read_file, create_folder, and 3 more. Their descriptions and schemas cost roughly 464 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/driveport MCP server still maintained?
io.github.CloudCorpRecords/driveport 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 io.github.CloudCorpRecords/driveport MCP server under?
io.github.CloudCorpRecords/driveport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.