_ registry / mcp streamable-http · checked 8h ago

quantakrypto

https://mcp.quantakrypto.com

Registry code: 9b3e5329524c266b

quantakrypto checks code for quantum-vulnerable cryptography and recommends post-quantum (NIST PQC) migrations. Use scan_path / inventory_crypto to assess a path, list_rules to see detectors, and explain_finding / suggest_hybrid for remediation guidance.

endpoint: https://mcp.quantakrypto.com/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing
karma: 0 · newcomer

reachable

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

103ms

last good check

priced tools

of 11 tools

_ answered our checks, 90 days 1 checks · signed record

2026-09-27 00:26 unknown → live

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts

distinct, expensive to fake

calls served

successful, last 30 days

_ what it can do 11 tools

11 auth-required 11 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

list_rules auth-required 8h ago
List the quantakrypto detector catalog: every detector id and what it looks for.

mcp-tool
{ "type": "object", "properties": {}, "additionalProperties": false }
arguments 5 lines
explain_finding auth-required never probed
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.

mcp-tool
{ "type": "object", "properties": { "ruleId": { "type": "string", "description": "The finding's rule id, matching a detector id prefix." }, "algorithm": { "type": "string", "description": "The classical algorithm family involved (e.g. RSA, ECDH, ECDSA)." } }, "additionalProperties": false }
arguments 14 lines

get_fix_examples auth-required 8h ago

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.

mcp-tool

{
  "type": "object",
  "properties": {
    "ruleId": {
      "type": "string",
      "description": "A finding's ruleId (resolved to its algorithm)."
    },
    "algorithm": {
      "type": "string",
      "description": "Classical algorithm family to migrate away from."
    }
  },
  "additionalProperties": false
}

arguments 14 lines

apply_triage auth-required never probed

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

mcp-tool

{
  "type": "object",
  "required": [
    "findings",
    "verdicts"
  ],
  "properties": {
    "findings": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "ruleId",
          "location"
        ],
        "properties": {
          "cwe": {
            "type": "string",
            "description": "e.g. \"CWE-327\"."
          },
          "hndl": {
            "type": "boolean",
            "description": "Exposed to harvest-now-decrypt-later."
          },
          "title": {
            "type": "string"
          },
          "ruleId": {
            "type": "string",
            "description": "Stable rule id, e.g. \"rsa-keygen\"."
          },
          "message": {
            "type": "string"
          },
          "category": {
            "type": "string"
          },
          "location": {
            "type": "object",
            "required": [
              "file"
            ],
            "properties": {
              "file": {
                "type": "string"
              },
              "line": {
                "type": "number"
              }
            },
            "description": "Where the finding is."
          },
          "severity": {
            "type": "string",
            "description": "critical | high | medium | low | info."
          },
          "algorithm": {
            "type": "string",
            "description": "Classical algorithm family, when applicable."
          },
          "confidence": {
            "type": "string"
          },
          "remediation": {
            "type": "string"
          }
        },
        "description": "A single finding from `scan_path --format json`."
      },
      "description": "The findings that were triaged."
    },
    "verdicts": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "fingerprint",
          "exposureScore",
          "priority",
          "rationale"
        ],
        "properties": {
          "priority": {
            "enum": [
              "now",
              "soon",
              "later"
            ],
            "type": "string"
          },
          "rationale": {
            "type": "string",
            "description": "Why this exposure score / priority."
          },
          "fingerprint": {
            "type": "string",
            "description": "Fingerprint of the finding this verdict applies to."
          },
          "exposureScore": {
            "type": "number",
            "description": "Real-world exposure (higher = more exposed)."
          }
        },
        "description": "A triage verdict for one finding."
      },
      "description": "One verdict per finding, keyed by fingerprint."
    }
  },
  "additionalProperties": false
}

arguments 110 lines

apply_verified_patch auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "finding", "originalContent", "newContent" ], "properties": { "finding": { "type": "object", "description": "The scan finding being fixed (needs a string ruleId and location.file)." }, "newContent": { "type": "string", "description": "Your proposed full corrected file content." }, "originalContent": { "type": "string", "description": "The file's current full content." } }, "additionalProperties": false }
arguments 23 lines

check_dependency auth-required never probed

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

mcp-tool

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Package name to look up (e.g. 'node-forge', 'jsonwebtoken')."
    },
    "ecosystem": {
      "type": "string",
      "description": "Package ecosystem. Default: npm."
    }
  },
  "additionalProperties": false
}

arguments 17 lines

remediate_findings auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "required": [
    "findings"
  ],
  "properties": {
    "findings": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "ruleId",
          "location"
        ],
        "properties": {
          "cwe": {
            "type": "string",
            "description": "e.g. \"CWE-327\"."
          },
          "hndl": {
            "type": "boolean",
            "description": "Exposed to harvest-now-decrypt-later."
          },
          "title": {
            "type": "string"
          },
          "ruleId": {
            "type": "string",
            "description": "Stable rule id, e.g. \"rsa-keygen\"."
          },
          "message": {
            "type": "string"
          },
          "category": {
            "type": "string"
          },
          "location": {
            "type": "object",
            "required": [
              "file"
            ],
            "properties": {
              "file": {
                "type": "string"
              },
              "line": {
                "type": "number"
              }
            },
            "description": "Where the finding is."
          },
          "severity": {
            "type": "string",
            "description": "critical | high | medium | low | info."
          },
          "algorithm": {
            "type": "string",
            "description": "Classical algorithm family, when applicable."
          },
          "confidence": {
            "type": "string"
          },
          "remediation": {
            "type": "string"
          }
        },
        "description": "A single finding from `scan_path --format json`."
      },
      "description": "Findings from a scan's JSON output."
    }
  },
  "additionalProperties": false
}

arguments 73 lines

score_delta auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "required": [
    "before",
    "after"
  ],
  "properties": {
    "after": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "ruleId",
          "location"
        ],
        "properties": {
          "cwe": {
            "type": "string",
            "description": "e.g. \"CWE-327\"."
          },
          "hndl": {
            "type": "boolean",
            "description": "Exposed to harvest-now-decrypt-later."
          },
          "title": {
            "type": "string"
          },
          "ruleId": {
            "type": "string",
            "description": "Stable rule id, e.g. \"rsa-keygen\"."
          },
          "message": {
            "type": "string"
          },
          "category": {
            "type": "string"
          },
          "location": {
            "type": "object",
            "required": [
              "file"
            ],
            "properties": {
              "file": {
                "type": "string"
              },
              "line": {
                "type": "number"
              }
            },
            "description": "Where the finding is."
          },
          "severity": {
            "type": "string",
            "description": "critical | high | medium | low | info."
          },
          "algorithm": {
            "type": "string",
            "description": "Classical algorithm family, when applicable."
          },
          "confidence": {
            "type": "string"
          },
          "remediation": {
            "type": "string"
          }
        },
        "description": "A single finding from `scan_path --format json`."
      },
      "description": "Findings after the change."
    },
    "before": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "ruleId",
          "location"
        ],
        "properties": {
          "cwe": {
            "type": "string",
            "description": "e.g. \"CWE-327\"."
          },
          "hndl": {
            "type": "boolean",
            "description": "Exposed to harvest-now-decrypt-later."
          },
          "title": {
            "type": "string"
          },
          "ruleId": {
            "type": "string",
            "description": "Stable rule id, e.g. \"rsa-keygen\"."
          },
          "message": {
            "type": "string"
          },
          "category": {
            "type": "string"
          },
          "location": {
            "type": "object",
            "required": [
              "file"
            ],
            "properties": {
              "file": {
                "type": "string"
              },
              "line": {
                "type": "number"
              }
            },
            "description": "Where the finding is."
          },
          "severity": {
            "type": "string",
            "description": "critical | high | medium | low | info."
          },
          "algorithm": {
            "type": "string",
            "description": "Classical algorithm family, when applicable."
          },
          "confidence": {
            "type": "string"
          },
          "remediation": {
            "type": "string"
          }
        },
        "description": "A single finding from `scan_path --format json`."
      },
      "description": "Findings before the change (from a scan's JSON findings)."
    }
  },
  "additionalProperties": false
}

arguments 138 lines

suggest_hybrid auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "properties": {
    "tier": {
      "enum": [
        "category-3",
        "category-5"
      ],
      "type": "string",
      "description": "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)."
    },
    "context": {
      "type": "string",
      "description": "Free-text description of the cryptographic usage (used when no algorithm is given)."
    },
    "algorithm": {
      "type": "string",
      "description": "Classical algorithm family to migrate away from."
    }
  },
  "additionalProperties": false
}

arguments 22 lines

triage_findings auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "required": [
    "findings"
  ],
  "properties": {
    "findings": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "ruleId",
          "location"
        ],
        "properties": {
          "cwe": {
            "type": "string",
            "description": "e.g. \"CWE-327\"."
          },
          "hndl": {
            "type": "boolean",
            "description": "Exposed to harvest-now-decrypt-later."
          },
          "title": {
            "type": "string"
          },
          "ruleId": {
            "type": "string",
            "description": "Stable rule id, e.g. \"rsa-keygen\"."
          },
          "message": {
            "type": "string"
          },
          "category": {
            "type": "string"
          },
          "location": {
            "type": "object",
            "required": [
              "file"
            ],
            "properties": {
              "file": {
                "type": "string"
              },
              "line": {
                "type": "number"
              }
            },
            "description": "Where the finding is."
          },
          "severity": {
            "type": "string",
            "description": "critical | high | medium | low | info."
          },
          "algorithm": {
            "type": "string",
            "description": "Classical algorithm family, when applicable."
          },
          "confidence": {
            "type": "string"
          },
          "remediation": {
            "type": "string"
          }
        },
        "description": "A single finding from `scan_path --format json`."
      },
      "description": "Findings from a scan's JSON output."
    }
  },
  "additionalProperties": false
}

arguments 73 lines

verify_fix auth-required never probed

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

mcp-tool

{
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The source code to check."
    },
    "filename": {
      "type": "string",
      "description": "Optional filename; its extension selects the detectors (overrides 'language')."
    },
    "language": {
      "type": "string",
      "description": "Language of the code (js, ts, python, go, java, csharp, rust, ruby, c, …)."
    }
  },
  "additionalProperties": false
}

arguments 21 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/9b3e5329524c266b/badge.svg)](https://brick.blue/agent/9b3e5329524c266b)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.