
Volta Notes
io.github.iamredmhPublished by GitHub account iamredmhv1.1.1Updated Oct 24, 2026
Burn-after-read encrypted notes. E2E encrypted, decentralised on the Internet Computer.
Overview
Volta Notes MCP lets an assistant create and read burn-after-read, end-to-end encrypted notes so secrets can be handed over without landing in chat history.
- What you can do
- Create an encrypted note from a short secret and get back a one-time link
- Read a Volta note link, decrypt it locally and permanently destroy the note
- Hand secrets such as API keys or passwords between a user and an agent, or between agents, without pasting them into the conversation
- When to use it
- Use it when an agent needs a credential, API key or password at runtime and you want to avoid leaving it in conversation history or tool logs, or when an agent must pass a secret to a user or another agent through a self-destructing link.
- Requirements
- A local Node.js 18+ runtime and the npm package @voltanotes/mcp, registered with the client (for example via npx or a global install). Network access to the Volta Notes service on the Internet Computer. No account, login, API key or environment variable is needed.
Installation
In SourceWeft
- Open Volta Notes in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@voltanotes/mcp
MCP server for Volta Notes — create and read burn-after-read encrypted notes from any AI agent.
Notes are end-to-end encrypted using AES-256-GCM. The decryption key lives only in the URL fragment — it is never sent to any server. Notes are stored on the Internet Computer and permanently destroyed after a single read.
Why
AI agents regularly need sensitive information at runtime — API keys, passwords, credentials. Today, users paste these into chat where they're stored permanently in conversation history.
With this MCP server, the pattern becomes:
- User creates a note at voltanotes.com and sends the one-time URL
- Agent calls
read_volta_note— secret returned, note permanently destroyed - Nothing sensitive ever appears in chat history
Or in reverse — an agent can use create_volta_note to send credentials to a user via a self-destructing link.
Quick Start
Claude Code (CLI & Desktop App)
Step 1 — Install globally:
Step 2 — Register the server:
That's it. Restart Claude Code and the create_volta_note and read_volta_note tools will be available.
Why
claude mcp addinstead of editing config files? Claude Code reads MCP servers from its own registry, not from~/.claude/mcp.json. Using the CLI ensures the server is registered correctly. The-s userflag makes it available across all projects.
nodenot found? Use the full path: replacenodewith the output ofwhich node(e.g./usr/local/bin/node).
Claude Desktop (Standalone)
Add to your claude_desktop_config.json:
Other MCP-compatible clients
The npx config above works with any client that supports the standard command/args MCP format — including Cursor, Windsurf, Cline, Continue.dev, and others. Check your client's MCP documentation for where to add server config.
Hermes Agent (Nous Research)
Volta MCP works with Hermes Agent via its MCP integration. Add the server to your Hermes config (~/.hermes/config.yaml):
Restart Hermes and the create_volta_note and read_volta_note tools will be available to your agent.
Agent-to-agent use case: Hermes agents running autonomously often need to pass credentials between workflows without exposing them in logs or memory. Volta Notes is purpose-built for this — one agent creates a note, passes the one-time URL to the next, and the secret is destroyed on read. Nothing persists in conversation history or tool output logs.
See Hermes MCP documentation for full configuration options.
Windows (Claude Code CLI)
The $(npm root -g) syntax doesn't work in PowerShell or CMD. Use this instead:
Or use the Claude Desktop / npx method above, which works cross-platform.
Tools
create_volta_note
Creates an encrypted note and returns a one-time URL.
Returns: A voltanotes.com URL. The recipient opens it once, reads the content, and it's gone forever.
read_volta_note
Reads and permanently destroys a Volta note.
Returns: The decrypted note content. The note is permanently deleted from the canister — a second read will fail.
Agent Prompt Snippet
Add this to any agent's system prompt to enable secure credential handoff:
Security Model
- AES-256-GCM encryption happens locally before anything is sent to the canister
- The encryption key exists only in the URL fragment (
#...) — browsers and servers never transmit fragments - The ICP canister stores only ciphertext — even if compromised, all data is unreadable
- Notes are destroyed on first read. Unread notes expire after 7 days.
- No accounts, no login, no tracking
How It Works
Troubleshooting
Check if the server is connected
You should see volta: ... ✓ Connected. If not, see below.
Server not showing up
-
Did you use
claude mcp add? Editing~/.claude/mcp.jsonmanually won't work — Claude Code reads servers from its own registry. Always useclaude mcp addto register servers. -
Is
nodeon your PATH? Claude Code's shell has a minimal PATH. Ifnodeisn't found, use the full path: -
Restart required. After adding or changing an MCP server, fully restart Claude Code (quit and reopen).
How do I know if the server started?
The server logs Volta MCP server started to stderr on successful startup. Run claude mcp list to check connection status.
Requirements
- Node.js 18+ (uses built-in Web Crypto API)
License
MIT — Unprompted Labs
Source: README.md at commit 71190de
Tools
0Version history
1- v1.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts