About Svm MCP Server
Svm MCP Server is an MCP server in the Blockchain category: first-party SAISO SVM MCP server with canonical parity operations.
Install
claude mcp add svm-mcp-server -- npx -y @saiso/svm-mcp-servernpx -y @saiso/svm-mcp-serverThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Svm MCP Server
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
SAISO
A developer-first toolkit for building, testing, and deploying EVM and SVM agents using ElizaOS with concurrent MCP server orchestration.
SAISO combines local orchestration, agent-aware CI/CD automation, and autonomous feedback loops to create a seamless development pipeline for AI agents that interact with multiple blockchain networks simultaneously. Whether you're developing cross-chain trading bots, multi-network governance tools, or complex DeFi automation routines, SAISO gives your agents the infrastructure they need to thrive across EVM and SVM ecosystems.
🚀 Features
1. 🧪 Multi-Server Agent Lab (saiso dev)
Spin up a complete multi-chain testing environment with one command:
- Concurrent MCP Servers: Run multiple EVM/SVM MCP server instances concurrently
- Smart Resource Management: Automatic port allocation (3001-3100) with conflict detection
- Multi-Chain Support: EVM networks plus SVM (Solana) support
- Environment-Variable Security: No local key storage - environment variables only
- Agent Memory Persistence: Chain-agnostic memory preservation across server changes
- Real-time Monitoring: Health checks, status reporting, and graceful shutdown handling
2. 🔗 Concurrent Multi-Server Architecture
Revolutionary multi-server orchestration for complex agent workflows:
- User-Defined Server Names: Descriptive server naming (e.g., "svm-trading", "eth-defi", "weather-bot")
- Individual Server Configs: Isolated JSON configurations in
.saiso/servers/directory - Server-Specific Environments: Clean environment variable organization per server
- Environment Safety: Automatic testnet-only testing with mainnet protection.
- Monorepo Support: Turbo-powered builds with intelligent caching.
3. 🧠 Multi-Environment Configuration
Environment Management
- Testnet (Default): Safe development environment with automatic faucet integration
- Mainnet: Production environment with confirmation prompts and safety checks
- Devnet: Experimental features and latest protocol updates
Configuration Features
- dotenv Integration: Multiple
.envfiles (.env.testnet,.env.mainnet,.env.devnet) - Environment Switching: Safe switching with backup and validation
- Private Key Management: Secure handling with masking and validation
- Network Validation: Automatic RPC and chain ID verification
📦 Tech Stack
- Agent Runtime: ElizaOS
- Blockchain Interface: EVM and SVM MCP orchestration
- Build System: Bun + Turbo (monorepo with intelligent caching)
- CLI Framework: Commander.js with beautiful UX and interactive prompts
- Configuration: dotenv with multi-environment support
- CI/CD: GitHub Actions with automated testing
✅ Why Use SAISO?
| Benefit | Description |
|---|---|
| Developer UX | One-command setup for EVM/SVM agents with beautiful CLI |
| Configuration Wizard | Interactive setup with validation and network testing |
| Reliability | Multi-environment testing with automated validation |
| Safety | Testnet-first development with mainnet confirmation prompts |
| Environment Management | Safe switching with backups and dry-run testing |
| Extensibility | Template-driven feature system ready for expansion |
🛠️ Getting Started
Prerequisites
Global Installation (Recommended)
# Install SAISO globally from npm
npm install -g @saiso/cli
# Verify installation
saiso --help
# Create your first agent
saiso new my-agent --env testnet
# Navigate to your project
cd my-agent
bun install
# Configure your environment
cp .env.example .env
# Edit .env and add your PRIVATE_KEY
# Start development
saiso dev
Development Installation
For contributing or using the latest development version:
# Clone and build the toolkit
git clone https://github.com/BHIIKTOR/saiso.git
cd saiso
bun install
bun run build
# Link CLI globally for development
cd packages/saiso-cli
npm link
# Now you can use 'saiso' command anywhere
saiso new my-agent --env testnet
Available Commands
saiso new <project-name> # Create a new multi-chain agent project
saiso dev # Start development environment
saiso config # Enhanced configuration management with wizard
saiso add <feature> # Add features to your agent
saiso switch-env <env> # Safe environment switching with backups
saiso switch-server <type> # Server switching with backup/restore
saiso mcp # Multi-server management commands
saiso env # Environment variable management per server
saiso identity # Build/validate ERC-8004 discovery metadata
saiso policy # Validate payment/trust policy files
saiso runtime transport list # List chat transport capabilities
saiso runtime goal list # List conversational goal-runner records
saiso runtime goal create <id> --title "..." # Create a goal run
saiso runtime goal action <id> --type request-approval|approve|start|pause|cancel|fail|complete
saiso docker # Docker doctor/ps/clean runtime commands
saiso test # Run comprehensive test suite
saiso test localnet --chain evm # Run Dockerized localnet integration flow
saiso test add # Add test templates to your project
saiso status # Show detailed MCP server status
saiso health # Health checks and network diagnostics
saiso receipts # Payment receipt summary (use --json for machine output)
Multi-Server Management
SAISO's multi-server architecture allows concurrent operation of multiple configured servers:
# Add servers with user-defined names
saiso mcp add --name "svm-trading" --type svm --network solana-mainnet
saiso mcp add --name "eth-defi" --type evm --network ethereum
# Server operations
saiso mcp list # List all configured servers
saiso mcp start svm-trading # Start specific server
saiso mcp stop eth-defi # Stop specific server
saiso mcp restart svm-trading # Restart server
saiso mcp status --resources # Show resource allocations
saiso mcp call --tool premium-simulate --params '{}' --min-trust-score 0.7 --max-cost-usd 0.5 --routing-profile balanced
# Environment management per server
saiso env generate svm-trading # Generate .env template for server
saiso env validate # Validate all server environments
saiso env list --show-values # List environment configuration
Enhanced Configuration Management
SAISO includes powerful configuration management with rich UX:
# Interactive configuration wizard
saiso config --wizard
# Validate current environment
saiso config --validate
# Test network connectivity
saiso config --test-network
# Get/set individual values
saiso config --get rpcUrl
saiso config --set privateKey=0x...
Safe Environment Switching
Advanced environment switching with comprehensive safety features:
# Switch with automatic backup
saiso switch-env mainnet --backup
# Dry-run to see what would change
saiso switch-env mainnet --dry-run
# Force switch (skip validation)
saiso switch-env testnet --force
Available Features
SAISO now exposes a broader feature surface across execution, policy, observability, and Privy-backed wallet workflows.
List all installable features at any time:
saiso add --list
Core feature categories:
- Execution and Routing
quote_and_swaptx_lifecycle_managercross_chain_intent_router
- Safety and Policy
preflight_risk_checkspolicy_guardrails_runtimeallowance_and_permission_manager
- State and Operations
portfolio_state_and_pnlevent_ingest_and_triggersscheduler_and_workflow_runnerobservability_and_incident_hooksoracle_and_market_data_layerlocal_strategy_test_harness
- Foundational wallet/network tools
query_balancesend_tokensinteract_contractgas_estimationcheck_network_status
Privy feature pack:
- Generic Privy workflows
privy_client_baseprivy_wallet_lifecycleprivy_balance_and_historyprivy_transferprivy_actions_swapprivy_policy_controlsprivy_intents_routerprivy_webhook_ingestprivy_accounts
- EVM-specific Privy workflows
privy_signing_evmprivy_advanced_execution_evm
- SVM-specific Privy workflows
privy_signing_svm
Quick install examples:
# Generic + parity-safe features
saiso add preflight_risk_checks
saiso add tx_lifecycle_manager
saiso add quote_and_swap
# Privy foundation + wallet flows
# Privy runtime features install privy_client_base automatically when needed.
saiso add privy_wallet_lifecycle
saiso add privy_transfer
# Chain-specific Privy signing
saiso add privy_signing_evm # in EVM projects
saiso add privy_signing_svm # in SVM projects
Detailed Privy documentation:
spec/privy-template-expansion-01/README.mddocs/privy-feature-pack.mddocs/template-live-provider-smokes.md
Execution semantics:
quote_and_swapfetches quotes by default. Withexecute: true, it builds an executable transaction payload but does not sign or broadcast.tx_lifecycle_manageris read-only and classifies pending, confirmed, finalized, failed, or unknown transaction state.policy_guardrails_runtimeandpreflight_risk_checksare decision layers; they do not submit transactions.- Privy signing and transfer features call Privy APIs and can authorize or move real assets when configured with live credentials. Use sandbox credentials or quote/read-only flows for first validation.
gas_estimationreads RPC fee data and optional price APIs; it does not submit transactions.
Docker Workflows
SAISO supports both MCP runtime modes:
npx(default)docker(containerized MCP runtime)
Docker Runtime Diagnostics
saiso docker doctor
saiso docker ps
saiso docker clean
Start Dev with Docker MCP
saiso dev --mcp docker
Optional overrides:
saiso dev --mcp docker \
--docker-image ghcr.io/mcpdotdirect/evm-mcp-server:latest \
--docker-pull-policy if-not-present \
--docker-network bridge
EVM Localnet Testing (Foundry Anvil)
saiso test localnet --chain evm
Localnet test flow:
- Boots Anvil in Docker
- Waits for RPC readiness (
http://127.0.0.1:8545) - Runs
localnet:setup,localnet:deploy,localnet:testscripts when present - Falls back to Foundry (
forge) conventions when configured - Tears down resources (or keep with
--keep-on-fail)
🏗️ Project Structure
saiso/
├── packages/
│ ├── saiso-cli/ # CLI tool with all commands
│ ├── saiso-core/ # Core utilities and scaffolding
│ └── (archived legacy packages under spec/old-saiso/archive/)
├── templates/
│ ├── agent-evm/ # EVM agent template
│ ├── agent-svm/ # SVM agent template
│ └── features/ # Feature templates
├── docs/ # Operator and feature integration guides
├── examples/ # Usage examples and documentation
├── .github/workflows/ # CI/CD templates
└── README.md
🧪 Example Usage
Creating a New Agent
# Interactive creation
saiso new my-agent
# Quick creation with options
saiso new trading-bot --env testnet --agent-name "TradingBot" --yes
# Create with deployable service blueprint
saiso new paid-service-agent --service-blueprint --yes
Service blueprint scaffolds include:
src/service.tspaid endpoint hostGET /healthz+GET /readyzGET /.well-known/agent-registration.jsonPOST /paid/toolpayment-aware MCP tool execution
Identity Discovery (ERC-8004)
# Build registration from current project config
saiso identity build
# Validate generated registration
saiso identity validate
# Print derived registration JSON without writing files
saiso identity show
# Sync local registration from remote registry API
saiso identity sync --registry-base-url https://registry.example
# CI drift check (fails when local and remote differ)
saiso identity sync --registry-base-url https://registry.example --dry-run --strict
Policy Validation
# Validate default policy files
saiso policy validate
# Strict mode fails if policy files are missing
saiso policy validate --strict
Hardening Gates (CI Parity)
Run the same hard gates locally before release/merge:
npx tsc -p packages/saiso-core/tsconfig.json
npx tsc -p packages/saiso-cli/tsconfig.json
bun test packages/saiso-core/tests
bun test packages/saiso-cli/src
bun test packages/saiso-core/tests/service-blueprint.test.ts
node spec/saiso-v1.0/scripts/smoke-x402-mpp.mjs
saiso policy validate --strict \
--payment-file spec/hardening-01/fixtures/policies/payment-policy.json \
--trust-file spec/hardening-01/fixtures/policies/trust-policy.json
Required CI settings:
IDENTITY_DRIFT_CHECKrepository variable (set totrueto enable strict identity drift gate).IDENTITY_REGISTRY_BASE_URL,IDENTITY_AGENT_REGISTRY,IDENTITY_AGENT_IDrepository secrets (identity drift gate).NPM_TOKENrepository secret (publish workflow).
Development Workflow
# Start development environment
saiso dev --env testnet --mcp npx
# Check configuration
saiso config --list
# Switch to mainnet (with safety prompts)
saiso switch-env mainnet
Generated Project Features
- Multi-environment configuration with
.env.testnet,.env.mainnet,.env.devnet - Complete ElizaOS integration with character configuration
- TypeScript setup with proper module resolution
- Comprehensive README with usage instructions
- Git integration with proper
.gitignore
🧩 Roadmap
✅ MVP Complete
- CLI tool with project scaffolding
- Multi-environment configuration management
- MCP server orchestration (npx)
- ElizaOS integration
- GitHub Actions CI/CD templates
- Expanded feature template implementation (core + ROI + Privy packs)
- Advanced gas estimation with MEV protection
- Network status monitoring and health checks
- Multi-Server Concurrent Architecture - Revolutionary concurrent server orchestration
- Multi-Chain Environment Management - Server-specific environment variables
- Agent Memory Persistence - Chain-agnostic memory preservation
- Enhanced CLI Commands -
saiso mcpandsaiso envcommand suites - Comprehensive documentation
🚧 Next Phase
- Complete testing framework (
saiso testcommand) - User agent testing suite with extensible test generation
- Unit test coverage for all packages
- Behavior testing framework
- Agent self-debugging capabilities
- Auto-documentation generation
- Advanced deployment automation
🔮 Future Extensions
- Additional EVM/SVM features (staking, DEX integration, etc.)
- Terraform module for cloud deployment
- Agent behavior registry
- Nix + Docker hybrid environments
🤝 Contributing
Pull requests, EVM/SVM plugins, behavior templates, and feedback are welcome!
Development Setup
git clone https://github.com/BHIIKTOR/saiso.git
cd saiso
bun install
bun run build
# Test the CLI
cd packages/saiso-cli
node dist/cli.js --help
Adding Features
The feature template system is ready for expansion. Each feature should include:
- Source code module
- ElizaOS action/evaluator integration
- Test cases
- Documentation
📄 License
MIT
Built with ❤️ by the saiso Team.
For questions, issues, or contributions, please visit our GitHub repository.
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.