Quantumguard MCP

Name: Quantumguard MCP
Author: kota1026

by kota1026version 1.0.0i★ –iRuns on your computer

Registry nameio.github.kota1026/quantumguard-mcp

Install

Overview

Description from the maker (original English)

Post-quantum cryptography security scanner. Detect ECDSA/RSA vulnerabilities, NIST compliance.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 46/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Cybersecurity

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "quantumguard": {
      "command": "npx",
      "args": [
        "-y",
        "quantumguard-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add quantumguard -- npx -y quantumguard-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "quantumguard": {
      "command": "npx",
      "args": [
        "-y",
        "quantumguard-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "quantumguard": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "quantumguard-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account kota1026, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Cybersecurityi

More stars than 0% of the other 1000 servers in this category
Published to the registry more recently than 10% of the other 1000 servers in this category
Basic checks equal to or better than 100% of the other 1000 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Quantumguard MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: EchelonGraph CVE & Exposure, KillerSkills, Phishnoo Sandbox

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

EchelonGraph CVE & Exposure

CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.

by echelongraphEarly↓ 1.4K/wkUpdated today

Computer or cloud✓ echelongraph.io

Install

KillerSkills

Security verdicts for agent skills and MCP servers, from sandbox runs, before you install them.

by cyligence-karimGrowing↓ 3.1K/wkUpdated today

Runs on your computer

Install

Phishnoo Sandbox

Explore synthetic security awareness metrics and file example threat reports.

by api.phishnoo.nlEarlyUpdated today

Runs in the cloud✓ api.phishnoo.nl

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Quantumguard MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Cybersecurityi

Common questions

Alternatives

EchelonGraph CVE & Exposure

KillerSkills

Phishnoo Sandbox

README from the maker

Quantum Shield

What is Quantum Shield?

Key Features

Architecture

9 Core Sequences

Tech Stack

Deployed Contracts

L1: Ethereum Sepolia

L3: Arbitrum Sepolia (12 contracts)

Quick Start

Prerequisites

Development Setup

2. Run database migrations

3. Start backend API (port 8080)

4. Start frontend (port 3000)

Verify

{"status":"healthy"}

Project Structure

Testing

Frontend E2E

Smart Contracts

Security

Audit Status

License