solscan

solscan-mcp is a Rust-based MCP server that interfaces with the Solscan Pro API to fetch and analyze Solana blockchain data. It provides tools to query token information, account activities, and transaction details, enabling LLMs to reason over live Solana data with the context provided by Solscan. To use it, start the server with the configured command and present prompts to the MCP that reference the available tools documented in TOOLS.md. The server handles API calls to Solscan and returns structured results that can be incorporated into downstream reasoning tasks by your agent or application.

Prerequisites:

• Rust toolchain (install via rustup: https://rustup.rs/)
• Optional: Docker for containerized usage (Docker installation shown below)
• A Solscan Pro API key (obtain from https://solscan.io/apis)

Regular installation (local):

1. Install the Solscan MCP binary: cargo install solscan-mcp
2. Confirm installation path: where solscan-mcp # typically /Users/yourname/.cargo/bin/solscan-mcp
3. Create or update your Claude config with the MCP server entry:

{
  "mcpServers": {
    "solscan-mcp": {
      "command": "/Users/yourname/.cargo/bin/solscan-mcp",
      "args": [],
      "env": {
        "SOLSCAN_API_KEY": "your_solscan_api_key"
      }
    }
  }
}

4. Start using the server by launching the command shown above (adjust path as appropriate).

Docker (WIP):

• Docker usage is marked as Work In Progress in the README. When available, you would typically build or pull a solscan-mcp image and run it with appropriate environment variables including SOLSCAN_API_KEY.
• Example (when available): docker run -e SOLSCAN_API_KEY=your_key -i solscan-mcp-image

Prerequisites recap:

• Rust toolchain installed
• Solscan Pro API key
• Access to update your Claude/agent config with the mcpServers entry

Tips:

• Keep your SOLSCAN_API_KEY secure; do not commit it to version control.
• If you update the binary with cargo install, ensure the path in your config remains correct.
• The server relies on the TOOLS.md documentation for available tools; consult it to understand the precise capabilities (e.g., token lookups, account activity queries, transaction details).
• If you encounter API rate limits or authentication errors, verify that the SOLSCAN_API_KEY is valid and not expired, and consider adding caching or rate-limiting in your prompts where appropriate.