Connect quantakrypto pqc-tools and your agent gets 11 tools, among them apply_triage, apply_verified_patch, check_dependency. It answers at https://mcp.quantakrypto.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 23 October 2026, succeeded.
Scan code for quantum-vulnerable cryptography and get NIST post-quantum migration guidance.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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, rationa Inputs: findings, verdicts |
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 cor Inputs: finding, originalContent, newContent |
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). Inputs: name, ecosystem |
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 Inputs: ruleId, algorithm |
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. Inputs: algorithm, ruleId |
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 con Inputs: 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. Inputs: before, after |
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. Inputs: algorithm, context, tier |
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 Inputs: findings |
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'. Inputs: code, language, filename |
Every block below points at https://mcp.quantakrypto.com/mcp. Pick your client and copy.
claude mcp add --transport http quantakrypto-pqc-tools https://mcp.quantakrypto.com/mcp
{
"mcpServers": {
"quantakrypto-pqc-tools": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.quantakrypto.com/mcp"]
}
}
}{
"mcpServers": {
"quantakrypto-pqc-tools": {
"url": "https://mcp.quantakrypto.com/mcp"
}
}
}{
"servers": {
"quantakrypto-pqc-tools": {
"type": "http",
"url": "https://mcp.quantakrypto.com/mcp"
}
}
}{
"context_servers": {
"quantakrypto-pqc-tools": {
"url": "https://mcp.quantakrypto.com/mcp"
}
}
}{
"mcpServers": {
"quantakrypto-pqc-tools": {
"serverUrl": "https://mcp.quantakrypto.com/mcp"
}
}
}{
"mcpServers": {
"quantakrypto-pqc-tools": {
"url": "https://mcp.quantakrypto.com/mcp"
}
}
}name: quantakrypto pqc-tools
version: 0.0.1
schema: v1
mcpServers:
- name: quantakrypto pqc-tools
type: streamable-http
url: https://mcp.quantakrypto.com/mcp{
"mcpServers": {
"quantakrypto-pqc-tools": {
"httpUrl": "https://mcp.quantakrypto.com/mcp"
}
}
}{
"mcpServers": {
"quantakrypto-pqc-tools": {
"type": "http",
"url": "https://mcp.quantakrypto.com/mcp"
}
}
}{
"mcpServers": {
"quantakrypto-pqc-tools": {
"url": "https://mcp.quantakrypto.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.quantakrypto.com%2Fmcp&type=streamable_http&id=quantakrypto-pqc-tools&name=quantakrypto%20pqc-tools
It answered our last check on 23 October 2026 in 207 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
11, as returned by the server's own tools/list on 20 September 2026: apply_triage, apply_verified_patch, check_dependency, explain_finding, get_fix_examples, list_rules, remediate_findings, score_delta, and 3 more.
It answered our last check on 23 October 2026 in 207 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.quantakrypto.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.quantakrypto. Endpoint host: mcp.quantakrypto.com. ARD identifier: urn:air:io.github.quantakrypto:mcp:pqc-tools.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.