io.github.raullenchai/vnsh
NPM · VNSH-MCP · SCANNED SEP 21
Portable workspaces for AI agents: one encrypted link any agent can read and write
Available components
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 96 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 14 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 805 tokens (~115/item across 7 items; 7 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 Management90
- Stability observed for 27 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the io.github.raullenchai/vnsh MCP server?
io.github.raullenchai/vnsh runs locally as an npm package, launched with npx -y vnsh-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 · vnsh-mcp
claude mcp add raullenchai-vnsh -- npx -y vnsh-mcp
{
"mcpServers": {
"raullenchai-vnsh": {
"command": "npx",
"args": [
"-y",
"vnsh-mcp"
]
}
}
} {
"servers": {
"raullenchai-vnsh": {
"command": "npx",
"args": [
"-y",
"vnsh-mcp"
]
}
}
} codex mcp add raullenchai-vnsh -- npx -y vnsh-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"raullenchai-vnsh": {
"type": "local",
"command": [
"npx",
"-y",
"vnsh-mcp"
],
"enabled": true
}
}
} openclaw mcp add raullenchai-vnsh --command npx --arg -y --arg vnsh-mcp
mcp_servers:
raullenchai-vnsh:
command: "npx"
args: ["-y", "vnsh-mcp"] {
"McpServers": {
"raullenchai-vnsh": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"vnsh-mcp"
]
}
}
} assistant mcp add raullenchai-vnsh -t stdio -c npx -a -y vnsh-mcp
{
"mcpServers": {
"raullenchai-vnsh": {
"command": "npx",
"args": [
"-y",
"vnsh-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 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.
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 Sept 2026 · Analysed npm/vnsh-mcp@1.3.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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
vnsh_read ~87
Securely retrieves and decrypts content from a vnsh URL. Use this tool whenever the user provides a vnsh.dev link or any URL with #k= and &iv= in the fragment. The content is decrypted locally - the server never sees the decryption key.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The full vnsh URL including the hash fragment (#k=...&iv=...) |
No output schema declared.
No examples provided.
vnsh_share ~131
Encrypts text content locally and uploads it to vnsh, returning a shareable URL. Use this when output exceeds ~50 lines or ~2000 characters, when generating complete code files, or when the user wants portable/shareable output. ALWAYS prefer vnsh_share over dumping large content into chat. The content is encrypted before upload - the server only sees encrypted bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content to encrypt and share |
| host | string | – | Override the vnsh host URL |
| ttl | number | – | Time-to-live in hours (default: 24, max: 168) |
No output schema declared.
No examples provided.
vnsh_share_file ~114
Encrypts a local file and uploads it to vnsh, returning a shareable URL. Use this for images, screenshots, PDFs, binaries, or any file that should not be loaded into context. More efficient than vnsh_share for large or binary files.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Absolute path to the file to encrypt and share |
| host | string | – | Override the vnsh host URL |
| ttl | number | – | Time-to-live in hours (default: 24, max: 168) |
No output schema declared.
No examples provided.
vnsh_workspace_create ~144
Creates a shared workspace and returns one link that any agent can read AND write. Use this when work will continue somewhere else: handing a plan, status doc, design, or investigation to another agent or another session, or when the user says they will pick this up in a different tool. Unlike vnsh_share (a one-shot snapshot), a workspace keeps the same URL as its content evolves. Content is encrypted locally; the server never sees the key. Expires 24h after the last write.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Initial content. HTML renders as a page via vnsh_workspace_open. |
| host | string | – | Override the vnsh host URL |
No output schema declared.
No examples provided.
vnsh_workspace_open ~92
Decrypts a vnsh workspace to a local temp file and opens it in the browser. Use this when the user wants to LOOK at a workspace rather than have its content read into context — HTML reports, dashboards, and diagrams render properly this way. Rendering happens locally from file://, so nothing is exposed to any server.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full workspace URL including the #w= fragment |
No output schema declared.
No examples provided.
vnsh_workspace_read ~92
Reads the current content of a vnsh workspace URL (a /w/ link with a #w= fragment). Use this whenever the user provides such a link — it is how you pick up work another agent left for you. Returns the content and its version number; pass that version to vnsh_workspace_update to write safely.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full workspace URL including the #w= fragment |
No output schema declared.
No examples provided.
vnsh_workspace_update ~145
Replaces the content of a vnsh workspace, keeping the same URL. Use this to record progress so far, revise a shared plan, or leave the next agent an updated document. Writes are version-checked: if someone else wrote first, this returns their current content so you can merge it with yours and call this again.
| Name | Type | Req | Description |
|---|---|---|---|
| base_version | number | – | Version this edit is based on. Omit to read the latest first. Pass the version from vnsh_workspace_read when you have already merged against it. |
| content | string | yes | The full new content (replaces everything) |
| url | string | yes | Full workspace URL including the #w= fragment |
No output schema declared.
No examples provided.
What is the io.github.raullenchai/vnsh MCP server?
io.github.raullenchai/vnsh is an MCP server listed in the public MCP registry as io.github.raullenchai/vnsh. Portable workspaces for AI agents: one encrypted link any agent can read and write. This page covers its npm package (vnsh-mcp).
Is the io.github.raullenchai/vnsh MCP server safe to use?
io.github.raullenchai/vnsh scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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.raullenchai/vnsh MCP server expose?
io.github.raullenchai/vnsh exposes 7 tools: vnsh_read, vnsh_share, vnsh_share_file, vnsh_workspace_create, vnsh_workspace_read, and 2 more. Their descriptions and schemas cost roughly 805 tokens of context every time the server is loaded.
Is the io.github.raullenchai/vnsh MCP server still maintained?
io.github.raullenchai/vnsh is still listed as active in the MCP registry. We last reached this channel on 21 September 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.raullenchai/vnsh MCP server under?
io.github.raullenchai/vnsh declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.