🟣🔎 solscan-mcp: A Solscan API MCP Server in Rust

Created By
wowinter13a year ago
An MCP server for querying Solana transactions using natural language with Solscan API
Overview

What is Solscan MCP?

Solscan MCP is a server designed for querying Solana transactions using natural language through the Solscan API. It allows users to interact with Solana blockchain data in a more intuitive way.

How to use Solscan MCP?

To use Solscan MCP, you can send natural language queries to the server, which will then process these queries and return relevant transaction data from the Solana blockchain.

Key features of Solscan MCP?

  • Natural language processing for querying blockchain data
  • Access to various Solscan API endpoints for detailed transaction information
  • Ability to retrieve account details, transaction history, and token information

Use cases of Solscan MCP?

  1. Querying specific transaction details on the Solana blockchain.
  2. Retrieving account balances and transaction history in a user-friendly manner.
  3. Analyzing token transfers and market data through natural language queries.

FAQ from Solscan MCP?

  • Can I query any Solana transaction?

Yes! You can query various types of transactions and account details using natural language.

  • Is there a limit to the number of queries I can make?

Currently, there are no specified limits, but performance may vary based on server load.

  • What programming language is Solscan MCP built with?

Solscan MCP is built using Rust.

Server Config

{
  "mcpServers": {
    "solscan-mcp": {
      "command": "/Users/$username/.cargo/bin/solscan-mcp",
      "args": [],
      "env": {
        "SOLSCAN_API_KEY": "your_solscan_api_key"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wowinter13
Star
18
Language
Rust
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

9 hours ago
Alloy

2 days ago