Solscan MCP 🚀

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

What is Solscan MCP?

Solscan MCP is an innovative server that allows users to query Solana transactions using natural language, leveraging the Solscan API for seamless interaction with the Solana blockchain.

How to use Solscan MCP?

To use Solscan MCP, clone the repository, build the project using Rust, and run the server. Once running, you can make natural language queries to retrieve transaction details or account balances.

Key features of Solscan MCP?

  • Natural language queries for Solana transactions.
  • High performance built with Rust.
  • Simple API endpoints for easy integration.
  • Open-source and community-driven contributions.

Use cases of Solscan MCP?

  1. Querying transaction statuses in plain language.
  2. Checking account balances without complex commands.
  3. Integrating with applications for user-friendly blockchain interactions.

FAQ from Solscan MCP?

  • Can I query any Solana transaction?

Yes! You can query any transaction by its ID using natural language.

  • Is Solscan MCP open-source?

Yes! Solscan MCP is open-source and welcomes contributions from the community.

  • What programming language is used?

The project is built using Rust for optimal performance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Valennmg
Star
1
Language
Rust
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago