Svm MCP Server

If you already use Svm MCP, the svm mcp mcp server is the piece that lets your assistant work with it directly. MCP server for SVM based projects integration.

What the server does

A Model Context Protocol (MCP) server that integrates Claude AI with SOON and other SVM-based blockchains. The server provides tools for checking balances, fetching recent transactions, and viewing token holdings on SOON's testnet and mainnet, for account balances, transactions, and token holdings.

This MCP server is designed to connect Claude with the SOON ecosystem, allowing it to: - Query wallet balances on testnet and mainnet - Fetch the most recent transactions for an address - Check token holdings for any account

• Get Balances — Fetch native token balances for any address on SOON testnet or mainnet
• Get Last Transaction — Retrieve the most recent transaction for an address
• Get Token Accounts — List all token accounts owned by an address

Installation

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

Credentials and setup notes

Configuration is passed through the environment: YOUR_TESTNET_RPC_URL, YOUR_MAINNET_RPC_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js (v16+) - NPM or Bun package manager - Claude Desktop (for local testing)

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by rkmonarch; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.