QuantumScan PQC Scanner MCP Server

by gaiabio12-design Your server? Claim it

answering

QuantumScan PQC Scanner is answering right now. Last checked 3 min ago. It exposes 4 tools.

PQC scanner for GitHub repos and smart contracts. Detects quantum-vulnerable ECDSA/RSA.

Uptime history 91 days of history · worst day 0%

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

124 ms

Response time

average over 24h

authentication required

Access

streamable-http

Nothing serious here today

Today is the operative word: we check QuantumScan PQC Scanner every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add quantumscan-pqc-scanner --transport http https://quantumscan.io/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://quantumscan.io/api/mcp

~/.codex/config.toml

[mcp_servers.quantumscan-pqc-scanner]
url = "https://quantumscan.io/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "quantumscan-pqc-scanner": {
      "url": "https://quantumscan.io/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "quantumscan-pqc-scanner": {
      "type": "http",
      "url": "https://quantumscan.io/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

scan

get_scan_result

Get the result of a previously submitted scan. Returns status (submitted | working | completed | failed) and, when completed, a full CBOM (Cryptographic Bill of Materials) compliant with EIP-7789 and CycloneDX CBOM 1.6, plus a quantum risk score (0 = fully safe, 100 = fully vulnerable). Rate-limited: 60 calls/min per IP or API key.

scan_contract

Scan a verified on-chain smart contract for quantum-vulnerable cryptography AND today's fraud patterns (rug pulls, honeypots, uncapped mints, reentrancy). Use this BEFORE signing a transaction, interacting with a DeFi protocol, or integrating a contract into an agent workflow. Synchronous — result is immediate (no polling needed). Requires the contract to be verified on Sourcify (https://sourcify.dev). Returns risk score 0-100, agent risk score, finding breakdown, and concrete PQC migration steps. Rate-limited: same as scan_repository (10/day per IP free, credit-based paid).

scan_repository

Submit a GitHub, GitLab, or Bitbucket repository for post-quantum cryptography (PQC) vulnerability scanning. Returns a scan_id. Call get_scan_result to poll for the result. Free tier: 10 scans/day per IP. Paid tier: credit-based (register at /api/agent/register).

pqc

check_pqc_risk

Instant check (no DB, no scan) — returns whether a list of algorithm names are quantum-vulnerable. Useful for quick risk assessment before calling scan_repository. Rate-limited: 100 calls/day per IP (free), 500/day per API key (paid).

Endpoints

URL	Transport	State	Latency	Checked
https://quantumscan.io/api/mcp	streamable-http	needs auth	104 ms	3 min ago

Alternatives to QuantumScan PQC Scanner

same job, measured the same way

FinishKit

by finishkit

FinishKit MCP: scan GitHub repos for security vulnerabilities, deployment blockers, and quality

43 installs/wk local only

quantakrypto pqc-tools

by quantakrypto

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

54 installs/wk 11 tools answering

NPMScan

by salemalem

Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups

23 tools answering

Sekura

by sekura

Scan a GitHub repository for vulnerabilities, with proof for every finding, from your coding agent.

answering

Flagrix

by flagrix-io

Scan GitHub repos and profiles for malware before cloning — commit-pinned risk verdicts for agents

84 installs/wk local only

Grisoco AI security audits

by grisoco

Smart-contract security audits for EVM chains and DAML: quote, run and fetch reports.

answering

Feldspar free repository security scan

by project-feldspar

Free deterministic security scan of public git repos: OSV.dev vulnerable deps, secrets, config lint.

2 tools answering

Repo-to-RAG

by evozim

GitHub repository vectorizer and context synthesizer for RAG pipelines.

answering

QuantumScan PQC Scanner — questions

Answers built from our own checks of this server.

What can QuantumScan PQC Scanner do?

It exposes 4 tools, read directly from the server on our last check. Among them: check_pqc_risk, get_scan_result, scan_contract, scan_repository. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is QuantumScan PQC Scanner working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 124 ms. The bar chart above shows every period we have measured.

How do I connect QuantumScan PQC Scanner?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does QuantumScan PQC Scanner need an API key?

Yes. Every time we knock, QuantumScan PQC Scanner answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is QuantumScan PQC Scanner?

It answers our handshake in 124 ms on average, which is faster than 88% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.