SolanaFM MCP. Analyze Solana Blocks and Account History Automatically

SolanaFM gives your agent straight access to Solana's ledger data. Forget clicking through a dozen tabs on some bloated web explorer; you just tell your AI client what you need and it pulls the raw, verifiable JSON payload.

You’re checking out blocks, transactions by signature or range, account metadata, and token balances—all without ever leaving your IDE. It turns those deep-dive crypto searches into simple conversation prompts. You get granular control over the entire Solana stack.

Account State and Ownership Details:
When you need to know what an account is, you use get_account_info. This function fetches the current metadata record and the precise state data for any given Solana address, telling you exactly who owns it. If you’re tracking token holdings, you'll rely on get_token_accounts, which returns every single individual token account attached to a specific wallet, listing both the mint details and their corresponding balances.

Tracking Activity Across Addresses:
To see what an address has been up to, you can use get_account_transactions. This compiles a complete list of all transaction signatures that have ever run against that specified wallet address. If you need more than just the signature—if you wanna know exactly what happened in one specific transfer or interaction—you pull the full payload using get_transaction by its unique signature string.

Deep Ledger Analysis (Blocks):
Analyzing the ledger itself requires knowing how to handle time and slots. You can fetch data for a single, specified block slot number using get_block, which gives you all the content and validator info for that exact moment in time. If you need to look at a big chunk of history—say, everything from Slot 100 through Slot 500—you use get_blocks.

This function fetches an entire array of block data covering your defined start-to-end slot range.

How It Works:
Your agent doesn't guess; it executes. You don't write complex RPC calls or filter JSON manually. You simply tell your client, 'Check the metadata for this address,' and it runs get_account_info. If you need to count token holdings, you prompt for that, and it uses get_token_accounts to return a list of mints and balances for every account linked to that wallet.

It’s all about precision. You wanna see the full payload details? Use get_transaction. Wanna see everything attached to an address's history? Call get_account_transactions. If you need to compare accounts, you get their current state via get_account_info and then check their token holdings using get_token_accounts. You can’t mess around with this data; it’s raw blockchain truth.

The system makes the complex web explorer search—the kind that takes like ten clicks just to verify ownership—into a single conversation prompt.