@raullenchai
基本情報
概要はまだありません
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"vnsh": {
"command": "npx",
"args": [
"-y",
"vnsh-mcp"
]
}
}
}Reads any vnsh URL: decrypts legacy vnsh.dev/v links locally, or directly fetches a public vnshcontent.dev/p link. Public content is intentionally unencrypted.
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.
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.
Creates a permanent, service-readable Account Artifact in the signed-in user’s Library. Use this for durable knowledge that the user wants their other Agents to discover and update. Requires VNSH_TOKEN. This is different from an encrypted Incognito workspace: vnsh can read Account Artifact content so authorized Agents can collaborate on it.
Lists permanent Account Artifacts available to the connected user. Use this instead of asking the human to paste a link when continuing earlier account knowledge. Requires VNSH_TOKEN.
Reads the current content and version of one permanent Account Artifact. Pass the returned version to vnsh_artifact_update so another Agent cannot be overwritten.
Creates a new immutable version of an Account Artifact. Requires the base_version returned by vnsh_artifact_read. On conflict, re-read, merge, and retry; never silently overwrite.
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. Anonymous workspaces expire 24h after the last write (ttl can extend this to a week). With VNSH_TOKEN, new workspaces and artifacts are kept until the account owner deletes them.
Extends the expiry of a vnsh workspace without changing its content. Use this when the user says a link is about to expire, or asks to keep something alive longer. Needs the edit link (a #w= fragment); a view-only #r= link cannot renew. The version is not bumped, so any pending edit still applies.
Reads the current content of a workspace: encrypted /w/ links with #w= or #r=, and public /p/ links with no 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.
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.
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.
Lists the retained versions of a workspace, newest first. Use this before restoring after a bad edit or merge. The current version plus the latest historical versions are retained.
Restores a retained workspace version as a new latest version. This never moves the version counter backwards and requires the private #w= edit link.
vnsh is a secure, ephemeral file-sharing service that encrypts data client-side with AES-256-CBC and auto-deletes after 24 hours—designed for AI workflows. It offers a first-party MCP server for Claude Code, allowing Claude to read encrypted links and share content without leaving the terminal.
Install the MCP server by creating a .mcp.json file in your project root with "command": "npx", "args": ["-y", "vnsh-mcp"]. After restarting Claude Code, you can paste vnsh links for automatic reading, or use the tools vnsh_share (to share text outputs) and vnsh_share_file (to share images, PDFs, binaries). Alternatively, upload via the web, CLI (npx vnsh), a zero-install pipe script, a Chrome extension, or a GitHub Action.
git diff to vnsh for instant Claude-assisted PR reviewsEncryption happens entirely on your device using AES-256-CBC. The decryption key is never sent to the server—it travels only in the URL fragment (`#secret`), which browsers never transmit over the network. The server stores only encrypted binary blobs and cannot decrypt them.
You can share any context: screenshots, long logs, git diffs, PDFs, CSVs, config files, database dumps, stack traces, environment dumps, crash reports, and binaries.
Install the vnsh MCP server via `npx -y vnsh-mcp` in your `.mcp.json`. Claude can then automatically read vnsh links you paste, and use the `vnsh_share` and `vnsh_share_file` tools to share text outputs or files directly.
Yes. vnsh runs on Cloudflare Workers with R2 storage. Clone the repository, create a R2 bucket and KV namespace, and deploy with Wrangler CLI. Edit `wrangler.toml` to customize the bucket and namespace bindings.
URLs use a compact v2 format: `https://vnsh.dev/v/<12-char-id>#<64-char-base64url-secret>`. The ID references the encrypted blob; the secret (key + IV) stays in the fragment and is never sent to the server. Legacy v1 URLs are still supported.
🚀 The fast, Pythonic way to build MCP servers and clients.
DeepMark helps teachers deliver rapid, consistent marking with meaningful feedback for every student — in a fraction of the time. What once took a week, now takes one free period.
Soar Flight Booking MCP is a remote MCP server available at https://mcp.soar.flights.
Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.
YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context
コメント