Skip to content

quantakrypto pqc-tools

by quantakrypto · remote · local (npm) · no sign-in to list tools · v0.5.2 · published by GitHub user quantakrypto

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

Changes · 8
CompareRegistry entry

11 tools: 8 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http pqc-tools https://mcp.quantakrypto.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

11 tools

Changes things 8Claude Code: ask
  • apply_triageDeterministically attach your triage verdicts to their findings and re-sort by exposure (highest first).No findings

    Why it is in this group

    • The name "apply_triage" says "apply": a word for a change.
    Description, as the server wrote it
    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_patchDeterministically VERIFY a proposed fix before writing it — runs the same patch-policy + verify_fix + blast-radius gates as `qremediate` (offline, no key, no network).No findings

    Why it is in this group

    • The name "apply_verified_patch" says "apply": a word for a change.
    Description, as the server wrote it
    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_dependencyCheck whether a package is in quantakrypto's known quantum-vulnerable dependency database (the classical crypto it exposes).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).
  • remediate_findingsProduce a deterministic remediation REQUEST bundle (rubric + fix schema + per-finding metadata + fingerprints) for YOU (the host agent) to fix.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • score_deltaCompute the readiness-score and HNDL change between two finding sets (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_hybridRecommend a post-quantum / hybrid migration.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_findingsProduce a deterministic triage REQUEST bundle (rubric + verdict schema + per-finding metadata) for YOU (the host agent) to reason over.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • verify_fixRun the quantakrypto detectors over a code snippet (NOT the filesystem) and report any classical crypto that remains.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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'.
Only reads 3Claude Code: allow
  • explain_findingExplain a quantakrypto finding and its post-quantum remediation.No findings

    Why it is in this group

    • The name "explain_finding" says "explain": a word for reading.
    Description, as the server wrote it
    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_examplesReturn before/after code examples for migrating a classical algorithm to a post-quantum / hybrid replacement.No findings

    Why it is in this group

    • The name "get_fix_examples" says "get": a word for reading.
    Description, as the server wrote it
    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_rulesList the quantakrypto detector catalog: every detector id and what it looks for.No findings

    Why it is in this group

    • The name "list_rules" says "list": a word for reading.
    Description, as the server wrote it
    List the quantakrypto detector catalog: every detector id and what it looks for.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.5.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http pqc-tools https://mcp.quantakrypto.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pqc-tools__explain_finding",
      "mcp__pqc-tools__get_fix_examples",
      "mcp__pqc-tools__list_rules"
    ],
    "ask": [
      "mcp__pqc-tools__apply_triage",
      "mcp__pqc-tools__apply_verified_patch",
      "mcp__pqc-tools__check_dependency",
      "mcp__pqc-tools__remediate_findings",
      "mcp__pqc-tools__score_delta",
      "mcp__pqc-tools__suggest_hybrid",
      "mcp__pqc-tools__triage_findings",
      "mcp__pqc-tools__verify_fix"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as pqc-tools. Review it before you use it.