原型 · 预览版：收录官方注册中心里的全部服务器，每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚
新手模式 关
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 菜单设置
新手模式 关
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch

quantakrypto pqc-tools

作者：quantakrypto版本 0.5.2i★ –i电脑或云端
注册名称io.github.quantakrypto/pqc-tools

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

你需要

  • 在云端运行无需安装任何东西，通过互联网连接
  • npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址，然后点击 Add
  4. 如果要求登录，请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://mcp.quantakrypto.com/mcp

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

或者在你的电脑上运行

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "pqc-tools": {
      "url": "https://mcp.quantakrypto.com/mcp"
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "pqc-tools": {
      "type": "http",
      "url": "https://mcp.quantakrypto.com/mcp"
    }
  }
}

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
  3. 粘贴下面的地址，起个名字，然后保存
  4. 如果要求登录，请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://mcp.quantakrypto.com/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 quantakrypto 验证，该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查；我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查；我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32461 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32461 个服务器的 19% 更新
  • 基础检查结果等于或优于此分类中其他 32461 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

quantakrypto pqc-tools 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.5.2）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, dotnet-mcp

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

dotnet-mcp

作者：Skymly

MCP server for .NET symbols, XAML, source generators, and restricted workspace edit

在你的电脑上运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

quantakrypto-tools

Open-source post-quantum readiness tooling by quantakrypto. Find quantum-vulnerable cryptography in any codebase, wire post-quantum readiness into your editor and your CI, and conformance-test post-quantum implementations — with zero runtime dependencies (Node built-ins only).

Design goals: simple, clean, reusable code; zero runtime dependencies;

everything documented, tested, and example-driven.

What's inside

ToolWhat it doesGet it
[qScan](packages/qscan) (@quantakrypto/qscan)CLI that finds quantum-vulnerable crypto (RSA, (EC)DH, ECDSA, EdDSA, …) across 14 languages (JS/TS, Python, Go, Java/Kotlin/Scala, C#, Rust, Ruby, PHP, Elixir, C/C++, Swift, Objective-C, Dart, Solidity/Move/Cairo) and prints a readiness score. SARIF / JSON / CBOM / evidence (ISO 27001 A.8.24) / OpenVEX output, baselines, incremental & parallel scans. Compliance mandate gate: --mandate cnsa-2.0 / nist-ir-8547 reports each prohibited finding with its dated clause and fails the build on the mandate's deadlines (--lead-months, --fail-now). Opt-in --triage (BYOK LLM re-rank/explain) and a qremediate codemod CLI.npx @quantakrypto/qscan ./
[MCP](packages/mcp) (@quantakrypto/mcp)Model Context Protocol server that gives AI coding agents post-quantum readiness tools (16 tools — scan, inventory, explain, suggest-hybrid, CBOM, plan-migration, triage, remediate, probe-endpoint, …). Local stdio + hostable HTTP.claude mcp add quantakrypto npx @quantakrypto/mcp
[Sieve](packages/sieve) (@quantakrypto/sieve)Conformance battery for ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) implementations, driven over a JSON stdin/stdout protocol.npx @quantakrypto/sieve --help
[Action](packages/action) (@quantakrypto/action)GitHub Action that runs the qScan/Sieve/qProbe checks in CI, writes SARIF for code-scanning upload, annotates the diff, and fails the build only on new quantum-vulnerable crypto.uses: quantakrypto/pqc-tools/packages/action@v1
[agent](packages/agent) (@quantakrypto/agent)Optional, zero-dependency BYOK (bring-your-own-key) LLM client (native fetch; Anthropic + OpenAI-compatible adapters) that powers qScan --triage and qremediate --llm. Networked, key-holding — kept isolated (see also qProbe).npm i @quantakrypto/agent
[qProbe](packages/qprobe) (@quantakrypto/qprobe)Actively probes live TLS/SSH endpoints you own for post-quantum readiness — PQC-hybrid key exchange (X25519MLKEM768) and classical certificate posture. Gated behind an ownership attestation; reports, never modifies ("engine disposes"). See THREAT-MODEL.npx @quantakrypto/qprobe --i-own-this host

All of qScan, MCP, the Action, agent, and qProbe share the engine in [`@quantakrypto/core`](packages/core) (npm i @quantakrypto/core) — detectors, the vulnerable-dependency DB, the readiness score, SARIF/JSON/CBOM/evidence/OpenVEX reporting, and the offline agent-plane primitives (context redactor, verify_fix gate, codemods, patch policy). Sieve is standalone: it tests *other* implementations and implements no crypto itself.

Infrastructure coverage. Beyond application source, the shared core engine carries config-scope detectors for Terraform/OpenTofu IaC and cloud KMS, JSON Web Keys, Kubernetes / cert-manager / Istio, CI/CD artifact & code signing (cosign/GPG/jarsigner/codesign/minisign), secrets at rest (SOPS/age, PGP, Sealed Secrets), message brokers (Kafka/MQTT), databases (pgcrypto, libpq sslmode), and JOSE/JWE key management — so qscan, the Action, and MCP flag infrastructure crypto with no extra install. qProbe adds the live-endpoint dimension (see the table above). The narrative anchor for infrastructure is *harvest now, decrypt later*: data and secrets captured today are decryptable once a CRQC exists.

Quick start

# 1. Scan a codebase for quantum-vulnerable cryptography.

npx @quantakrypto/qscan ./

2. Give your AI coding agent post-quantum readiness tools.

claude mcp add quantakrypto npx @quantakrypto/mcp

3. Conformance-test a post-quantum implementation (adapter speaks the JSON protocol).

npx @quantakrypto/sieve --impl "node ./my-impl.js" --param ml-kem-768

4. Gate against a compliance mandate's dated deadlines (CNSA 2.0 / NIST IR 8547).

Verdicts also ride in --format json/sarif/evidence; --policy lets an org

acknowledge families it is knowingly migrating (exempt from early gating).

npx @quantakrypto/qscan ./ --mandate cnsa-2.0 [--policy .quantakrypto/crypto-policy.json]

Add the CI gate by dropping packages/action/examples/quantum-readiness.yml into .github/workflows/, or wire it up directly:

- uses: quantakrypto/pqc-tools/packages/action@v1

with: path: "." severity-threshold: "high"

Each package README has the full options reference and more examples: qScan · MCP · Sieve · Action · core · agent.

Using quantakrypto alongside a PQC library (liboqs / OQS)

quantakrypto does not implement post-quantum cryptography, by design — it is the scanner, the CI gate, and the conformance harness you wrap around a real PQC library like liboqs / Open Quantum Safe. They compose: quantakrypto finds and gates classical crypto (qscan, the Action), tells you what to migrate to and in what order (qscan --tier, MCP plan_migration, qremediate), and conformance-tests the replacement (sieve runs any ML-KEM/ML-DSA/SLH-DSA implementation against FIPS 203/204/205, with exact-value KATs when you supply official NIST ACVP vectors). liboqs supplies the primitives.

See the worked end-to-end walkthrough — scan → migrate → verify → gate — in [`examples/liboqs-migration/`](examples/liboqs-migration/README.md).

Workspace layout

quantakrypto-tools/

├── packages/ │ ├── core/ @quantakrypto/core — shared engine (the contract lives in src/types.ts + src/index.ts) │ ├── qscan/ @quantakrypto/qscan — CLI │ ├── mcp/ @quantakrypto/mcp — MCP server (stdio now, HTTP scaffold for hosting) │ ├── action/ @quantakrypto/action — GitHub Action │ ├── sieve/ @quantakrypto/sieve — conformance battery + JSON protocol │ ├── agent/ @quantakrypto/agent — opt-in BYOK LLM client (triage + remediation) │ └── qprobe/ @quantakrypto/qprobe — active TLS/SSH endpoint probing (gated; the only prober) ├── docs/ architecture, hosted-MCP design, improvement roadmap └── examples/ end-to-end examples

Development

Requires Node ≥ 20.

npm install        # links the workspaces

npm run build # tsc --build (project references) npm test # node:test across all packages

The toolchain is intentionally tiny: TypeScript + tsx (to run node:test on .ts) are the only dev dependencies; there are no runtime dependencies.

Documentation & compliance

Full documentation lives in [`docs/`](docs/README.md):

  • [Objectives & scope](docs/OBJECTIVES.md) — what the toolchain is for, what each library does, the load-bearing decisions, and the deliberate scope boundaries. Start here.
  • [Architecture decisions](docs/adr/README.md) — the immutable "why" behind each load-bearing choice (zero deps, shared core contract, two-plane agent, …).
  • [Standards & compliance](docs/COMPLIANCE.md) — what the tools touch and could align to: NIST FIPS 203/204/205, SP 800-208, CNSA 2.0, SARIF, CWE, ISO/IEC 27001 (A.8.24), Common Criteria, FIPS 140-3, EU DORA/NIS2, US M-23-02 / NSM-10, and OSS assurance (SLSA, OpenSSF Scorecard, SPDX/REUSE).
  • Governance: Contributing · Security · Code of Conduct · Changelog.

License

Apache-2.0. The methodology is open; the assessments, attestation reports, and deliverables are where the quantakrypto practice lives.

Support & training

Questions, commercial support, or post-quantum readiness training for your team — visit [quantakrypto.com](https://quantakrypto.com) or email [hello@quantakrypto.com](mailto:hello@quantakrypto.com).

问 PopNx