QNSQY
NPM · QNSQY
Linux only, local: post-quantum CBOM scan, encrypt to public keys, verify. Takes no secrets
Available components
Last scanned (19 hours ago)
Scores higher than 31% of npm servers
Category Security
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 Security100
- 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
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency10
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1278 tokens (~127/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 7.2.49 → 7.2.51 functional
- Package version: 7.2.49 → 7.2.50 functional
- 1 Nov 26 60
First indexed and scored.
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 4 Nov 2026 · Analysed npm/qnsqy@7.2.51
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 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
qnsqy_encrypt Encrypt a file ~213
Encrypt a file with quantum-safe encryption. Free algorithms (0 credits, no file limit): ML-KEM-512 on all tiers, ML-KEM-768 on Pro+, everything on Business. Strict profile: this tool takes no password, passphrase, private key, API key or payment token.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | AEAD: aes256-gcm (default) or xchacha20-poly1305 (Pro+) |
| compress | boolean | – | Compress before encrypting |
| file | string | yes | Path to input file |
| kem | string | – | KEM algorithm: ml-kem512 (free), ml-kem768, ml-kem1024, hqc-128/192/256 |
| output | string | – | Output path (default: {file}.qs) |
| paranoid | boolean | – | Size sealing: hide the exact size (padding to a Padme bucket of at least 1 KiB) |
| recipient | string | yes | Recipient public key file path |
No output schema declared.
No examples provided.
qnsqy_hash Hash a file ~106
Compute file hash (BLAKE3/SHA3/SHA256/etc). Always FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | blake3 (default), blake2b, blake2s, sha256, sha512, sha3-256, sha3-512, shake256 |
| file | string | yes | File or directory to hash |
| format | string | – | hex (default) or base64 |
| recursive | boolean | – | Hash directory recursively |
No output schema declared.
No examples provided.
qnsqy_hash_verify Check a file against a hash ~58
Verify file hash. Always FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Hash algorithm (default: blake3) |
| file | string | yes | File to verify |
| hash | string | yes | Expected hash value (hex or base64) |
No output schema declared.
No examples provided.
qnsqy_scan Scan for quantum-vulnerable cryptography ~521
Find classical crypto files; `format: cyclonedx` gives a CycloneDX 1.7 CBOM (JSON) of the cryptographic material found in files (not crypto in source code, binaries or network traffic), stating only what the scanner read: algorithms it assumes from a file type are marked as assumed. Inline results are cut at 10 KB, and a longer JSON report or CBOM is refused with an error: pass `output` to write the whole report to a file. `format: omb-csv|omb-xlsx|omb-json` writes the OMB M-23-02 inventory report of one system (the memo's nine items; omb-xlsx needs `output`; the memo excludes national security systems), with the system profile `omb_profile` and the omb_* values that override it. Free on all tiers (an account is needed). Strict profile: this tool takes no password, passphrase, private key, API key or payment token.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | Directory to scan |
| format | string | – | text (default), json, csv, html, markdown, cyclonedx (CycloneDX 1.7 CBOM, JSON), omb-csv, omb-xlsx, omb-json (OMB M-23-02 inventory report) |
| min_risk | string | – | Minimum risk level: safe, low, medium, high, critical |
| omb_data_types | string | – | OMB M-23-02 item 8: types of data |
| omb_fips199 | string | – | OMB M-23-02 item 2: low, moderate or high |
| omb_fisma_id | string | – | OMB M-23-02 item 1: FISMA system identifier (an identifier only) |
| omb_hva_id | string | – | OMB M-23-02 item 3: HVA identifier |
| omb_notes | string | – | OMB M-23-02 item 9: additional notes |
| omb_profile | string | – | OMB M-23-02 report: the system profile (TOML file) |
| omb_time_to_live | string | – | OMB M-23-02 item 8: time to live |
| output | string | – | Write the report to this file instead of returning it inline (inline results are limited to 10 KB) |
| recursive | boolean | – | Scan subdirectories (default: true) |
No output schema declared.
No examples provided.
qnsqy_status Show account and plan status ~18
Account & tier status. Always FREE.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qnsqy_usage Show usage ~17
Credit usage info. Always FREE.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qnsqy_verify Verify a signature ~42
Verify file signature. Always FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | File to verify (.qs with embedded signature) |
| key | string | yes | Public key file |
No output schema declared.
No examples provided.
qnsqy_verify_integrity Check an encrypted file's integrity ~35
Check .qs file integrity without password. Always FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | .qs file to check |
No output schema declared.
No examples provided.
qnsqy_verify_release Verify a release signature ~115
Verify a QNSQY release artifact's detached ML-DSA-87 signature against QNSQY's release public key. Always FREE. Strict profile: this tool takes no password, passphrase, private key, API key or payment token.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | string | yes | Path to the signed artifact (e.g. checksums.txt); verified byte-for-byte |
| signature | string | yes | Path to the ML-DSA-87 signature file (raw bytes or hex, typically <artifact>.sig) |
No output schema declared.
No examples provided.
qnsqy_version Show the QNSQY version ~29
Version info. Always FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| verbose | boolean | – | Show extended algorithm/feature info |
No output schema declared.
No examples provided.
How do I install the QNSQY MCP server?
QNSQY runs locally as an npm package, launched with npx -y qnsqy. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · qnsqy
claude mcp add quantumsequrity-qnsqy -- npx -y qnsqy
What is the QNSQY MCP server?
QNSQY is an MCP server listed in the public MCP registry as io.github.quantumsequrity/qnsqy. Linux only, local: post-quantum CBOM scan, encrypt to public keys, verify. Takes no secrets. This page covers its npm package (qnsqy).
Is the QNSQY MCP server safe to use?
QNSQY scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 QNSQY MCP server expose?
QNSQY exposes 10 tools: qnsqy_encrypt, qnsqy_verify, qnsqy_verify_release, qnsqy_hash, qnsqy_hash_verify, and 5 more. Their descriptions and schemas cost roughly 1,154 tokens of context every time the server is loaded.
Is the QNSQY MCP server still maintained?
QNSQY is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.