quantakrypto pqc-tools

Deterministically attach your triage verdicts to their findings and re-sort by exposure (highest first). Never suppresses. Pass the same 'findings' array you triaged plus a 'verdicts' array of { fingerprint, exposureScore, priority, rationale }.

Deterministically VERIFY a proposed fix before writing it — runs the same patch-policy + verify_fix + blast-radius gates as `qremediate` (offline, no key, no network). Give the finding, the file's current content, and your proposed FULL corrected content; returns approved:true only if the patch is in-policy, clears the finding, adds no new finding, introduces no network/exec sink, and is bounded in size. This does NOT write the file — you write it, only when approved, and never auto-merge.

Check whether a package is in quantakrypto's known quantum-vulnerable dependency database (the classical crypto it exposes). Provide 'name' and optional 'ecosystem' (default npm).

Explain a quantakrypto finding and its post-quantum remediation. Provide a ruleId (e.g. 'forge-rsa-keygen', 'elliptic-ec', 'node-rsa', 'pem-ec-private-key') and/or an algorithm (e.g. 'RSA', 'ECDSA'). The ruleId is resolved against the core detector set, so library and config rules explain correctly.

Scan a path and emit a CycloneDX 1.6 Cryptographic Bill of Materials (CBOM) of the classical cryptographic assets found, for compliance / supply-chain tooling. Reads the filesystem, so it is gated like scan_path over HTTP.

Return before/after code examples for migrating a classical algorithm to a post-quantum / hybrid replacement. Provide an 'algorithm' (RSA, ECDH, ECDSA, …) or a 'ruleId' from a finding.

Produce a post-quantum readiness inventory for a path: a 0-100 readiness score plus counts of cryptographic findings by algorithm, category, and severity.

List the quantakrypto detector catalog: every detector id and what it looks for.

Scan a path and return a deterministic, prioritized post-quantum migration plan: findings grouped by algorithm, ordered harvest-now-decrypt-later first, each with its PQC target and the readiness-score impact. Reads the filesystem, so it is gated like scan_path over HTTP.

Actively probe ONE live TLS/SSH endpoint YOU OWN for post-quantum readiness (PQC-hybrid key exchange X25519MLKEM768, classical certificate posture). REQUIRES an ownership attestation: set i_own_this=true to confirm you are authorized to test the target. Refuses CIDR ranges / wildcards / lists — one host at a time. Performs only a benign, unauthenticated handshake and never modifies the endpoint. NOTE: this is the ONLY quantakrypto MCP tool that opens a network connection; the server is otherwise offline. Over HTTP it is disabled unless the operator sets QUANTAKRYPTO_MCP_ALLOW_NETWORK=1.

Produce a deterministic remediation REQUEST bundle (rubric + fix schema + per-finding metadata + fingerprints) for YOU (the host agent) to fix. This tool calls no model and needs no key. For each finding, propose the corrected FULL file content, then VERIFY with verify_fix and keep only fixes that clear the finding. Never touch files with secrets; never auto-merge. Pass 'findings' from scan_path --format json.

Scan a file or directory for classical (quantum-vulnerable) asymmetric cryptography using quantakrypto. Returns a readiness summary and findings.

Compute the readiness-score and HNDL change between two finding sets (e.g. before and after a migration). Pass 'before' and 'after' as arrays of findings from scan_path --format json.

Recommend a post-quantum / hybrid migration. Provide an 'algorithm' (e.g. RSA, ECDH, ECDSA) or free-text 'context' describing the usage. Set 'tier' to 'category-5' for CNSA 2.0 / national-security systems.

Produce a deterministic triage REQUEST bundle (rubric + verdict schema + per-finding metadata) for YOU (the host agent) to reason over. This tool does NOT call any model and needs no API key. Assess each finding's real-world exposure, then call apply_triage with your verdicts. Pass 'findings' as an array from scan_path --format json.

Run the quantakrypto detectors over a code snippet (NOT the filesystem) and report any classical crypto that remains. Use this to confirm an edit actually removed the quantum-vulnerable usage. Provide 'code' plus a 'language' or 'filename'.