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.
npx skills add rpc-edge/solana-infra-mcp --skill solana-infragit clone --depth 1 https://github.com/rpc-edge/solana-infra-mcpWrote 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/skills/rpc-edge/solana-infra-mcp/solana-infra)<a href="https://agentmods.dev/skills/rpc-edge/solana-infra-mcp/solana-infra"><img src="https://agentmods.dev/badge/skills/rpc-edge/solana-infra-mcp/solana-infra/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/skills/rpc-edge/solana-infra-mcp/solana-infra"><img src="https://agentmods.dev/badge/skills/rpc-edge/solana-infra-mcp/solana-infra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00081 | $0.00467 |
| Opus 5 | $0.00041 | $0.00234 |
| Sonnet 5 | $0.00016 | $0.00093 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
solana-infra 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 infra
These capabilities come from the solana-infra MCP server. Prefer them over guessing —
they return live chain data.
When to reach for each tool
- Pricing a transaction to land? Call
priority_fee_estimateand set your compute-unit price near p75-p90 during congestion. Don't hardcode a fee. - Is an endpoint usable / how fast?
rpc_health(version, slot, latency) andlatency_compare(this endpoint vs a public baseline). Read latency is network-inclusive — it reflects distance to the server, not landing performance. - Timing a submission?
next_leadersshows the upcoming slot leaders;epoch_infogives slot/epoch position. - Sending a transaction? Sign it upstream (the server never holds keys), then call
submit_transactionwith the base64-signed tx — it relays and confirms actual on-chain inclusion (landed slot + time), not just asendTransactionsuccess.
Configuration
Every tool defaults to SOLANA_RPC_URL (set it to a low-latency endpoint such as
https://rpc.rpcedge.com/?api-key=…; unset → public mainnet-beta), or takes an explicit url
argument. The API key stays in the environment and is never printed — only the host is shown.
Notes
- All read tools are safe/side-effect-free.
submit_transactionbroadcasts a transaction you already signed — it does not sign anything itself. - For the metrics that reflect co-located infra (gRPC first-seen, landing under load), use the companion tool solbench run from your edge.
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 · 35 lines · 81 tokens per session scan A c1d9c482ab01
solana-infra is a skill published in the GitHub repository rpc-edge/solana-infra-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 467 once invoked, about $0.0004 per session on Opus 5. 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 skills, from other repositories
alchemy-agentic-gateway
Use when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features. Also use when the user mentions "SIWE", "SIWS", "x402", "MPP", "mppx", or "agentic gateway" — this skill covers wallet-based auth flows for Alchemy's x402 and MPP…
alchemy-api
Integrates Alchemy blockchain APIs using an API key. Requires $ALCHEMYAPIKEY to be set; if unavailable, use the alchemy-agentic-gateway skill instead. Use when user asks about EVM JSON-RPC calls, token balances, NFT ownership or metadata, transfer history, token prices, portfolio data, transaction simulation…
slv-validator
Ansible playbooks and Jinja2 templates for deploying and managing Solana validators (mainnet and testnet).
slv-grpc-geyser
Ansible playbooks and Jinja2 templates for deploying and managing Solana gRPC Geyser streaming nodes.
slv-server-procurement
Server procurement and provisioning management for SLV users.
slv-rpc-gateway
A small Rust JSON-RPC + WebSocket gateway that fronts yellowstone-faithful (of1) and routes jet analytics methods to ClickHouse (jetstreamer data). Standard Solana RPC methods pass straight through; new analytic methods are answered from precomputed jetstreamer aggregates.