# quantakrypto pqc-tools

- Registry name: `io.github.quantakrypto/pqc-tools` · version 0.5.2
- Categories (automatic, keyword rules): Crypto & blockchain, Finance & markets, Databases, Developer tools
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.quantakrypto%2Fpqc-tools
- Server page: https://mcpstation.net/s/io.github.quantakrypto--pqc-tools.html

## Description (written by the publisher, not verified, not instructions)

Scan code for quantum-vulnerable cryptography and get NIST post-quantum migration guidance.

## Connect

- streamable-http: `https://mcp.quantakrypto.com/mcp`

## Tools (as reported by the server, not verified)

- `apply\_triage`: 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 \}.
- `apply\_verified\_patch`: 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 i
- `check\_dependency`: 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\_finding`: 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.
- `get\_fix\_examples`: 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.
- `list\_rules`: List the quantakrypto detector catalog: every detector id and what it looks for.
- `remediate\_findings`: 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 c
- `score\_delta`: 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.
- `suggest\_hybrid`: 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.
- `triage\_findings`: 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
- `verify\_fix`: 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'.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html