Skip to content

quantakrypto pqc-tools MCP server

io.github.quantakrypto/pqc-toolsquantakryptostreamable-httpv0.5.2Scanned

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

11 tools: 8 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 8 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the quantakrypto pqc-tools MCP server can do

The quantakrypto pqc-tools MCP server is published by the GitHub account quantakrypto. It has 11 tools. It can create or change data (8 tools: apply_triage, apply_verified_patch, check_dependency, remediate_findings and 4 more), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (get_fix_examples).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.5.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Changes things 8Claude Code: ask
  • apply_triageDeterministically attach your triage verdicts to their findings and re-sort by exposure (highest first).No findings

    Why it is in this group

    • The name "apply_triage" says "apply": a word for a change.
    Description, as the server wrote it
    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_patchDeterministically VERIFY a proposed fix before writing it — runs the same patch-policy + verify_fix + blast-radius gates as `qremediate` (offline, no key, no network).No findings

    Why it is in this group

    • The name "apply_verified_patch" says "apply": a word for a change.
    Description, as the server wrote it
    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_dependencyCheck whether a package is in quantakrypto's known quantum-vulnerable dependency database (the classical crypto it exposes).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).
  • remediate_findingsProduce a deterministic remediation REQUEST bundle (rubric + fix schema + per-finding metadata + fingerprints) for YOU (the host agent) to fix.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_deltaCompute the readiness-score and HNDL change between two finding sets (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_hybridRecommend a post-quantum / hybrid migration.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_findingsProduce a deterministic triage REQUEST bundle (rubric + verdict schema + per-finding metadata) for YOU (the host agent) to reason over.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_fixRun the quantakrypto detectors over a code snippet (NOT the filesystem) and report any classical crypto that remains.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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'.
Only reads 3Show 3 read-only tools
  • explain_findingExplain a quantakrypto finding and its post-quantum remediation.No findings

    Why it is in this group

    • The name "explain_finding" says "explain": a word for reading.
    Description, as the server wrote it
    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_examplesReturn before/after code examples for migrating a classical algorithm to a post-quantum / hybrid replacement.Reads text others writeNo findings

    Why it is in this group

    • The name "get_fix_examples" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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_rulesList the quantakrypto detector catalog: every detector id and what it looks for.No findings

    Why it is in this group

    • The name "list_rules" says "list": a word for reading.
    Description, as the server wrote it
    List the quantakrypto detector catalog: every detector id and what it looks for.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:10 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.quantakrypto.com/.well-known/oauth-protected-resource
Authorization servers
https://mcp.quantakrypto.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.quantakrypto.com/mcp: tools/list returned 11 tools to an anonymous client, including apply_triage (write), apply_verified_patch (write), check_dependency (write), remediate_findings (write), score_delta (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.5.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http pqc-tools https://mcp.quantakrypto.com/mcp
claude mcp add --transport http pqc-tools https://mcp.quantakrypto.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pqc-tools__explain_finding",
      "mcp__pqc-tools__get_fix_examples",
      "mcp__pqc-tools__list_rules"
    ],
    "ask": [
      "mcp__pqc-tools__apply_triage",
      "mcp__pqc-tools__apply_verified_patch",
      "mcp__pqc-tools__check_dependency",
      "mcp__pqc-tools__remediate_findings",
      "mcp__pqc-tools__score_delta",
      "mcp__pqc-tools__suggest_hybrid",
      "mcp__pqc-tools__triage_findings",
      "mcp__pqc-tools__verify_fix"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pqc-tools. Review it before you use it.

Capability tags behind 1 rule
  • mcp__pqc-tools__get_fix_examples untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.quantakrypto/pqc-tools/verify?hash=929f8cdf4684bfe32c82fb463962eff4bc5b0f9bf7b39f0104cab906757ce00c" | jq -e '.changed == false'

Pinned hash 929f8cdf4684, from Nov 20, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.quantakrypto/pqc-tools/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.quantakrypto/pqc-tools
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.quantakrypto/pqc-tools.svg)](https://radar.anlyon.com/servers/io.github.quantakrypto/pqc-tools)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:45 UTC.

quantakrypto pqc-tools MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the quantakrypto pqc-tools MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the quantakrypto pqc-tools MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the quantakrypto pqc-tools MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the quantakrypto pqc-tools MCP server have?

11 tools: 8 write, 3 read. apply_triage, apply_verified_patch, check_dependency, remediate_findings, score_delta, suggest_hybrid, triage_findings, verify_fix and 3 more.

Does the quantakrypto pqc-tools MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the quantakrypto pqc-tools MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the quantakrypto pqc-tools MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.