Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ExpertVagabond/solana-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/expertvagabond/solana-mcp-server/solana)<a href="https://agentmods.dev/mcp/expertvagabond/solana-mcp-server/solana"><img src="https://agentmods.dev/badge/mcp/expertvagabond/solana-mcp-server/solana/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/expertvagabond/solana-mcp-server/solana"><img src="https://agentmods.dev/badge/mcp/expertvagabond/solana-mcp-server/solana.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
solana scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "solana": { "command": "npx", "args": [ "-y", "solana-mcp-server" ], "env": {} } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 10 lines scan A a79948a6f8d1
solana is an MCP server published in the GitHub repository ExpertVagabond/solana-mcp-server (1 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
sui-mcp
Read-only Sui blockchain analytics: 59 tools, protocol-aware tx decoding, no API keys or wallet. Runs locally from the sui-analytics-mcp npm package. Needs 6 environment variables to run.
mcp-solana-ico
MCP server "mcp-solana-ico" as configured in waifuai/mcp-solana-ico. Runs locally from the mcp-solana-ico Python package.
mcp-telegram
MCP server for Telegram userbot — messages, media, reactions, polls & more. Built on GramJS/MTProto. Runs locally from the @overpod/mcp-telegram npm package. Needs 2 environment variables to run.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.0). Needs 6 environment variables to run.
helius
Official Helius MCP Server - Complete Solana blockchain data access for AI assistants. Runs locally from the helius-mcp npm package.
itglue-mcp
MCP server "itglue-mcp" as configured in WYRE-AI/itglue-mcp. Runs in Docker (ghcr.io/wyre-ai/itglue-mcp:v1.16.5). Needs 6 environment variables to run.