# quantakrypto pqc-tools MCP server

> Provides AI coding agents with tools to scan codebases for quantum-vulnerable cryptography and plan post-quantum migration.

- Repository: https://github.com/quantakrypto/pqc-tools
- Page: https://hostedmcp.org/servers/quantakrypto/pqc-tools
- Transport: stdio, remote
- Stars: 16
- License: Apache-2.0
- Latest version: 0.5.2

## Install

### Claude Code

```sh
claude mcp add pqc-tools -- npx -y @quantakrypto/mcp
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "pqc-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@quantakrypto/mcp"
      ]
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "pqc-tools": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@quantakrypto/mcp"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"pqc-tools","type":"stdio","command":"npx","args":["-y","@quantakrypto/mcp"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "pqc-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@quantakrypto/mcp"
      ]
    }
  }
}
```

### Codex

```sh
codex mcp add pqc-tools -- npx -y @quantakrypto/mcp
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.pqc-tools]
command = "npx"
args = ["-y", "@quantakrypto/mcp"]
```

### Gemini CLI

```sh
gemini mcp add -s user pqc-tools npx -- -y @quantakrypto/mcp
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "pqc-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@quantakrypto/mcp"
      ]
    }
  }
}
```

## Tools (16)

- `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 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_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.
- `generate_cbom`: 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.
- `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.
- `inventory_crypto`: 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_rules`: List the quantakrypto detector catalog: every detector id and what it looks for.
- `plan_migration`: 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.
- `probe_endpoint`: 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.
- `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 clear the finding. Never touch files with secrets; never auto-merge. Pass 'findings' from scan_path --format json.
- `scan_path`: Scan a file or directory for classical (quantum-vulnerable) asymmetric cryptography using quantakrypto. Returns a readiness summary and findings.
- `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 array from scan_path --format json.
- `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'.

## FAQ

### What can the MCP server do?

The MCP server provides 16 tools for AI coding agents, including scanning, inventorying, explaining vulnerabilities, suggesting hybrid approaches, and planning migrations.

### Does this tool implement post-quantum cryptography?

No, the tool is designed to be a scanner, CI gate, and conformance harness rather than a cryptographic implementation itself.

### How many programming languages can be scanned?

The qScan tool can find quantum-vulnerable cryptography across 14 different languages.

### Can it scan infrastructure configuration?

Yes, the core engine includes detectors for Terraform/OpenTofu IaC, cloud KMS, Kubernetes, and various secrets management tools.
