pqc-migration-mcp
This server gives AI agents post-quantum migration arithmetic and taxonomy facts — sizes, fragments, reassembly safety, failure families, and benchmark scoring — without exposing repair mechanisms.
credential_size – compute total on-wire bytes and per-component breakdown for a KEM+sig credential (e.g., ML-KEM-768 + ML-DSA-65).
fragments – calculate how many frames an object splits into on a transport and whether fragmentation is mandatory.
reassembly_window – determine if a safe capacity cap exists (feasible and safe) given object size, memory budget, and concurrency; if none, get the max safe concurrency.
list_failure_families – retrieve all 39 post-quantum migration failure families with case counts and published analogues.
describe_family – get details on a specific failure family: invariants broken, which unrepaired designs fail it, and what they did (no repair info).
score_submission – score a PQC-MFB submission (map of case_id to bool) to get coverage, regressions, and zero-coverage families.
All tools are exposed via MCP (JSON-RPC 2.0 over stdio) and return domain errors as tool results so agents can self-correct. Detection only — no repair mechanisms are provided.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pqc-migration-mcp credential size for ML-KEM-768 and ML-DSA-44"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pqc-migration-mcp
Give your AI agent the post-quantum migration facts it keeps guessing at.
Six tools over MCP: credential sizes, fragment counts, the reassembly window, the 39-family failure taxonomy, and benchmark scoring. Ask Claude "will our ML-KEM-768 handshake fit in a BLE MTU?" and it computes the answer instead of estimating one.
📖 Full documentation, tutorial and conceptual guide: https://nickharris808.github.io/pqc-toolkit/
Why this exists
Agents are increasingly doing PQC migration work, and they are confidently wrong about exactly the things that matter: how big a credential actually is, how many fragments it becomes, and whether a safe reassembly cap exists at your concurrency. Those are arithmetic, not judgement — so hand the agent the arithmetic.
The protocol layer here is dependency-free. MCP is JSON-RPC 2.0 over line-delimited stdio, which is small enough to implement directly and keeps the install trivial.
Related MCP server: attestix
Install
pip install git+https://github.com/nickharris808/pqc-migration-mcpThis pulls pqc-sizes and pqc-mfb from their repositories too. Not on PyPI
yet, so pip install pqc-migration-mcp does not work today.
30-second quickstart
# talk to it directly -- it is line-delimited JSON-RPC on stdio
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | pqc-migration-mcpClaude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"pqc-migration": {
"command": "pqc-migration-mcp"
}
}
}Restart Claude Desktop. The six tools appear under the connector.
Tools
Tool | Answers |
| How many bytes is a KEM+signature credential, component by component? |
| How many fragments on this transport — and is fragmentation now mandatory? |
| Does a safe capacity cap exist at all? If not, what concurrency would work? |
| All 39 failure families, with case counts and published analogues |
| What breaks in this family, in which designs, and what did each do? |
| Score a PQC-MFB submission: coverage, regressions, zero-coverage families |
Worked example — actual output
The transport is line-delimited JSON — one complete object per line. Keep the
request on a single line; a request wrapped across two lines arrives as two
incomplete ones and comes back as two -32700 parse errors.
$ echo '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"reassembly_window","arguments":{"largest_legitimate_object":12000,"memory_budget":32768,"concurrency":3}}}' | pqc-migration-mcpThe server replies with one JSON object per line. Pretty-printed, the content
payload of that reply is:
{
"budget": 32768,
"ceiling": 10922,
"concurrency": 3,
"explanation": "EMPTY WINDOW: floor 12,000 B > ceiling 10,922 B (short by 1,078 B). No capacity cap is both feasible and safe. Raise the budget to at least 36,000 B, reduce concurrency to at most 2, or choose a smaller credential.",
"floor": 12000,
"is_empty": true,
"max_safe_concurrency": 2,
"recommended_cap": null
}The agent gets a verdict and the number that would fix it, so it can propose a concrete change rather than reporting a problem.
What this server will not tell you
It exposes detection. It does not expose repairs.
An agent can learn that a design fails krack_retransmission and exactly what the
unrepaired design did. It cannot obtain the mechanism that closes it. That boundary is
deliberate: an MCP tool returning repairs would let any user enumerate the entire closed
set in an afternoon.
There is a test that calls describe_family for all 39 families plus every other
tool, concatenates the responses, and fails if repair_mechanism, repaired_detail or
repaired_held appears anywhere in the output.
Error semantics
Domain errors — an unknown algorithm, an unknown family — come back as a tool result
with isError: true and a message naming the valid options, so the agent can correct
itself. Only protocol faults become JSON-RPC errors (-32601 unknown method/tool,
-32602 bad arguments, -32700 unparseable line).
A malformed line does not kill the loop; the server replies with a parse error and keeps serving.
Tests
pip install -e ".[dev]" && pytest # 57 passedTests cover the protocol, every tool, the moat boundary, and the real stdio transport driven as a subprocess — including a check that stderr stays empty, since MCP clients read stdout as protocol and stray warnings confuse them.
Scope
Arithmetic, taxonomy lookup and scoring. No cryptography, no network, no telemetry. It does not inspect your implementation. A clean answer means your configuration is sound, not that your code enforces it.
Related
pqc-sizes · pqc-mfb ·
pqc-guard-action · pqc-dos-embedded
Closing the 39 families is what the closed core does. Relevant subject matter is covered by a filed provisional patent application. For commercial use of the full envelope, open a GitHub Discussion or an issue on this repository.
Honest scope
What this proves. That the arithmetic and taxonomy an agent is reasoning with are correct: real credential sizes, real fragment counts, a real window verdict, and the real failure taxonomy.
What it does NOT prove.
Not that the agent used the answer. This supplies facts; it does not supervise what is done with them.
Not an inspection of your code. No tool here reads your implementation.
Not a repair channel. Every tool exposes detection only. A test calls
describe_familyfor all 39 families plus every other tool and fails if a repair field appears anywhere in the output.
Errors. Domain problems come back as tool results with isError: true and a
message naming valid options, so an agent can self-correct. Only protocol faults
become JSON-RPC errors.
The PQC migration toolkit
Eleven free tools for teams moving authenticated key exchange to post-quantum. They find and measure; they do not repair.
Tool | What it does | Where |
Sizes, fragment counts, and the two-sided reassembly window | source | |
The same arithmetic for Node and the browser | source | |
Fail the build when the window is empty | GitHub Action | |
169 lines of C: the failure on a real 64 KB device | source | |
Re-verify the bound on-device, no SMT solver | source | |
The same bound in Lean 4 — 0 | source | |
The gate in synthesizable RTL, 5 Yosys proofs | source | |
pqc-migration-mcp ← you are here | Six MCP tools for AI agents | source |
322 cases · 39 failure families · scorer | source | |
The benchmark as a dataset | HF | |
122 named formal results, 6 provers | HF | |
Try it in your browser, no install | HF Space |
New here? The end-to-end tutorial walks one realistic migration through all of them in about ten minutes: sizes -> window -> CI gate -> benchmark.
In a hurry? pqc-sizes tells you in five seconds whether your credential fragments and whether a safe cap exists. pqc-explorer does the same in a browser, with no install.
The closed core
Closing the 39 failure families — downgrade binding, retransmission-safe installation, fragmentation transcripts, roaming forward secrecy, multi-link key separation, admission control, group-key binding — is a separate proprietary codebase. Relevant subject matter is covered by a filed provisional patent application.
That split is measured, not asserted: under a replicate noise control only 4 of 32 repair mechanisms are externally distinguishable, so publishing these detectors does not disclose the repairs.
For commercial licensing, open a GitHub Discussion or an issue on any of these repos.
License
Apache-2.0. See LICENSE and CONTRIBUTING.md.
Available Tools
6 toolscredential_sizeC
Total on-wire bytes for a KEM + signature credential, with a per-component breakdown.
Inputs: kem, sig.
describe_familyA
Detail for one failure family: the invariants it breaks, the unrepaired designs that fail it, and what each did. Does not return repairs.
Inputs: family (required).
fragmentsB
How many fragments an object becomes on a transport, and whether fragmentation is therefore mandatory.
Inputs: object_bytes (required), frame_payload (required).
list_failure_familiesA
All 39 post-quantum migration failure families, with case counts and published prior-art analogues.
Inputs: no named parameters.
reassembly_windowC
The two-sided reassembly-capacity window. Returns is_empty=true when NO capacity cap is both feasible and safe, plus the maximum concurrency that would be safe.
Inputs: concurrency (required), memory_budget (required), largest_legitimate_object (required).
score_submissionB
Score a PQC-MFB submission ({case_id: bool}). Returns coverage, regressions, and which families have zero coverage.
Inputs: submission (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of PQC migration analysis: failure families, reassembly capacity, submission scoring, credential size, family details, and fragmentation. No overlaps in functionality.
Most tools follow a verb_noun pattern with underscores (list_failure_families, score_submission, describe_family). 'credential_size' and 'reassembly_window' are noun-like but still clear; 'fragments' is a single noun, slightly deviating.
The set includes 6 tools, which is well within the ideal 3-15 range. Each tool addresses a specific need without redundancy, making the scope manageable and focused.
The tools cover querying failure families and scoring submissions, but lack submission management, repair retrieval (noted in describe_family), and listing submissions. Some gaps exist for a full workflow.
Maintenance
Related MCP Connectors
Production-grade cryptography toolkit with 31 MCP tools for classical, PQC, and KMS workflows.
QuantumOracle — 18 post-quantum crypto tools: Kyber, Dilithium, hybrid schemes, migration.
Five AI-agent MCP tools: Repair, Verify, Witness, Monitor, Recovery. Free beta; no billing.
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to perform quantum-resistant cryptographic operations using NIST-standardized algorithms including ML-KEM, ML-DSA, and SPHINCS+. Supports key generation, encryption, digital signatures, and security analysis for post-quantum cryptography research and development.251MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for compliance automation of AI agents, enabling EU AI Act compliance, verifiable credentials, and decentralized identity management with 47 tools across 9 modules.37 PyPI668Apache 2.0
- AlicenseBqualityDmaintenanceDefense-grade cryptographic compliance and analysis tools for MCP, including FIPS 140-3 validation, CNSA 2.0 analysis, post-quantum readiness assessment, and classical cipher utilities.182MIT
- AlicenseAqualityCmaintenancePost-quantum readiness for AI coding agents: scans code for quantum-vulnerable cryptography (RSA/ECDH/ECDSA/DH) and returns NIST ML-KEM/ML-DSA/SLH-DSA (and hybrid) migration guidance, with fix verification and dependency checks. Content-based, advisory tools only; runs local (npx @quantakrypto/mcp) or as a hosted OAuth endpoint.1616Apache 2.0