volta-mcp-server
Related Servers
Alternatives to volta-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create end-to-end encrypted, self-destructing notes that can be securely shared via a one-click link, ensuring secrets are never stored in plain text in chat history.1-
- AlicenseAqualityBmaintenanceLets AI agents encrypt a password, API key, or note locally, pay a small USDC fee over x402 on Base, and share a single-use link that can be opened exactly once and is destroyed on read. Reading is free, expiring unread secrets are cleaned up, and the server only ever stores ciphertext.10MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted, zero-knowledge encrypted, self-destructing secrets for secure agent-to-agent coordination3AGPL 3.0
- AlicenseAqualityBmaintenanceShare encrypted, self-destructing secrets from your AI agent. Zero-knowledge E2E encryption. Agent-blind input sources (env:, file:, dotenv:) keep secrets out of LLM context.413 npm1MIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents a shared, encrypted workspace they can create, list, read, update, version-history, restore, renew and share via a single link that multiple agents and people can read and write. Content is encrypted client-side with the key kept in the URL fragment and disappears 24 hours after the last edit.7 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create, read, update, list, and restore shared encrypted workspaces and one-shot links that both people and other agents can open and edit through a single URL. Content is encrypted client-side, version-checked on write to prevent clobbering, and expires 24 hours after the last edit.7 npmMIT
TDQS
Scored across 2 tools
The tools have clearly distinct purposes with no functional overlap: one creates secure notes while the other consumes them. An agent can easily distinguish between generating a new URL versus retrieving and destroying an existing note.
Both tools follow a consistent verb_noun pattern using snake_case (create_volta_note, read_volta_note), with identical resource naming ('volta_note') and parallel grammatical structure.
While two tools falls slightly below the typical optimal range, it is reasonable for this narrowly scoped one-time secret service where only creation and retrieval operations are relevant to the security model.
The tools cover the essential lifecycle (create and read-once-destroy) for secure note sharing. Minor potential gaps include missing expiration configuration or metadata retrieval, though these may be intentionally excluded for security.