quantakrypto pqc-tools
REMOTE · MCP.QUANTAKRYPTO.COM · 2 COMPONENTS · SCANNED SEP 20
Scan code for quantum-vulnerable cryptography and get NIST post-quantum migration guidance.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1293 tokens (~99/item across 13 items; 11 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the quantakrypto pqc-tools MCP server?
quantakrypto pqc-tools is a hosted endpoint at https://mcp.quantakrypto.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.quantakrypto.com
claude mcp add --transport http quantakrypto-pqc-tools '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"
}
}
} [mcp_servers.quantakrypto-pqc-tools] url = "https://mcp.quantakrypto.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"quantakrypto-pqc-tools": {
"type": "remote",
"url": "https://mcp.quantakrypto.com/mcp",
"enabled": true
}
}
} openclaw mcp add quantakrypto-pqc-tools --url 'https://mcp.quantakrypto.com/mcp' --transport streamable-http
mcp_servers:
quantakrypto-pqc-tools:
url: "https://mcp.quantakrypto.com/mcp" {
"McpServers": {
"quantakrypto-pqc-tools": {
"Transport": "http",
"Url": "https://mcp.quantakrypto.com/mcp"
}
}
} assistant mcp add quantakrypto-pqc-tools -t streamable-http -u 'https://mcp.quantakrypto.com/mcp'
{
"mcpServers": {
"quantakrypto-pqc-tools": {
"type": "http",
"url": "https://mcp.quantakrypto.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.quantakrypto.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quantakrypto.com | CN=WE1,O=Google Trust Services,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9bb7b9ce32012ef70e809b92380150b6 |
| SANs: quantakrypto.com, *.quantakrypto.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.quantakrypto.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| quantakrypto.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.quantakrypto.com/api/auth/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.quantakrypto.com/api/auth/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.quantakrypto.com/api/auth/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.quantakrypto.com/mcp |
| Authorisation server | https://mcp.quantakrypto.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.quantakrypto.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.quantakrypto.com/mcp | HTTPS enforced | 301 | https://mcp.quantakrypto.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_triage ~94
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | The findings that were triaged. |
| verdicts | array | yes | One verdict per finding, keyed by fingerprint. |
No output schema declared.
No examples provided.
apply_verified_patch ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| finding | object | yes | The scan finding being fixed (needs a string ruleId and location.file). |
| newContent | string | yes | Your proposed full corrected file content. |
| originalContent | string | yes | The file's current full content. |
No output schema declared.
No examples provided.
check_dependency ~82
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).
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem. Default: npm. |
| name | string | yes | Package name to look up (e.g. 'node-forge', 'jsonwebtoken'). |
No output schema declared.
No examples provided.
explain_finding ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | The classical algorithm family involved (e.g. RSA, ECDH, ECDSA). |
| ruleId | string | – | The finding's rule id, matching a detector id prefix. |
No output schema declared.
No examples provided.
get_fix_examples ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Classical algorithm family to migrate away from. |
| ruleId | string | – | A finding's ruleId (resolved to its algorithm). |
No output schema declared.
No examples provided.
list_rules ~25
List the quantakrypto detector catalog: every detector id and what it looks for.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remediate_findings ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | Findings from a scan's JSON output. |
No output schema declared.
No examples provided.
score_delta ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | array | yes | Findings after the change. |
| before | array | yes | Findings before the change (from a scan's JSON findings). |
No output schema declared.
No examples provided.
suggest_hybrid ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Classical algorithm family to migrate away from. |
| context | string | – | Free-text description of the cryptographic usage (used when no algorithm is given). |
| tier | string | – | Security tier: 'category-3' (default, commercial — ML-KEM-768 / ML-DSA-65) or 'category-5' (CNSA 2.0 / NSS, long-lived secrets — ML-KEM-1024 / ML-DSA-87). |
No output schema declared.
No examples provided.
triage_findings ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | Findings from a scan's JSON output. |
No output schema declared.
No examples provided.
verify_fix ~123
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The source code to check. |
| filename | string | – | Optional filename; its extension selects the detectors (overrides 'language'). |
| language | string | – | Language of the code (js, ts, python, go, java, csharp, rust, ruby, c, …). |
No output schema declared.
No examples provided.
What is the quantakrypto pqc-tools MCP server?
quantakrypto pqc-tools is an MCP server listed in the public MCP registry as io.github.quantakrypto/pqc-tools. Scan code for quantum-vulnerable cryptography and get NIST post-quantum migration guidance. This page covers its hosted endpoint (https://mcp.quantakrypto.com/mcp).
Is the quantakrypto pqc-tools MCP server safe to use?
quantakrypto pqc-tools scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the quantakrypto pqc-tools MCP server expose?
quantakrypto pqc-tools exposes 11 tools: apply_triage, apply_verified_patch, check_dependency, explain_finding, get_fix_examples, and 6 more. Their descriptions and schemas cost roughly 1,180 tokens of context every time the server is loaded.
Does the quantakrypto pqc-tools MCP server require authentication?
Yes. quantakrypto pqc-tools asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the quantakrypto pqc-tools MCP server still maintained?
quantakrypto pqc-tools is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.