d3lta02/sepolia-prover-mcp
If you are the rightful owner of sepolia-prover-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
Succinct Prover MCP v2.0 is a Model Context Protocol server designed for running Succinct Network provers efficiently.
run_prover
Start your prover with smart defaults
stop_prover
Stop running prover gracefully
delete_prover_completely
Remove all containers and images
show_live_prover_logs
Monitor real-time prover activity
detect_hardware
Check your system capabilities
Succinct Prover MCP v2.0
A Model Context Protocol (MCP) server for running Succinct Network provers.
Quick Start
# 1. Install & Setup
npm install
npm run build
npm run init # Interactive setup with AI assistant
# 2. Use with AI
"Run Succinct Prover"
"Show live prover logs"
"Stop prover"
Required Software
- Node.js 18+ - Download here
- Docker Desktop - Download here
- Docker must be running before setup
Setup Required
1. Get Test Tokens
- Sepolia ETH: Use any Sepolia faucet
- PROVE tokens: Official Succinct Faucet
2. Create Prover Contract
Visit: https://staking.sepolia.succinct.xyz/prover
- Click "Create Prover"
- Copy the contract address (this is your
PROVER_ADDRESS
) - Important: This is NOT your wallet address!
3. Configure Environment
The npm run init
command creates your configuration file automatically.
Manual setup (.env file):
PROVER_ADDRESS=0x1234567890123456789012345678901234567890 # Contract address from step 2
PRIVATE_KEY=1234567890123456789012345678901234567890123456789012345678901234 # Your wallet private key (64 chars, no 0x)
Available Tools
run_prover
Start your prover with smart defaults
stop_prover
Stop running prover gracefully
delete_prover_completely
Remove all containers and images
show_live_prover_logs
Monitor real-time prover activity
detect_hardware
Check your system capabilities
calibrate_prover_hardware
Optimize for maximum earnings
get_environment_status
Check configuration status
get_system_health
Overall system status check
PROVER_ADDRESS Explained
Common Mistake: Using wallet address instead of prover contract address
Correct Process:
- Go to https://staking.sepolia.succinct.xyz/prover
- Connect your wallet (MetaMask/WalletConnect)
- Click "Create Prover" → Transaction creates a contract
- Copy the contract address (shown after creation)
- Use this contract address as your
PROVER_ADDRESS
Why? Your wallet creates a prover contract. The prover software needs the contract address, not your wallet address.
Common Workflows
First Time Setup
1. "Get PROVE tokens" (faucet)
2. "Detect hardware"
3. "Run Succinct Prover"
Daily Operation
1. "Show live prover logs" (check status)
2. "Run Succinct Prover" (if stopped)
3. Monitor prover via logs
Maintenance
1. "Stop prover" (graceful stop)
2. "Delete prover completely" (full cleanup)
3. System updates/maintenance
4. "Run Succinct Prover" (restart)
Configuration
Default Values (Conservative)
- CPU Mode: 500,000 PGUs/sec, 0.8 PROVE per billion PGUs
- GPU Mode: 1,500,000 PGUs/sec, 0.4 PROVE per billion PGUs
- Auto-detect: Smart hardware detection
Optimization
- Run
"Calibrate my prover hardware"
for optimal bid prices - Higher throughput = more competitive = more earnings
- Lower bid prices = more competitive but less profit per proof
Security & Safety
- Testnet Only: Sepolia network for safe testing
- Test Wallet: Use a separate wallet with small amounts
- Never Share: Keep your private key secure
- Backup: Save your prover contract address
Troubleshooting
"No prover containers found"
1. Check: "Get environment status"
2. Try: "Run Succinct Prover"
3. Verify: Docker is running
"Authentication failed"
1. Check: PROVER_ADDRESS is contract address (not wallet)
2. Check: PRIVATE_KEY is 64 characters, no 0x prefix
3. Recreate: Run "npm run init" again
"Container not found"
1. Check: "Show live prover logs"
2. Restart: "Run Succinct Prover"
3. Clean: "Delete prover completely" then restart
Poor Earnings
1. Optimize: "Calibrate my prover hardware"
2. Check: "Detect hardware" (GPU vs CPU)
3. Monitor: Network competition via logs
Monitoring
Real-time Monitoring
- AI Tools:
"Show live prover logs"
(formatted) - Terminal:
docker logs -f [container-id]
(raw) - Web: https://explorer.sepolia.succinct.xyz/
Performance Metrics
- Proofs fulfilled: Count in logs
- Bidding success: Ratio of bids to wins
- Earnings: PROVE tokens earned
- Uptime: Container running time
Official Resources
- Staking Interface: https://staking.sepolia.succinct.xyz/
- Documentation: https://docs.succinct.xyz/docs/provers/
- Network Explorer: https://explorer.sepolia.succinct.xyz/
- PROVE Faucet: Google Form
Pro Tips
For Better Earnings
- Calibrate First: Run hardware calibration for optimal settings
- Monitor Competition: Check network activity during different hours
- Use GPU: If you have NVIDIA GPU with CUDA support
- Stable Connection: Ensure reliable internet for consistent bidding
Resource Requirements
- Minimum: 4 cores, 8GB RAM, 20GB disk
- Recommended: 8+ cores, 16GB+ RAM, SSD
- GPU Mode: NVIDIA GPU with CUDA support
Development & Advanced
Build from Source
git clone [repository]
cd prover-mcp
npm install
npm run build
Manual Container Management
# List containers
docker ps --filter "name=succinct-prover"
# Manual stop
docker stop [container-id]
# View logs
docker logs -f [container-id]
Environment Debugging
# Check variables
"Get environment status"
# Reset configuration
npm run init
v2.0 - Simple & Reliable | Test Network Only | Built by @Delta_web3