carry
NPM · @HEYVAMZ/CARRY
AirDrop for AI chats and projects: send Claude Code or Codex sessions through your own Google Drive.
Available components
Last scanned (20 hours ago)
Scores higher than 49% 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 Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
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 (Apache-2.0).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1043 tokens (~86/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
- Package version: 0.4.4 → 0.4.5 functional
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 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.
- 11 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.
- 9 Nov 26 +1
- Stability: unverified → 0.07 ▲ functional
- 8 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
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/@heyvamz/carry@0.4.5
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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | Not reviewed | node install-txcript.js |
Background: Why install scripts are a supply-chain risk →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| 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 →
carry_add_friend Add a friend ~71
Pair with a friend once. Given their email or name, returns a pairing code for the user to send them. Given a code the friend sent (starts with carry1.), accepts it and returns the user's code to send back if they haven't paired that way yet.
| Name | Type | Req | Description |
|---|---|---|---|
| email_or_code | string | yes | – |
No output schema declared.
No examples provided.
carry_connect_google_drive Connect Google Drive ~65
Connect carry to the user's Google Drive. Opens Google sign-in in their browser; they sign in and click Allow. Takes up to 5 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| friends | array | – | Emails that receive new shares by default |
| name | string | yes | Name friends will see |
No output schema declared.
No examples provided.
carry_inbox Carry inbox ~43
What paired friends sent: chats, projects, and UPDATED ones (your shares sent back with their work). Numbered; open one with carry_open ref "<number>".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
carry_list_chats List chats ~43
List AI chats stored on this computer (Claude Code, Codex) by name, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many (default 20) |
No output schema declared.
No examples provided.
carry_list_projects List projects ~72
List the user's projects (repos their Claude Code/Codex chats were started in), or with name, the chats in one project plus related chats started elsewhere that worked on its files. Use this to let the user pick what to share.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Project name from the list, for details |
No output schema declared.
No examples provided.
carry_list_shared List shared chats ~29
List shared chats: everyone's in synced-folder mode, your own shares with links in Google Drive mode.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
carry_open Open a shared chat ~134
Open a shared chat (name, .carry file path, or Drive link). By default returns its handoff and history so you can continue it right here. Set continue_in to load it as a real session in a coding tool instead.
| Name | Type | Req | Description |
|---|---|---|---|
| continue_in | string | – | claude_app / codex_app open it in the Claude or Codex desktop app; the others write a session to resume in that tool |
| dir | string | – | For project packs with continue_in: the local project folder (absolute path) |
| ref | string | yes | Pack name, path to a .carry file, or Google Drive link |
No output schema declared.
No examples provided.
carry_return Send back to friend ~78
Send a chat or project that was opened from a friend back to them with the work done here. Optionally write a short summary of what was done as handoff.
| Name | Type | Req | Description |
|---|---|---|---|
| chat | string | – | Chat name (from carry_list_chats) |
| handoff | string | – | – |
| project | string | – | Project name, instead of chat |
No output schema declared.
No examples provided.
carry_share_chat Share a chat ~148
Share a chat from carry_list_chats. Secrets are redacted before upload. Write a handoff summary (goal, done, current state, decisions, next steps) and pass it.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_return | boolean | – | With to: their carry sends it back automatically after they work on it |
| chat | string | yes | Chat name from carry_list_chats |
| emails | array | – | Not paired: Google emails them a link |
| handoff | string | – | Markdown summary for whoever continues it |
| link | boolean | – | Anyone with the link can open it |
| to | array | – | Paired friends (names): goes into their carry inbox. Preferred over emails. |
No output schema declared.
No examples provided.
carry_share_project Share a project ~233
Share a whole project: chosen chats, Claude Code memory notes, CLAUDE.md/AGENTS.md and a handoff. First call carry_list_projects with the name and confirm with the user which chats to include (related chats are not included unless added). Write a project-level handoff (goal, architecture, decisions, status, next steps) and pass it. The code itself travels via git.
| Name | Type | Req | Description |
|---|---|---|---|
| add | array | – | Extra chat names to include, e.g. related chats |
| auto_return | boolean | – | – |
| chats | number | – | How many of the newest chats started in the project to include (default 5) |
| dir | string | – | Deprecated: same as project |
| emails | array | – | – |
| handoff | string | – | – |
| link | boolean | – | – |
| project | string | – | Project name from carry_list_projects, or an absolute folder path |
| related | boolean | – | Include all related chats |
| skip | array | – | Chat names to leave out |
| to | array | – | Paired friends (names): goes into their carry inbox |
No output schema declared.
No examples provided.
carry_share_summary Share this conversation ~104
Share THIS conversation from a chat app (Claude app, ChatGPT), whose history carry cannot read. Write a thorough handoff of the conversation so far and pass it as summary.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | – | – |
| link | boolean | – | – |
| name | string | yes | Short name, e.g. "auth bug in login" |
| summary | string | yes | Markdown: goal, what was done, current state, decisions and why, open questions, next steps |
No output schema declared.
No examples provided.
carry_status Carry status ~23
Show whether carry is set up on this computer and where shared chats go.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the carry MCP server?
carry runs locally as an npm package, launched with npx -y @heyvamz/carry mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @heyvamz/carry
claude mcp add vamzzisme-carry -- npx -y @heyvamz/carry mcp
What is the carry MCP server?
carry is an MCP server listed in the public MCP registry as io.github.vamzzisme/carry. AirDrop for AI chats and projects: send Claude Code or Codex sessions through your own Google Drive. This page covers its npm package (@heyvamz/carry).
Is the carry MCP server safe to use?
carry scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 carry MCP server expose?
carry exposes 12 tools: carry_status, carry_connect_google_drive, carry_list_chats, carry_share_chat, carry_add_friend, and 7 more. Their descriptions and schemas cost roughly 1,043 tokens of context every time the server is loaded.
Is the carry MCP server still maintained?
carry 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 carry MCP server under?
carry declares the Apache-2.0 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 carry MCP server?
VerifyMCP ran 16 checks on carry, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.