CryptoData MCP Server - Real-time crypto market data, DeFi analytics, and on-chain intelligence...
Post-quantum asset protection protocol for Ethereum using NIST-standardized cryptography
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.
┌─────────────────────────────────────────────────────────────────┐
│ 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 │
└──────────────────┴──────────────────────────────────────────────┘
| # | 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 |
| 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 |
| Contract | Address |
|---|---|
| Vault | 0x07012aeF87C6E423c32F2f8eaF81762f63337260 |
| ProverRegistry | 0x08e1fc1A0d614bc132B48950760c7A291cCB8946 |
| SPHINCS+ Verifier | 0xD090b5A627d9bd6D96a8b5f6F504ebCa79980103 |
| Contract | Address |
|---|---|
| CoreLayer | 0xb04F4DFe093dC80420117EDC8300f5EB6F6EDBf0 |
| veQS | 0xE72dFa97C9E452dC0b8E6aa026c910D21B20fCAE |
| Governor | 0xe93b8129DC3dBD48E5d78C5A4C156DD1BFa8D65B |
| QSToken | 0xBD66beBE19E664dF143da54808d746192e4f2ee2 |
All L3 contracts verified on Sourcify.
# 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
curl http://localhost:8080/v1/health
# {"status":"healthy"}
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
# 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.
This project is licensed under the MIT License. See LICENSE for details.
Built for a post-quantum future.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y cryptodata-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-kota1026-cryptodata-mcp": {
"command": "npx",
"args": [
"-y",
"cryptodata-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencecryptodata-mcpnpmio.github.kota1026/cryptodata-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.