io.github.kota1026/quantumguard-mcp
NPM · QUANTUMGUARD-MCP · SCANNED AUG 3
Post-quantum cryptography security scanner. Detect ECDSA/RSA vulnerabilities, NIST compliance.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 95), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 95), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 128 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 532 tokens (~59/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · quantumguard-mcp
claude mcp add kota1026-quantumguard-mcp -- npx -y quantumguard-mcp
codex mcp add kota1026-quantumguard-mcp -- npx -y quantumguard-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kota1026-quantumguard-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"quantumguard-mcp"
],
"enabled": true
}
}
} openclaw mcp add kota1026-quantumguard-mcp --command npx --arg -y --arg quantumguard-mcp
mcp_servers:
kota1026-quantumguard-mcp:
command: "npx"
args: ["-y", "quantumguard-mcp"] {
"mcpServers": {
"kota1026-quantumguard-mcp": {
"command": "npx",
"args": [
"-y",
"quantumguard-mcp"
]
}
}
} 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.
- 2 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +13
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −3
- 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 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
pqc_algorithm_comparison ~98
Compare pre-quantum and post-quantum signature algorithms side-by-side (performance, size, security)
| Name | Type | Req | Description |
|---|---|---|---|
| algorithms | array | — | Algorithm IDs to compare. Available: ecdsa-secp256k1, ed25519, rsa-2048, ml-dsa-44, ml-dsa-65, ml-dsa-87, slh-dsa-128s, slh-dsa-128f |
No output schema declared.
No examples provided.
pqc_analyze_signature ~51
Analyze a hex-encoded signature or key to identify the algorithm and check quantum safety
| Name | Type | Req | Description |
|---|---|---|---|
| hex_data | string | yes | Hex-encoded signature or public key (with or without 0x prefix) |
No output schema declared.
No examples provided.
pqc_compliance_check ~60
Check a project directory for NIST post-quantum cryptography compliance (FIPS 202/203/204/205, CNSA 2.0)
| Name | Type | Req | Description |
|---|---|---|---|
| project_path | string | yes | Absolute path to the project directory to check |
No output schema declared.
No examples provided.
pqc_key_size_comparison ~36
Compare key and signature sizes between pre-quantum and post-quantum algorithms to plan storage/bandwidth impact
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pqc_migration_guide ~72
Get migration code templates for converting pre-quantum crypto to post-quantum (ECDSA→Dilithium, RSA→ML-KEM, SHA-256→SHA3)
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | — | Target programming language |
| migration_type | string | yes | Type of cryptographic migration |
No output schema declared.
No examples provided.
pqc_nist_standards_reference ~45
Get a quick reference of NIST post-quantum cryptography standards (FIPS 203, 204, 205) with parameters and recommendations
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pqc_recommend_algorithm ~68
Get algorithm recommendations based on your use case, performance requirements, and target environment
| Name | Type | Req | Description |
|---|---|---|---|
| priority | string | — | What to optimize for |
| target_environment | string | — | Where the crypto operations will run |
| use_case | string | yes | Primary use case for the cryptographic operation |
No output schema declared.
No examples provided.
pqc_scan_directory ~54
Recursively scan a directory for quantum-vulnerable cryptographic patterns across all source files
| Name | Type | Req | Description |
|---|---|---|---|
| directory_path | string | yes | Absolute path to the directory to scan |
| recursive | boolean | — | Scan subdirectories recursively |
No output schema declared.
No examples provided.
pqc_scan_file ~48
Scan a single file for quantum-vulnerable cryptographic patterns (ECDSA, RSA, weak hashes, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Absolute path to the file to scan |
No output schema declared.
No examples provided.