# quantakrypto pqc-tools (remote · mcp.quantakrypto.com)

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

- Trust score: 79/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.quantakrypto.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/quantakrypto-pqc-tools/mcp.md), [page](https://verifymcp.io/servers/quantakrypto-pqc-tools/mcp)
- npm · `@quantakrypto/mcp`: 79/100, [markdown](https://verifymcp.io/servers/quantakrypto-pqc-tools/quantakrypto-mcp.md), [page](https://verifymcp.io/servers/quantakrypto-pqc-tools/quantakrypto-mcp)

## Channel facts

- Endpoint: `https://mcp.quantakrypto.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1293 tokens (~99/item across 13 items; 11 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.quantakrypto-pqc-tools]
url = "https://mcp.quantakrypto.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "quantakrypto-pqc-tools": {
      "type": "remote",
      "url": "https://mcp.quantakrypto.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add quantakrypto-pqc-tools --url https://mcp.quantakrypto.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  quantakrypto-pqc-tools:
    url: "https://mcp.quantakrypto.com/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 78, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 73, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 73)

First indexed and scored.

## MCP tools (11)

### `apply_triage` (~94 tokens)

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

Input parameters:

- `findings` (array, required): The findings that were triaged.
- `verdicts` (array, required): One verdict per finding, keyed by fingerprint.

### `apply_verified_patch` (~168 tokens)

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.

Input parameters:

- `finding` (object, required): The scan finding being fixed (needs a string ruleId and location.file).
- `newContent` (string, required): Your proposed full corrected file content.
- `originalContent` (string, required): The file's current full content.

### `check_dependency` (~82 tokens)

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

Input parameters:

- `ecosystem` (string): Package ecosystem. Default: npm.
- `name` (string, required): Package name to look up (e.g. 'node-forge', 'jsonwebtoken').

### `explain_finding` (~135 tokens)

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.

Input parameters:

- `algorithm` (string): The classical algorithm family involved (e.g. RSA, ECDH, ECDSA).
- `ruleId` (string): The finding's rule id, matching a detector id prefix.

### `get_fix_examples` (~90 tokens)

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.

Input parameters:

- `algorithm` (string): Classical algorithm family to migrate away from.
- `ruleId` (string): A finding's ruleId (resolved to its algorithm).

### `list_rules` (~25 tokens)

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

### `remediate_findings` (~112 tokens)

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.

Input parameters:

- `findings` (array, required): Findings from a scan's JSON output.

### `score_delta` (~79 tokens)

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.

Input parameters:

- `after` (array, required): Findings after the change.
- `before` (array, required): Findings before the change (from a scan's JSON findings).

### `suggest_hybrid` (~172 tokens)

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.

Input parameters:

- `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).

### `triage_findings` (~100 tokens)

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.

Input parameters:

- `findings` (array, required): Findings from a scan's JSON output.

### `verify_fix` (~123 tokens)

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

Input parameters:

- `code` (string, required): 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, …).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/quantakrypto-pqc-tools/mcp#diagnostics

## Score history

- 2026-08-03: 79
- 2026-08-02: 78
- 2026-08-01: 78
- 2026-07-31: 78
- 2026-07-30: 73
- 2026-07-29: 75
- 2026-07-28: 75
- 2026-07-27: 74
- 2026-07-26: 73

## Links

- Remote endpoint: https://mcp.quantakrypto.com/mcp
- Repository: https://github.com/quantakrypto/pqc-tools
- Changelog RSS feed: https://verifymcp.io/servers/quantakrypto-pqc-tools/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/quantakrypto-pqc-tools/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/quantakrypto-pqc-tools/mcp