mcpbeat

quantakrypto pqc-tools MCP Server

io.github.quantakrypto/pqc-tools
answering

quantakrypto pqc-tools is answering right now. Last checked 11 min ago. 537 installs a week from npm. It exposes 11 tools. Last commit 30 Jul 2026.

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

Installs per day peak 296 · avg 57 · +7% w/w
a month agotoday
Uptime history 40 hours of history · worst hour 75%
40 hours agonow
98.9%
Uptime 24h
90 of 91 checks
11
Tools
read from the server
157 ms
Response time
average over 24h
537
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add pqc-tools --transport http https://mcp.quantakrypto.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "pqc-tools": {
      "url": "https://mcp.quantakrypto.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.pqc-tools]
url = "https://mcp.quantakrypto.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "pqc-tools": {
      "url": "https://mcp.quantakrypto.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "pqc-tools": {
      "url": "https://mcp.quantakrypto.com/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

apply
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.
dependency
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
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.
fix
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.
remediate
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.
rules
list_rules
List the quantakrypto detector catalog: every detector id and what it looks for.
score
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
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
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
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'.

Endpoints

URLTransportStateLatencyChecked
https://mcp.quantakrypto.com/mcp streamable-http answering 182 ms 11 min ago

quantakrypto pqc-tools — questions

Answers built from our own checks of this server.

What can quantakrypto pqc-tools do?
It exposes 11 tools, read directly from the server on our last check. Among them: apply_triage, apply_verified_patch, check_dependency, explain_finding, get_fix_examples, list_rules and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is quantakrypto pqc-tools working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 157 ms. The bar chart above shows every period we have measured.
How do I connect quantakrypto pqc-tools?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does quantakrypto pqc-tools need an API key?
No. quantakrypto pqc-tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is quantakrypto pqc-tools?
It answers our handshake in 157 ms on average, which is faster than 72% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use quantakrypto pqc-tools?
The npm package @quantakrypto/mcp was installed 537 times in the last week. Week over week that is +7%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is quantakrypto pqc-tools open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript and 9 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.