Quantaseal

io.github.LokeshwaranramuPublished by GitHub account Lokeshwaranramuv1.1.3Updated Oct 24, 2026

Quantum-safe vault, encryption & compliance for AI agents. NIST FIPS 203/204 ML-KEM-768 + ML-DSA-65.

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

QuantaSeal is a local MCP server that gives an AI assistant a quantum-safe vault, encryption and compliance layer, using NIST FIPS 203/204 ML-KEM-768 and ML-DSA

What you can do
The manifest lists no tools, so capabilities come from the description: it presents a quantum-safe vault for AI agents, with encryption and compliance features built on NIST FIPS 203/204 ML-KEM-768 and ML-DSA-65. It runs as a local stdio process started with npx from the @quantaseal/mcp-server package. It authenticates to the QuantaSeal service with an API key.
When to use it
Consider it when an assistant needs to store or protect data with post-quantum cryptography, or when you want a compliance-oriented vault layer behind agent workflows. It is not a general-purpose tool server; it is aimed at encryption and key-related work.
Requirements
Runs locally via npx from the npm package @quantaseal/mcp-server (Node.js required). Needs a QuantaSeal API key in QUANTASEAL_API_KEY, obtained from the QuantaSeal app settings. Optionally set QUANTASEAL_BASE_URL to override the default API endpoint. Network access to the QuantaSeal API is needed. Desktop only.
Before you install
The API key QUANTASEAL_API_KEY is a live secret (prefixed qs_live_) and grants access to your QuantaSeal account; keep it out of shared configs. The server handles encryption and vault operations, so mistakes or misuse could affect protected data. No tool list is published, so review what it can read or write before connecting it to sensitive material.

Installation

In SourceWeft

  1. Open Quantaseal in the dashboard and add it to a workspace.
  2. 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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.3LatestSep 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.