ShareBox
NPM · SHAREBOX-CLI
Publish the web tools your agent builds to a self-hosted ShareBox and share them like a Google Doc
Available components
Last scanned (4 hours ago)
Scores higher than 39% of npm servers
Category Developer Tools
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
- 0 of 27 dependencies flagged as unhealthy. View diagnostics → Pass
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 (AGPL-3.0-or-later).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 645 tokens (~80/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 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 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.
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.
- 14 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 0.1.1 → 0.1.4 functional
- 9 Oct 26 25
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 17 Oct 2026 · Analysed npm/sharebox-cli@0.1.4
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 27 packages
| Packages resolved | 27 |
|---|---|
| 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 →
sharebox_create_project ~64
Create a starter folder for a new tool (sharebox.json and a public/index.html example that uses the SDK).
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | Absolute path of a new or empty folder. |
| name | string | yes | Name of the tool, shown to its users. |
No output schema declared.
No examples provided.
sharebox_guide ~40
How to build a tool for ShareBox: folder layout, SDK for identity and data, optional worker, limits. Read it before writing the tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sharebox_info ~47
Details of a tool: address, version and who it is shared with.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | The tool: absolute path of its folder, or its id, address or name. |
No output schema declared.
No examples provided.
sharebox_list ~22
List the tools the user can manage, with address and version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sharebox_publish ~133
Publish a tool's folder. The first time it creates the tool with its own HTTPS address; later it updates the same tool, keeping address and data. New tools are private.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | Absolute path of the tool's folder. |
| name | string | – | Name of the tool, only on the first publish (otherwise the one in sharebox.json). |
| tool | string | – | Optional: an existing tool (id, address or name) to update instead of the one in sharebox.json. Use it when you rebuilt the tool in a new folder, so the shared link stays the same. |
No output schema declared.
No examples provided.
sharebox_rollback ~79
Go back to the previous version of a tool, e.g. when the last publish broke it. The previous files are published again as a new version: same link, stored data unchanged. Calling it again undoes the rollback.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | The tool: absolute path of its folder, or its id, address or name. |
No output schema declared.
No examples provided.
sharebox_share ~122
Share a tool (or change the role of an existing share). Takes effect immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | "use" = can use (default); "manage" = can also republish and share. |
| tool | string | yes | The tool: absolute path of its folder, or its id, address or name. |
| with | string | yes | An email ("anna@company.com"), a domain ("@company.com": every Google Workspace account of that domain) or "anyone" (anyone with the link, still signing in with Google). |
No output schema declared.
No examples provided.
sharebox_unshare ~63
Remove a share. Takes effect immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | The tool: absolute path of its folder, or its id, address or name. |
| with | string | yes | The email, "@domain" or "anyone", as in the share. |
No output schema declared.
No examples provided.
How do I install the ShareBox MCP server?
ShareBox runs locally as an npm package, launched with npx -y sharebox-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sharebox-cli
claude mcp add zalaso-sharebox -- npx -y sharebox-cli
What is the ShareBox MCP server?
ShareBox is an MCP server listed in the public MCP registry as io.github.zalaso/sharebox. Publish the web tools your agent builds to a self-hosted ShareBox and share them like a Google Doc. This page covers its npm package (sharebox-cli).
Is the ShareBox MCP server safe to use?
ShareBox scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 ShareBox MCP server expose?
ShareBox exposes 8 tools: sharebox_guide, sharebox_create_project, sharebox_publish, sharebox_list, sharebox_info, and 3 more. Their descriptions and schemas cost roughly 570 tokens of context every time the server is loaded.
Is the ShareBox MCP server still maintained?
ShareBox is still listed as active in the MCP registry. We last reached this channel on 17 October 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 ShareBox MCP server under?
ShareBox declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.