QuantumScan PQC Scanner

Each tool has a distinctly different purpose: check_pqc_risk is an instant algorithm check, scan_repository is an asynchronous repo submission, scan_contract is a synchronous smart contract scan, and get_scan_result polls repo scan results. The scanning tools are differentiated by target type and execution model, so there is no ambiguity.

All tool names follow a consistent lower_snake_case verb_noun pattern: check_pqc_risk, get_scan_result, scan_contract, scan_repository. The verbs (check, get, scan) clearly reflect the action, and the nouns (pqc_risk, scan_result, contract, repository) specify the object. This is a uniform and predictable naming convention.

With just 4 tools, the server is well-scoped for its purpose. It covers the essential operations: a quick pre-scan check, a repo scan submission, a result retrieval, and a direct contract scan. This is a concise set that avoids unnecessary bloat while providing all needed entry points.

The tool surface covers the full workflow: check_pqc_risk provides a rapid pre-assessment, scan_repository starts an async scan, get_scan_result retrieves the scan outcome and CBOM, and scan_contract handles synchronous contract evaluation. There are no obvious missing operations or dead ends for the stated domain.