quantakrypto pqc-tools MCP server

• apply_triageFree

  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_patchwrite actionFree

  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_dependencyFree

  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_findingFree

  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_examplesFree

  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_rulesFree

  List the quantakrypto detector catalog: every detector id and what it looks for.

• remediate_findingsFree

  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_deltaFree

  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_hybridFree

  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_findingsFree

  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_fixwrite actionFree

  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'.

• Code scan19 source files scanned25/25
• Live reliabilityremote reachable in 2155ms17/20
• Tool poisoning11 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
• Maintenancelast push 23 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 63% of 917 Security servers

Tools

11

the typical Security server has 10

Tools that change things

18%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Security server answers 100%

Response time

562 ms

faster than 19% of 551 Security servers

GitHub stars

15

more than 91% of 589 Security servers

Downloads a week

24

more than 5% of 386 Security servers with a package

quantakrypto pqc-tools: common questions

Is quantakrypto pqc-tools MCP server safe?

Mostly: it is graded B (82/100). Read the quantakrypto pqc-tools safety report

How do I install quantakrypto pqc-tools?

It runs remotely at mcp.quantakrypto.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does quantakrypto pqc-tools need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is quantakrypto pqc-tools maintained?

The last commit was 32 days ago (2026-10-14). The latest release is v0.5.2.

Is quantakrypto pqc-tools up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of quantakrypto pqc-tools?

Servers from other publishers that do the same job: Notebooklm Secure MCP server, PyMemoryEditor MCP server and Autopilot Jobhunt MCP server.

How does quantakrypto pqc-tools compare with other Security MCP servers?

safety score 82/100 (higher than 63% of 917 Security servers); tools 11 (the typical Security server has 10); tools that change things 18% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.