io.github.Lokeshwaranramu/quantaseal
NPM · @QUANTASEAL/MCP-SERVER · SCANNED SEP 25
Quantum-safe vault, encryption & compliance for AI agents. NIST FIPS 203/204 ML-KEM-768 + ML-DSA-65.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 91 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1584 tokens (~75/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "vault_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.Lokeshwaranramu/quantaseal MCP server?
io.github.Lokeshwaranramu/quantaseal runs locally as an npm package, launched with npx -y @quantaseal/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @quantaseal/mcp-server
claude mcp add lokeshwaranramu-quantaseal -- npx -y @quantaseal/mcp-server
{
"mcpServers": {
"lokeshwaranramu-quantaseal": {
"command": "npx",
"args": [
"-y",
"@quantaseal/mcp-server"
]
}
}
} {
"servers": {
"lokeshwaranramu-quantaseal": {
"command": "npx",
"args": [
"-y",
"@quantaseal/mcp-server"
]
}
}
} codex mcp add lokeshwaranramu-quantaseal -- npx -y @quantaseal/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lokeshwaranramu-quantaseal": {
"type": "local",
"command": [
"npx",
"-y",
"@quantaseal/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add lokeshwaranramu-quantaseal --command npx --arg -y --arg @quantaseal/mcp-server
mcp_servers:
lokeshwaranramu-quantaseal:
command: "npx"
args: ["-y", "@quantaseal/mcp-server"] {
"McpServers": {
"lokeshwaranramu-quantaseal": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@quantaseal/mcp-server"
]
}
}
} assistant mcp add lokeshwaranramu-quantaseal -t stdio -c npx -a -y @quantaseal/mcp-server
{
"mcpServers": {
"lokeshwaranramu-quantaseal": {
"command": "npx",
"args": [
"-y",
"@quantaseal/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@quantaseal/mcp-server@1.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
decrypt ~58
Decrypt a HybridCryptoEnvelope from the encrypt tool. Verifies both ML-DSA-65 PQC signature and HMAC-SHA-512 before decrypting.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | The complete HybridCryptoEnvelope from a previous encrypt call |
No output schema declared.
No examples provided.
encrypt ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | KEM algorithm (default: ML-KEM-768) |
| plaintext | string | yes | Text to encrypt |
No output schema declared.
No examples provided.
generate_compliance_report ~45
Generate a compliance report with evidence citations, control status, and a PDF download link. Evidence is sourced from the immutable audit log.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Compliance framework |
No output schema declared.
No examples provided.
get_cbom ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Response format: full JSON or executive summary (default: json) |
No output schema declared.
No examples provided.
get_compliance_score ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Compliance framework |
No output schema declared.
No examples provided.
get_metrics ~41
Get current API usage metrics - API call counts, throughput (req/min), latency percentiles (P50/P95/P99), vault statistics, and plan limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_readiness_score ~82
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_regulatory_alerts ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| severity | string | – | Filter by minimum severity (default: all) |
| unacknowledged_only | boolean | – | Return only alerts not yet acknowledged (default: false) |
No output schema declared.
No examples provided.
list_audit_logs ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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') |
No output schema declared.
No examples provided.
list_compliance_reports ~45
List previously generated compliance reports for a framework, including their status and download URLs. Defaults to SOC2.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | Compliance framework (default: SOC2) |
No output schema declared.
No examples provided.
list_integrations ~45
List all configured integrations for this tenant. Returns name, system type (Salesforce, SAP, AWS S3, Kafka, Postgres, etc.), status, and allowed operations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
proxy_request ~92
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).
| Name | Type | Req | Description |
|---|---|---|---|
| integration_id | string | yes | UUID of the integration |
| operation | string | yes | Operation to perform (must be listed in the integration's allowed_operations) |
| payload | object | yes | Operation-specific payload |
No output schema declared.
No examples provided.
quantaseal_health ~65
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sign ~56
Sign text with ML-DSA-65 (FIPS 204) + HMAC-SHA-512. Returns the PQC signature, HMAC signature, and public key for verification.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Text to sign |
No output schema declared.
No examples provided.
test_integration ~44
Test connectivity to a configured integration. Verifies authentication without executing data operations. Returns status and latency_ms.
| Name | Type | Req | Description |
|---|---|---|---|
| integration_id | string | yes | UUID of the integration to test |
No output schema declared.
No examples provided.
vault_delete ~45
Soft-delete a vault entry. Entry is deactivated and excluded from list results. Logged in the audit trail.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | UUID of the vault entry to delete |
No output schema declared.
No examples provided.
vault_list ~46
List vault entries (metadata only - no plaintext). Use vault_unseal to retrieve the actual credential.
| Name | Type | Req | Description |
|---|---|---|---|
| include_inactive | boolean | – | Include soft-deleted entries (default: false) |
No output schema declared.
No examples provided.
vault_rotate ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | UUID of the vault entry to rotate |
No output schema declared.
No examples provided.
vault_seal ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| credential_type | string | yes | Credential type |
| metadata | object | – | Optional metadata to store alongside the credential |
| name | string | yes | Human-readable label (e.g. 'aws-prod-keys') |
| plaintext | object | yes | Credential key-value pairs (e.g. {"key": "sk-abc123"}) |
| ttl_days | number | – | Optional TTL in days (1–365). Omit for no expiry. |
No output schema declared.
No examples provided.
vault_unseal ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | UUID of the vault entry to unseal |
No output schema declared.
No examples provided.
verify_signature ~110
Verify an ML-DSA-65 + HMAC-SHA-512 signature from the sign tool. Reports validity of both the PQC signature and HMAC independently.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Original text that was signed |
| hmac_signature | string | yes | Base64-encoded HMAC-SHA-512 signature |
| public_key | string | yes | Base64-encoded public key from the sign result |
| signature | string | yes | Base64-encoded ML-DSA-65 signature |
No output schema declared.
No examples provided.
What is the io.github.Lokeshwaranramu/quantaseal MCP server?
io.github.Lokeshwaranramu/quantaseal is an MCP server listed in the public MCP registry as io.github.Lokeshwaranramu/quantaseal. Quantum-safe vault, encryption & compliance for AI agents. NIST FIPS 203/204 ML-KEM-768 + ML-DSA-65. This page covers its npm package (@quantaseal/mcp-server).
Is the io.github.Lokeshwaranramu/quantaseal MCP server safe to use?
io.github.Lokeshwaranramu/quantaseal scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Lokeshwaranramu/quantaseal MCP server expose?
io.github.Lokeshwaranramu/quantaseal exposes 21 tools: quantaseal_health, vault_seal, vault_unseal, vault_list, vault_rotate, and 16 more. Their descriptions and schemas cost roughly 1,584 tokens of context every time the server is loaded.
Is the io.github.Lokeshwaranramu/quantaseal MCP server still maintained?
io.github.Lokeshwaranramu/quantaseal is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Lokeshwaranramu/quantaseal MCP server under?
io.github.Lokeshwaranramu/quantaseal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.