
Quantumguard Mcp
- Updated July 28, 2026
- kota1026/quantum-shield
QuantumGuard MCP is a MCP server that scans projects for classical crypto (ECDSA/RSA) exposure and NIST-oriented post-quantum compliance gaps.
About
QuantumGuard MCP is a Model Context Protocol server that gives AI coding agents a focused post-quantum cryptography scanner. developers and small teams use it when they need to know whether their app still depends on classical public-key schemes such as ECDSA or RSA before those choices become expensive to fix under NIST PQC migration timelines. The server connects over stdio via the published npm package, so you register it once in your agent and invoke scan-style tools during security review rather than exporting logs by hand. It is aimed at backend and infrastructure-heavy products—APIs, CLIs, and SaaS—that touch TLS, JWTs, wallet signatures, or custom crypto. It does not replace a full penetration test or formal FIPS audit, but it surfaces algorithm-level debt early in the ship phase when refactors are still cheap. Pair it with SmartGuard or VaultGuard from the same maintainer when you also ship smart contracts or DeFi vault logic.
- Flags ECDSA and RSA usage that may be vulnerable in a harvest-now-decrypt-later threat model
- Maps findings toward NIST post-quantum cryptography guidance for prioritization
- Runs as stdio MCP over npm package quantumguard-mcp (registry v0.1.1)
- Designed for agent-driven scans from Claude Code, Cursor, and similar coding agents
- Complements manual pentests with repeatable algorithm inventory across a codebase
Quantumguard Mcp by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
claude mcp add quantumguard-mcp -- npx -y quantumguard-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | quantumguard-mcp |
|---|---|
| Transport | STDIO |
| Auth | None |
| Last updated | July 28, 2026 |
| Repository | kota1026/quantum-shield ↗ |
What it does
Scan repos and crypto usage for classical algorithms that fail post-quantum readiness and NIST-aligned migration planning before you ship keys or TLS configs.
Who is it for?
Best when you're shipping auth, payments, or blockchain-adjacent features and want agent-assisted PQC readiness checks in the security pass before release.
Skip if: Skip if you only need Vue or UI composable docs, or pure smart-contract bytecode audits without application-layer crypto.
What you get
After registering the server, your agent can return structured vulnerability and compliance-oriented findings so you can prioritize PQC migration before launch.
- Agent-readable report of ECDSA/RSA and related classical crypto exposure
- NIST-oriented compliance gap signals for migration planning
- Repeatable scan workflow invokable from the IDE agent
By the numbers
- Server schema: Model Context Protocol 2025-12-11
- npm identifier: quantumguard-mcp at package version 0.1.1
- Transport: stdio
README.md
Quantum Shield
Post-quantum asset protection protocol for Ethereum using NIST-standardized cryptography
What is Quantum Shield?
Quantum Shield protects smart contract assets against quantum computing threats using NIST FIPS 204 (ML-DSA/Dilithium) and FIPS 205 (SLH-DSA/SPHINCS+) dual post-quantum signatures, combined with a decentralized Prover Pool, VRF-based selection, and time-locked custody.
Key Features
- Dual PQC Signatures — ML-DSA-65 + SLH-DSA for defense-in-depth
- Prover Pool — Decentralized verification with stake-weighted selection via VRF
- Time-Locked Custody — 24h normal unlock, 7-day emergency path with bond
- Observer Network — Independent challenge system with quadratic slashing
- On-Chain Governance — veQS token voting, security council, insurance fund
- 11 Sub-Applications — Consumer, Prover, Observer, Explorer, Enterprise, Governance, Admin
Architecture
┌─────────────────────────────────────────────────────────────────┐
│ Frontend (Next.js 15) 11 apps, 136 routes, ja/en i18n │
├─────────────────────────────────────────────────────────────────┤
│ Backend API (Rust/Axum) REST API, SIWE auth, Auto-Claim │
├──────────────────┬──────────────────────────────────────────────┤
│ L1: Sepolia │ L3: Arbitrum Sepolia │
│ • Vault │ • CoreLayer • Governor │
│ • ProverRegistry│ • veQS • RewardRouter │
│ • SPHINCS+ Vfy │ • QSToken • InsuranceFund │
└──────────────────┴──────────────────────────────────────────────┘
9 Core Sequences
| # | Flow | Path |
|---|---|---|
| 1 | Consumer Lock | Frontend → API → DB → L1 Vault |
| 2 | Normal Unlock | 24h timelock → Prover verification → L1 claim |
| 3 | Emergency Unlock | Bond deposit → 7-day lock → Emergency path |
| 4 | Prover Registration | Stake → VRF selection → Proof generation |
| 5 | Observer Challenge | Monitor → Challenge → VRF arbitration |
| 6 | Slashing | Quadratic penalty → L1 ProverRegistry |
| 7 | Governance | veQS voting → Proposal execution on L3 |
| 8 | Emergency Pause | Security council → L1 pause |
| 9 | Token Hub | Stake QS → veQS → Rewards |
Tech Stack
| Layer | Technology |
|---|---|
| Frontend | Next.js 15, TypeScript, Tailwind CSS, Wagmi, RainbowKit |
| Backend | Rust, Axum, PostgreSQL, Redis, RabbitMQ |
| Contracts | Solidity 0.8.24 (Foundry), deployed to Sepolia + Arbitrum Sepolia |
| Cryptography | NIST FIPS 204 (ML-DSA-65), FIPS 205 (SLH-DSA), SHA3-256 |
| SDK | WASM (Rust → wasm-pack), npm-publishable |
| Testing | Playwright (E2E), Vitest, cargo test, Foundry forge test |
Deployed Contracts
L1: Ethereum Sepolia
| Contract | Address |
|---|---|
| Vault | 0x07012aeF87C6E423c32F2f8eaF81762f63337260 |
| ProverRegistry | 0x08e1fc1A0d614bc132B48950760c7A291cCB8946 |
| SPHINCS+ Verifier | 0xD090b5A627d9bd6D96a8b5f6F504ebCa79980103 |
L3: Arbitrum Sepolia (12 contracts)
| Contract | Address |
|---|---|
| CoreLayer | 0xb04F4DFe093dC80420117EDC8300f5EB6F6EDBf0 |
| veQS | 0xE72dFa97C9E452dC0b8E6aa026c910D21B20fCAE |
| Governor | 0xe93b8129DC3dBD48E5d78C5A4C156DD1BFa8D65B |
| QSToken | 0xBD66beBE19E664dF143da54808d746192e4f2ee2 |
All L3 contracts verified on Sourcify.
Quick Start
Prerequisites
- Docker & Docker Compose
- Rust 1.75+ with cargo
- Node.js 20+ with pnpm
- Foundry (forge, anvil)
Development Setup
# 1. Start infrastructure
docker compose up -d postgres redis rabbitmq l3-node minio minio-init
# 2. Run database migrations
cd src/api/api
DATABASE_URL="postgresql://quantum:quantum_dev@localhost:5432/quantum_shield" sqlx migrate run
# 3. Start backend API (port 8080)
cargo run --bin api-server
# 4. Start frontend (port 3000)
cd src/frontend/web
pnpm install
pnpm dev
Verify
curl http://localhost:8080/v1/health
# {"status":"healthy"}
Project Structure
quantum-shield/
├── src/
│ ├── api/api/ # Rust/Axum backend
│ │ ├── src/routes/ # API route handlers
│ │ ├── src/services/ # Business logic
│ │ ├── migrations/ # PostgreSQL migrations (17 files)
│ │ └── config/ # YAML configuration
│ ├── frontend/web/ # Next.js 15 frontend
│ │ ├── src/app/ # App Router pages (11 apps)
│ │ ├── src/components/ # 300+ React components
│ │ ├── src/hooks/ # React Query hooks per app
│ │ └── locales/ # ja/en translations
│ ├── l1/contracts/ # L1 Solidity contracts (Foundry)
│ ├── l3/ # L3 governance contracts
│ └── frontend/sdk/wasm/ # WASM SDK (Dilithium + SPHINCS+)
├── docs/
│ ├── core/SEQUENCES.md # 9 core sequence specifications
│ ├── ACTUAL_STATE.md # Current implementation state
│ └── pitch/ # Pitch deck, grant applications
├── docker-compose.yml # Development infrastructure
└── .github/workflows/ # CI/CD pipelines
Testing
# Backend
cd src/api/api && cargo test
# Frontend E2E
cd src/frontend/web && npx playwright test
# Smart Contracts
cd src/l1/contracts && forge test
Test Coverage: 137 E2E tests passing, 107 integration tests, 0 failures.
Security
- Cryptography: NIST FIPS 204 ML-DSA-65 + FIPS 205 SLH-DSA (post-quantum)
- Hashing: SHA3-256 (no keccak256 in application layer)
- Authentication: SIWE (Sign-In with Ethereum) + JWT
- Time Locks: 24h normal, 7-day emergency with bond collateral
- Slashing: Quadratic penalty for malicious provers
Audit Status
- Internal code review
- External audit (planned)
License
This project is licensed under the MIT License. See LICENSE for details.
Built for a post-quantum future.
Recommended MCP Servers
How it compares
Post-quantum crypto scanner MCP, not a general agent skill or smart-contract-only auditor.
FAQ
Who is QuantumGuard MCP for?
Developers using Claude Code or Cursor who need repeatable post-quantum and classical-algorithm checks on application and infra code.
When should I use QuantumGuard MCP?
Use it during ship-phase security review, before committing to long-lived ECDSA/RSA keys, TLS configs, or signing pipelines you cannot rotate easily.
How do I add QuantumGuard MCP to my agent?
Install the npm package quantumguard-mcp, add a stdio MCP entry pointing at that binary in your agent's MCP config, restart the client, then call the server's scan tools from chat.