Connect-MCP

quantakrypto pqc-tools

io.github.quantakrypto/pqc-tools · v0.5.2

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

MCPremotelocal · npmno credentialsFiles & storageCrypto

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 11 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 83/100

What it does: 11 tools · 6 read, 0 write · Developer tools, Files & storage, Crypto

Test call list_rules: needs a key: rpc error: Unauthorized: Authentication required (992 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: 0
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://mcp.quantakrypto.com/mcp
Package
registry:   npm
identifier: @quantakrypto/mcp
version:    0.5.2
transport:  stdio

Tools

11 tools listed at last check
  • 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'.

Badge

Connect-MCP badge for io.github.quantakrypto/pqc-tools

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.quantakrypto/pqc-tools.svg)](https://clawy.uk/mcp/s/io.github.quantakrypto/pqc-tools)

Repository