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

quantakrypto

https://mcp.quantakrypto.com

Registry code: 9b3e5329524c266b

api record

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 · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is quantakrypto live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is quantakrypto free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does quantakrypto have?
11 tools: explain_finding, remediate_findings, score_delta, check_dependency, list_rules, suggest_hybrid, triage_findings, apply_verified_patch, ….
Is quantakrypto safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.6%· all time 99.6%

latency
175ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 489 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
security & compliance threat & vulnerability
used for
  • scan code for quantum-vulnerable crypto
  • recommend post-quantum migrations
  • check a dependency for classical crypto
  • verify a crypto fix in code
takes → gives
code → data
tools
10 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

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

  • explain_finding reads 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
  • remediate_findings reads 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 reads 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
  • check_dependency reads auth-required 1h ago

    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
  • list_rules reads auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • suggest_hybrid reads 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 reads 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
  • apply_verified_patch changes data 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
  • apply_triage reads 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
  • verify_fix reads 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
  • get_fix_examples reads auth-required 1h 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
_ 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9b3e5329524c266b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9b3e5329524c266b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

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

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ 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
0

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.

_ also on quantakrypto.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.