QuantumScan PQC Scanner
REMOTE · QUANTUMSCAN.IO · SCANNED SEP 20
PQC scanner for GitHub repos and smart contracts. Detects quantum-vulnerable ECDSA/RSA.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 402. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the QuantumScan PQC Scanner MCP server?
QuantumScan PQC Scanner is a hosted endpoint at https://quantumscan.io/api/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 · quantumscan.io
claude mcp add --transport http gaiabio12-design-quantumscan-pqc-scanner 'https://quantumscan.io/api/mcp'
{
"mcpServers": {
"gaiabio12-design-quantumscan-pqc-scanner": {
"url": "https://quantumscan.io/api/mcp"
}
}
} {
"servers": {
"gaiabio12-design-quantumscan-pqc-scanner": {
"type": "http",
"url": "https://quantumscan.io/api/mcp"
}
}
} [mcp_servers.gaiabio12-design-quantumscan-pqc-scanner] url = "https://quantumscan.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gaiabio12-design-quantumscan-pqc-scanner": {
"type": "remote",
"url": "https://quantumscan.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add gaiabio12-design-quantumscan-pqc-scanner --url 'https://quantumscan.io/api/mcp' --transport streamable-http
mcp_servers:
gaiabio12-design-quantumscan-pqc-scanner:
url: "https://quantumscan.io/api/mcp" {
"McpServers": {
"gaiabio12-design-quantumscan-pqc-scanner": {
"Transport": "http",
"Url": "https://quantumscan.io/api/mcp"
}
}
} assistant mcp add gaiabio12-design-quantumscan-pqc-scanner -t streamable-http -u 'https://quantumscan.io/api/mcp'
{
"mcpServers": {
"gaiabio12-design-quantumscan-pqc-scanner": {
"type": "http",
"url": "https://quantumscan.io/api/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.
- 27 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- 26 Aug 26 −51
- 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
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://quantumscan.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quantumscan.io | CN=YR2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | RSA 2048 | SHA256-RSA | 643a92db12ac6c6898b4c3f277c13887f96 |
| SANs: quantumscan.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of quantumscan.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| quantumscan.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 402 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://quantumscan.io/api/mcp | HTTP error | 402 | |
| http (plaintext) | http://quantumscan.io/api/mcp | HTTPS enforced | 308 | https://quantumscan.io/api/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 →
check_pqc_risk ~95
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).
| Name | Type | Req | Description |
|---|---|---|---|
| algorithms | array | yes | Algorithm names, e.g. ["ECDSA", "RSA-2048", "ML-KEM-768"] |
No output schema declared.
No examples provided.
get_scan_result ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | UUID returned by scan_repository |
No output schema declared.
No examples provided.
scan_contract ~249
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).
| Name | Type | Req | Description |
|---|---|---|---|
| contract_address | string | yes | Ethereum-format contract address (0x + 40 hex chars). Example: 0xdAC17F958D2ee523a2206206994597C13D831ec7 |
| network | number | – | Chain ID. Default: 1 (Ethereum Mainnet). Supported: 1, 137 (Polygon), 42161 (Arbitrum One), 10 (Optimism), 8453 (Base), 56 (BNB Chain), 43114 (Avalanche C-Chain). |
No output schema declared.
No examples provided.
scan_repository ~96
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).
| Name | Type | Req | Description |
|---|---|---|---|
| repo_url | string | yes | Full repository URL. Example: https://github.com/uniswap/v3-core |
No output schema declared.
No examples provided.
What is the QuantumScan PQC Scanner MCP server?
QuantumScan PQC Scanner is an MCP server listed in the public MCP registry as io.github.gaiabio12-design/quantumscan-pqc-scanner. PQC scanner for GitHub repos and smart contracts. Detects quantum-vulnerable ECDSA/RSA. This page covers its hosted endpoint (https://quantumscan.io/api/mcp).
Is the QuantumScan PQC Scanner MCP server safe to use?
QuantumScan PQC Scanner scores 25 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 QuantumScan PQC Scanner MCP server expose?
QuantumScan PQC Scanner exposes 4 tools: scan_repository, get_scan_result, check_pqc_risk, scan_contract. Their descriptions and schemas cost roughly 547 tokens of context every time the server is loaded.
Does the QuantumScan PQC Scanner MCP server require authentication?
No. We connected to QuantumScan PQC Scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QuantumScan PQC Scanner MCP server still maintained?
QuantumScan PQC Scanner 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.