Labsco
strangelove-ventures logo

Web3 MCP

โ˜… 95

from strangelove-ventures

Interact with multiple blockchains including Solana, Ethereum, THORChain, XRP Ledger, TON, Cardano, and UTXO chains.

๐Ÿ”ฅ๐Ÿ”ฅ๐Ÿ”ฅโœ“ VerifiedFreeQuick setup

Web3 MCP

A Model-Context-Protocol server for interacting with multiple blockchains including Solana, Ethereum, THORChain, XRP Ledger, TON (The Open Network), Cardano, and UTXO chains. This server provides simple RPC endpoints for common blockchain operations, allowing secure interactions with various blockchains through environment variables.

Web3 Server MCP server

Features

Solana Operations:

  • Check SOL account balances
  • Get detailed account information
  • Transfer SOL between accounts
  • View SPL token balances
  • Get your wallet address from private key
  • Swap tokens using Jupiter (Best price routing across all Solana DEXs)

Ethereum & EVM Chain Operations:

  • Check native token balances across multiple networks
  • Check ERC-20 token balances
  • Send native tokens (using private key from .env)
  • Send ERC-20 tokens (using private key from .env)
  • Approve ERC-20 token spending (using private key from .env)

Cardano Operations:

  • Get network information and statistics
  • Check address balances and transaction history
  • View UTxOs for an address
  • Explore stake pools and delegation information
  • Get details about native assets
  • View detailed transaction information
  • Get statistics about the current epoch

THORChain Operations:

  • Check RUNE balances
  • Get detailed pool information
  • Get swap quotes between any supported assets
  • Cross-chain swaps via THORChain protocol

UTXO Chain Operations:

  • Bitcoin (BTC)
    • Check address balances
    • View transaction history
    • Validate addresses
    • Get network info and fees
  • Litecoin (LTC)
    • Check address balances
    • View transaction history
    • Validate addresses
    • Get network info and fees
  • Dogecoin (DOGE)
    • Check address balances
    • View transaction history
    • Validate addresses
    • Get network info and fees
  • Bitcoin Cash (BCH)
    • Check address balances
    • View transaction history
    • Validate addresses
    • Get network info and fees

XRP Ledger Operations:

  • Check XRP account balances
  • View transaction history
  • Validate XRP addresses
  • Send XRP to another address
  • Get current XRP Ledger information
  • Check token balances
  • Create trustlines for tokens

TON (The Open Network) Operations:

  • Get TON account balances
  • View transaction history
  • Validate TON addresses
  • Send TON to another address with optional memo/comment
  • Get current TON network information

Supported EVM Networks:

  • Ethereum
  • Base
  • Arbitrum
  • Optimism
  • BSC (Binance Smart Chain)
  • Polygon
  • Avalanche
  • Berachain

Tool Registration

The Web3 MCP server allows you to control which blockchain tools are registered through environment variables:

  • ENABLE_SOLANA_TOOLS: Enable/disable Solana tools
  • ENABLE_ETHEREUM_TOOLS: Enable/disable Ethereum and EVM chain tools
  • ENABLE_BITCOIN_TOOLS: Enable/disable Bitcoin tools
  • ENABLE_LITECOIN_TOOLS: Enable/disable Litecoin tools
  • ENABLE_DOGECOIN_TOOLS: Enable/disable Dogecoin tools
  • ENABLE_BITCOINCASH_TOOLS: Enable/disable Bitcoin Cash tools
  • ENABLE_THORCHAIN_TOOLS: Enable/disable THORChain tools
  • ENABLE_RIPPLE_TOOLS: Enable/disable XRP Ledger tools
  • ENABLE_CARDANO_TOOLS: Enable/disable Cardano tools
  • ENABLE_TON_TOOLS: Enable/disable TON tools

Set these variables to true or false in your .env file to control which tools are available to the server. This allows you to:

  • Reduce startup time by only loading required tools
  • Minimize security surface area by disabling unused chains
  • Customize the server for specific use cases
  • Control resource usage by limiting active connections

Security Notes

  1. Environment Variables: All private keys are stored in the .env file and never exposed in the conversation history
  2. Private Keys: Only use this with test wallets containing small amounts of funds
  3. RPC Endpoints: Custom RPC endpoints can be configured in the .env file for better reliability and rate limits
  4. .env Security: The .env file is automatically ignored by git to prevent accidental exposure of private keys
  5. Tool Registration: Use the tool registration controls to minimize security surface area by only enabling required chains

Development

To modify or extend the tool:

  1. Source code is in the src directory
  2. Chain-specific code in src/chains
  3. Run npm run build after making changes
  4. Use TypeScript for all new code