Security & Testing
quantumscan.io
Scan code and smart contracts for quantum-vulnerable cryptography and fraud patterns.
ENDPOINT 1
https://quantumscan.io/api/mcp
Known tools 4
scan_repositorySubmit a GitHub, GitLab, or Bitbucket repository for post-quantum cryptography (PQC) vulnerability scanning.
Potential side effectscheck_pqc_riskInstant check (no DB, no scan) — returns whether a list of algorithm names are quantum-vulnerable.
Inferred read-onlyscan_contractScan a verified on-chain smart contract for quantum-vulnerable cryptography AND today's fraud patterns (rug pulls, honeypots, uncapped mints, reentrancy).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.quantumscan-io]
url = "https://quantumscan.io/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"quantumscan-io": {
"type": "http",
"url": "https://quantumscan.io/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: quantumscan-io
Remote MCP URL: https://quantumscan.io/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"quantumscan-io": {
"url": "https://quantumscan.io/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"quantumscan-io": {
"type": "http",
"url": "https://quantumscan.io/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "quantumscan-io",
"transport": "streamable-http",
"url": "https://quantumscan.io/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for quantumscan.io was fetched 2026-09-03T18:48:16.983Z.
quantumscan.io is assessed as RestrictedContent: Domain runs gambling-related technology.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.