# io.github.Lokeshwaranramu/quantaseal (npm · @quantaseal/mcp-server)

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

- Trust score: 48/100 (low)
- Change this week: +26
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@quantaseal/mcp-server`: 48/100 (this document), [markdown](https://verifymcp.io/servers/lokeshwaranramu-quantaseal/quantaseal-mcp-server.md), [page](https://verifymcp.io/servers/lokeshwaranramu-quantaseal/quantaseal-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@quantaseal/mcp-server`
- Version: `1.1.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 33/100
  - Malware scan not yet available for this package.
  - CVE check failed: a known medium-severity CVE affects @hono/node-server 1.19.17, reached via @modelcontextprotocol/sdk > @hono/node-server. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 38 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1584 tokens (~75/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add lokeshwaranramu-quantaseal -- npx -y @quantaseal/mcp-server
```

### Codex

```bash
codex mcp add lokeshwaranramu-quantaseal -- npx -y @quantaseal/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lokeshwaranramu-quantaseal": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@quantaseal/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lokeshwaranramu-quantaseal --command npx --arg -y --arg @quantaseal/mcp-server
```

### Hermes

```yaml
mcp_servers:
  lokeshwaranramu-quantaseal:
    command: "npx"
    args: ["-y", "@quantaseal/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "lokeshwaranramu-quantaseal": {
      "command": "npx",
      "args": [
        "-y",
        "@quantaseal/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 48, +48)

- [security regression] GHSA-frvp-7c67-39w9 affects this package: medium
- [security regression] Provenance: unverified → fail
- [security regression] Known CVEs: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional] Licence: MIT

### 2026-08-01 (score 0, −16)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-31 (score 16, −6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 22)

First indexed and scored.

## MCP tools (21)

### `quantaseal_health` (~65 tokens)

Check QuantaSeal API health and PQC algorithm status. Returns service health for Database, Redis, KMS, and Crypto Pool, plus the active post-quantum algorithms (ML-KEM-768, ML-DSA-65, AES-256-GCM).

### `vault_seal` (~143 tokens)

Seal (encrypt and store) a credential using ML-KEM-768 + AES-256-GCM + ML-DSA-65 triple-layer encryption. Tenant isolation is enforced by the API key. Returns the vault entry UUID.

Input parameters:

- `credential_type` (string, required): Credential type
- `metadata` (object): Optional metadata to store alongside the credential
- `name` (string, required): Human-readable label (e.g. 'aws-prod-keys')
- `plaintext` (object, required): Credential key-value pairs (e.g. {"key": "sk-abc123"})
- `ttl_days` (number): Optional TTL in days (1–365). Omit for no expiry.

### `vault_unseal` (~70 tokens)

Unseal (decrypt and retrieve) a credential. Verifies ML-DSA-65 signature and HMAC-SHA-512 before any decryption. Every call is logged in the tamper-evident audit trail.

Input parameters:

- `entry_id` (string, required): UUID of the vault entry to unseal

### `vault_list` (~46 tokens)

List vault entries (metadata only - no plaintext). Use vault_unseal to retrieve the actual credential.

Input parameters:

- `include_inactive` (boolean): Include soft-deleted entries (default: false)

### `vault_rotate` (~60 tokens)

Rotate encryption keys for a vault entry. The credential is decrypted with current keys and immediately re-encrypted with fresh keys. Old entry is deactivated. Returns old and new entry IDs.

Input parameters:

- `entry_id` (string, required): UUID of the vault entry to rotate

### `vault_delete` (~45 tokens)

Soft-delete a vault entry. Entry is deactivated and excluded from list results. Logged in the audit trail.

Input parameters:

- `entry_id` (string, required): UUID of the vault entry to delete

### `encrypt` (~79 tokens)

Encrypt text using ML-KEM-768 + AES-256-GCM (FIPS 203). Returns a HybridCryptoEnvelope with ciphertext and ML-DSA-65 signature. Store the full envelope to decrypt later.

Input parameters:

- `algorithm` (string): KEM algorithm (default: ML-KEM-768)
- `plaintext` (string, required): Text to encrypt

### `decrypt` (~58 tokens)

Decrypt a HybridCryptoEnvelope from the encrypt tool. Verifies both ML-DSA-65 PQC signature and HMAC-SHA-512 before decrypting.

Input parameters:

- `envelope` (object, required): The complete HybridCryptoEnvelope from a previous encrypt call

### `sign` (~56 tokens)

Sign text with ML-DSA-65 (FIPS 204) + HMAC-SHA-512. Returns the PQC signature, HMAC signature, and public key for verification.

Input parameters:

- `data` (string, required): Text to sign

### `verify_signature` (~110 tokens)

Verify an ML-DSA-65 + HMAC-SHA-512 signature from the sign tool. Reports validity of both the PQC signature and HMAC independently.

Input parameters:

- `data` (string, required): Original text that was signed
- `hmac_signature` (string, required): Base64-encoded HMAC-SHA-512 signature
- `public_key` (string, required): Base64-encoded public key from the sign result
- `signature` (string, required): Base64-encoded ML-DSA-65 signature

### `list_integrations` (~45 tokens)

List all configured integrations for this tenant. Returns name, system type (Salesforce, SAP, AWS S3, Kafka, Postgres, etc.), status, and allowed operations.

### `test_integration` (~44 tokens)

Test connectivity to a configured integration. Verifies authentication without executing data operations. Returns status and latency_ms.

Input parameters:

- `integration_id` (string, required): UUID of the integration to test

### `proxy_request` (~92 tokens)

Execute an operation through an integration proxy. The credential is automatically unsealed from the vault, the operation is performed, and the response is encrypted. Only operations in allowed_operations are permitted (default-deny policy).

Input parameters:

- `integration_id` (string, required): UUID of the integration
- `operation` (string, required): Operation to perform (must be listed in the integration's allowed_operations)
- `payload` (object, required): Operation-specific payload

### `get_compliance_score` (~76 tokens)

Get the current compliance score (0–100) with grade and control breakdown. Supported: SOC2, ISO27001, PCI-DSS, HIPAA, GDPR, NIST-CSF, FedRAMP, APRA-CPS-234, NIST-800-53.

Input parameters:

- `framework` (string, required): Compliance framework

### `generate_compliance_report` (~45 tokens)

Generate a compliance report with evidence citations, control status, and a PDF download link. Evidence is sourced from the immutable audit log.

Input parameters:

- `framework` (string, required): Compliance framework

### `list_compliance_reports` (~45 tokens)

List previously generated compliance reports for a framework, including their status and download URLs. Defaults to SOC2.

Input parameters:

- `framework` (string): Compliance framework (default: SOC2)

### `list_audit_logs` (~156 tokens)

Query the immutable audit trail. Logs are protected by a SHA3-256 hash chain + ML-DSA-65 signatures - tamper-evident and exportable for compliance evidence. Filter by action, date range, or actor.

Input parameters:

- `action` (string): Filter by action (e.g. 'vault.seal', 'encryption.encrypt', 'proxy.outbound')
- `end_date` (string): ISO 8601 end date (e.g. '2026-12-31')
- `limit` (number): Number of entries (default: 50, max: 500)
- `start_date` (string): ISO 8601 start date (e.g. '2026-01-01')

### `get_metrics` (~41 tokens)

Get current API usage metrics - API call counts, throughput (req/min), latency percentiles (P50/P95/P99), vault statistics, and plan limits.

### `get_readiness_score` (~82 tokens)

Get this tenant's Quantum Readiness Score (0–100) with a letter grade and a breakdown across 5 pillars: Encryption (PQC algorithm coverage), Key Management (rotation + TTL), Integrations (PQC plane coverage), Compliance (framework scores), and Audit (log completeness). Use this to assess and report on post-quantum migration progress.

### `get_regulatory_alerts` (~125 tokens)

Retrieve active post-quantum regulatory alerts and compliance change notifications. Covers APRA CPS 234, NIST SP 800-131A, CNSS Policy 15, ENISA PQC guidelines, and ISO/IEC 18033. Returns severity, affected frameworks, required action, and deadline for each alert. Use this to stay current on regulatory changes that require cryptographic updates.

Input parameters:

- `severity` (string): Filter by minimum severity (default: all)
- `unacknowledged_only` (boolean): Return only alerts not yet acknowledged (default: false)

### `get_cbom` (~101 tokens)

Get the Cryptographic Bill of Materials (CBOM) for all integrations configured in this tenant. Returns algorithm coverage, PQC migration status (quantum-safe / hybrid / classical-only / unknown), and remediation priority for each connector. Use this to identify which systems still use classical-only cryptography and are at risk from 'Harvest Now, Decrypt Later' attacks.

Input parameters:

- `format` (string): Response format: full JSON or executive summary (default: json)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/lokeshwaranramu-quantaseal/quantaseal-mcp-server#diagnostics

## Score history

- 2026-08-03: 48
- 2026-08-02: 48
- 2026-08-01: 0
- 2026-07-31: 16
- 2026-07-30: 22
- 2026-07-28: 22
- 2026-07-27: 22

## Links

- npm package: https://www.npmjs.com/package/@quantaseal/mcp-server
- Socket report: https://socket.dev/npm/package/@quantaseal/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/lokeshwaranramu-quantaseal/quantaseal-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/lokeshwaranramu-quantaseal/quantaseal-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/lokeshwaranramu-quantaseal/quantaseal-mcp-server