universal-crypto

Universal Crypto MCP is a server that exposes a suite of crypto-focused tools and data providers via the MCP framework. It enables AI agents and automated workflows to interact with multiple blockchain networks (EVM-compatible chains and Solana) through a consistent MCP interface, offering capabilities such as on-chain data queries, DeFi interactions, wallet management, and market data access. Users can deploy the MCP using Node.js tooling and then query or drive tools programmatically in order to fetch prices, monitor liquidity, execute trades, or retrieve historical blockchain events. The server is designed to be compatible with MCP clients, enabling agents to discover tools, invoke them, and interpret results within an autonomous workflow or chat-like session.

Prerequisites:

• Node.js 18+ and npm installed on your system
• Basic familiarity with running MCP servers via npx or your preferred package manager

1. Install prerequisites:

• Install Node.js from https://nodejs.org/ (ensure node -v prints 18 or newer)

2. Run the MCP server directly with npx (no local install required):

• Command: npx -y @nirholas/universal-crypto-mcp

3. Alternative: Install locally and run from your project (optional):

• Create a project directory and initialize: mkdir universal-crypto-mcp && cd universal-crypto-mcp npm init -y
• Install the MCP package locally (as a dev/dependency if preferred): npm install @nirholas/universal-crypto-mcp
• Run the server from node_modules (if the package exposes a CLI): npx @nirholas/universal-crypto-mcp

4. Verify installation:

• Ensure the MCP server starts without errors and listen on the expected channel/port as per your MCP client configuration.

Notes:

• The server leverages the MCP ecosystem to expose 380+ tools and multi-chain support (EVM + Solana). Ensure your environment has access to required network resources (e.g., RPC endpoints) if tools need external calls.
• If you plan to run behind proxies or within restricted networks, configure environment variables or CLI flags for network access as needed.
• When integrating with agents, you can rely on tool discovery to surface available capabilities and their input/output schemas. Consider caching frequently used data (prices, liquidity) to reduce latency.
• If you encounter permission or caching issues, try clearing npm/pnpm/yarn caches or running with clean environment variables. Review MCP registry docs for specific tool version requirements.
• Although the MCP server is designed to be portable, some tools may require API keys or access tokens; store these securely using your environment variable management strategy.