
Pqvault
io.github.pdaxtPublished by GitHub account pdaxtv2.1.0Updated Oct 27, 2026
Post-quantum secrets manager for AI agents. ML-KEM-768 + X25519 + AES-256-GCM.
Overview
A local, desktop-only MCP server that acts as a post-quantum secrets manager for AI agents, using ML-KEM-768, X25519 and AES-256-GCM.
- What you can do
- The listing names no tools, so capabilities are inferred from the description only.
- It presents itself as a secrets manager that AI agents can use to hold and handle secrets.
- Its cryptography combines ML-KEM-768, X25519 and AES-256-GCM for post-quantum key exchange and authenticated encryption.
- It runs as a local process on the user's machine over stdio.
- When to use it
- Consider it if you want an assistant to work with stored secrets through a local server whose design is meant to resist future quantum attacks. It is a narrow, single-purpose tool; most assistants will not need it unless secret handling is the task.
- Requirements
- Runs as a local stdio process on a desktop machine; no package, environment variables, headers or authentication are declared in the manifest, so the actual install and runtime requirements are not documented here.
Installation
In SourceWeft
- Open Pqvault 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
This repository has no README.
Tools
0Version history
1- v2.1.0LatestSep 16, 2026
Score
25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.