🟣🔎 Solscan MCP Server

🟣🔎 Solscan MCP server exists for a simple reason — assistants are far more useful when they can act on 🟣🔎 Solscan directly instead of describing what you should do. An MCP server for querying Solana transactions using natural language with Solscan API.

What you get

A Model Context Protocol (MCP) server for interacting with the Solscan Pro API for Solana blockchain data. This server provides tools to query token information, account activities, and transaction details on the Solana blockchain via Large Language Models.

What the assistant can call

Once 🟣🔎 Solscan is connected, these are the calls the assistant has available:

• Regular — where solscan-mcp # -> /Users/$username/.cargo/bin/solscan-mcp

Configuration and credentials

You will need one environment variable: SOLSCAN_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. 🟣🔎 Solscan's toolset — Regular — is a fair guide to whether it matches your workflow. It is maintained by wowinter13; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the 🟣🔎 solscan mcp server does with a few real requests.