quantakrypto pqc-tools
This server provides a comprehensive suite of tools for assessing, planning, and managing post-quantum cryptography (PQC) readiness in codebases and live systems.
Scan & Inventory
scan_path— Scan a file/directory for classical (quantum-vulnerable) asymmetric cryptography; returns a summary or raw JSON findings.inventory_crypto— Produce a 0–100 post-quantum readiness score with finding counts broken down by algorithm, category, and severity.generate_cbom— Emit a CycloneDX 1.6 Cryptographic Bill of Materials (CBOM) of all classical cryptographic assets, for compliance and supply-chain tooling.check_dependency— Check if a package is in the known quantum-vulnerable dependency database.
Migration Planning & Recommendations
plan_migration— Generate a prioritized migration plan ordered by harvest-now-decrypt-later (HNDL) risk, with PQC targets and readiness-score impact per finding.suggest_hybrid— Recommend a post-quantum/hybrid migration strategy for a given classical algorithm (supports CNSA 2.0 / national-security tier).get_fix_examples— Retrieve before/after code examples for migrating away from a classical algorithm.explain_finding— Get a detailed explanation of a finding (by ruleId or algorithm) and its post-quantum remediation guidance.list_rules— Browse the full detector catalog listing every detector ID and description.
Remediation & Verification
remediate_findings— Produce a deterministic remediation request bundle (rubric, fix schema, per-finding metadata) for the host agent to execute fixes.apply_verified_patch— Verify a proposed fix through patch-policy, verify_fix, and blast-radius gates before writing; returnsapproved: trueonly if safe and effective.verify_fix— Run detectors over a code snippet to confirm quantum-vulnerable crypto has been removed.
Triage & Scoring
triage_findings— Produce a deterministic triage request bundle for the host agent to assess each finding's real-world exposure.apply_triage— Attach triage verdicts to findings and re-sort by exposure score (highest first); never suppresses findings.score_delta— Compute the readiness-score and HNDL change between two sets of findings (e.g., before and after a migration).
Live Endpoint Probing
probe_endpoint— Probe a live TLS/SSH endpoint you own for PQC-hybrid key exchange and classical certificate posture. Requires ownership attestation (i_own_this: true); performs only a benign unauthenticated handshake.
Scans C/C++ codebases for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Dart code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Elixir codebases for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Istio configuration files for quantum-vulnerable cryptography as part of infrastructure coverage.
Scans Kotlin code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Kubernetes configuration files for quantum-vulnerable cryptography as part of infrastructure coverage.
Scans MQTT message broker configuration for quantum-vulnerable cryptography as part of infrastructure coverage.
Scans OpenTofu infrastructure-as-code configurations for quantum-vulnerable cryptography as part of infrastructure coverage.
Scans PHP code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Python code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Ruby code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Rust code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Scala code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Solidity code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Swift code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
Scans Terraform infrastructure-as-code configurations for quantum-vulnerable cryptography as part of infrastructure coverage.
Scans TypeScript code for quantum-vulnerable asymmetric cryptography, returning findings and a readiness score.
quantakrypto-tools
Open-source post-quantum readiness tooling by quantakrypto. Find quantum-vulnerable cryptography in any codebase, wire post-quantum readiness into your editor and your CI, and conformance-test post-quantum implementations — with zero runtime dependencies (Node built-ins only).
Design goals: simple, clean, reusable code; zero runtime dependencies; everything documented, tested, and example-driven.
What's inside
Tool | What it does | Get it |
qScan ( | CLI that finds quantum-vulnerable crypto (RSA, (EC)DH, ECDSA, EdDSA, …) across 14 languages (JS/TS, Python, Go, Java/Kotlin/Scala, C#, Rust, Ruby, PHP, Elixir, C/C++, Swift, Objective-C, Dart, Solidity/Move/Cairo) and prints a readiness score. SARIF / JSON / CBOM / evidence (ISO 27001 A.8.24) / OpenVEX output, baselines, incremental & parallel scans. Compliance mandate gate: |
|
MCP ( | Model Context Protocol server that gives AI coding agents post-quantum readiness tools (16 tools — scan, inventory, explain, suggest-hybrid, CBOM, plan-migration, triage, remediate, probe-endpoint, …). Local stdio + hostable HTTP. |
|
Sieve ( | Conformance battery for ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) implementations, driven over a JSON stdin/stdout protocol. |
|
Action ( | GitHub Action that runs the qScan/Sieve/qProbe checks in CI, writes SARIF for code-scanning upload, annotates the diff, and fails the build only on new quantum-vulnerable crypto. |
|
agent ( | Optional, zero-dependency BYOK (bring-your-own-key) LLM client (native |
|
qProbe ( | Actively probes live TLS/SSH endpoints you own for post-quantum readiness — PQC-hybrid key exchange (X25519MLKEM768) and classical certificate posture. Gated behind an ownership attestation; reports, never modifies ("engine disposes"). See THREAT-MODEL. |
|
All of qScan, MCP, the Action, agent, and qProbe share the engine in
@quantakrypto/core (npm i @quantakrypto/core) — detectors,
the vulnerable-dependency DB, the readiness score, SARIF/JSON/CBOM/evidence/OpenVEX
reporting, and the
offline agent-plane primitives (context redactor, verify_fix gate, codemods, patch
policy). Sieve is standalone: it tests other implementations and implements no
crypto itself.
Infrastructure coverage. Beyond application source, the shared core engine
carries config-scope detectors for Terraform/OpenTofu IaC and cloud KMS, JSON
Web Keys, Kubernetes / cert-manager / Istio, CI/CD artifact & code signing
(cosign/GPG/jarsigner/codesign/minisign), secrets at rest (SOPS/age, PGP, Sealed
Secrets), message brokers (Kafka/MQTT), databases (pgcrypto, libpq sslmode), and
JOSE/JWE key management — so qscan, the Action, and MCP flag infrastructure
crypto with no extra install. qProbe adds the live-endpoint dimension (see the
table above). The narrative anchor for infrastructure is harvest now, decrypt
later: data and secrets captured today are decryptable once a CRQC exists.
Related MCP server: PiQrypt MCP Server
Quick start
# 1. Scan a codebase for quantum-vulnerable cryptography.
npx @quantakrypto/qscan ./
# 2. Give your AI coding agent post-quantum readiness tools.
claude mcp add quantakrypto npx @quantakrypto/mcp
# 3. Conformance-test a post-quantum implementation (adapter speaks the JSON protocol).
npx @quantakrypto/sieve --impl "node ./my-impl.js" --param ml-kem-768
# 4. Gate against a compliance mandate's dated deadlines (CNSA 2.0 / NIST IR 8547).
# Verdicts also ride in --format json/sarif/evidence; --policy lets an org
# acknowledge families it is knowingly migrating (exempt from early gating).
npx @quantakrypto/qscan ./ --mandate cnsa-2.0 [--policy .quantakrypto/crypto-policy.json]Add the CI gate by dropping
packages/action/examples/quantum-readiness.yml
into .github/workflows/, or wire it up directly:
- uses: quantakrypto/pqc-tools/packages/action@v1
with:
path: "."
severity-threshold: "high"Each package README has the full options reference and more examples: qScan · MCP · Sieve · Action · core · agent.
Using quantakrypto alongside a PQC library (liboqs / OQS)
quantakrypto does not implement post-quantum cryptography, by design — it is
the scanner, the CI gate, and the conformance harness you wrap around a real PQC
library like liboqs / Open Quantum Safe. They
compose: quantakrypto finds and gates classical crypto (qscan, the Action),
tells you what to migrate to and in what order (qscan --tier, MCP
plan_migration, qremediate), and conformance-tests the replacement
(sieve runs any ML-KEM/ML-DSA/SLH-DSA implementation against FIPS 203/204/205,
with exact-value KATs when you supply official NIST ACVP vectors). liboqs
supplies the primitives.
See the worked end-to-end walkthrough — scan → migrate → verify → gate — in
examples/liboqs-migration/.
Workspace layout
quantakrypto-tools/
├── packages/
│ ├── core/ @quantakrypto/core — shared engine (the contract lives in src/types.ts + src/index.ts)
│ ├── qscan/ @quantakrypto/qscan — CLI
│ ├── mcp/ @quantakrypto/mcp — MCP server (stdio now, HTTP scaffold for hosting)
│ ├── action/ @quantakrypto/action — GitHub Action
│ ├── sieve/ @quantakrypto/sieve — conformance battery + JSON protocol
│ ├── agent/ @quantakrypto/agent — opt-in BYOK LLM client (triage + remediation)
│ └── qprobe/ @quantakrypto/qprobe — active TLS/SSH endpoint probing (gated; the only prober)
├── docs/ architecture, hosted-MCP design, improvement roadmap
└── examples/ end-to-end examplesDevelopment
Requires Node ≥ 20.
npm install # links the workspaces
npm run build # tsc --build (project references)
npm test # node:test across all packagesThe toolchain is intentionally tiny: TypeScript + tsx (to run node:test on
.ts) are the only dev dependencies; there are no runtime dependencies.
Documentation & compliance
Full documentation lives in docs/:
Objectives & scope — what the toolchain is for, what each library does, the load-bearing decisions, and the deliberate scope boundaries. Start here.
Architecture decisions — the immutable "why" behind each load-bearing choice (zero deps, shared core contract, two-plane agent, …).
Standards & compliance — what the tools touch and could align to: NIST FIPS 203/204/205, SP 800-208, CNSA 2.0, SARIF, CWE, ISO/IEC 27001 (A.8.24), Common Criteria, FIPS 140-3, EU DORA/NIS2, US M-23-02 / NSM-10, and OSS assurance (SLSA, OpenSSF Scorecard, SPDX/REUSE).
Governance: Contributing · Security · Code of Conduct · Changelog.
License
Apache-2.0. The methodology is open; the assessments, attestation reports, and deliverables are where the quantakrypto practice lives.
Support & training
Questions, commercial support, or post-quantum readiness training for your team — visit quantakrypto.com or email hello@quantakrypto.com.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceEnables AI assistants to perform quantum-resistant cryptographic operations using NIST-standardized algorithms including ML-KEM, ML-DSA, and SPHINCS+. Supports key generation, encryption, digital signatures, and security analysis for post-quantum cryptography research and development.1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to sign decisions with post-quantum cryptographic proofs and maintain secure audit trails for compliance. It provides tools for stamping events, verifying chain integrity, and exporting audit data across industries like finance and healthcare.457MIT
- AlicenseAqualityAmaintenanceMCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.143815Apache 2.0
- AlicenseAqualityBmaintenanceAgent-native "safe to ship?" security gate for AI-generated code. Uses real parsers and inter-rocedural taint analysis (JS/TS, Python, Go) to flag the classes AI coding agents get wrong — secrets, SQL injection, SS, SSRF, path traversal, command injection, weak JWT/CORS — and ranks findings by confidence. Exposes a scan tool over MCP.192MIT
Related MCP Connectors
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Zero-install security baseline for AI coding agents — OWASP/CWE-cited rules over MCP.
Production-grade cryptography toolkit with 31 MCP tools for classical, PQC, and KMS workflows.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/quantakrypto/pqc-tools'
If you have feedback or need assistance with the MCP directory API, please join our Discord server