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/GeckoVision/gecko-surfWrote 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/geckovision/gecko-surf/txline_sharp_agent-solana-dev)<a href="https://agentmods.dev/mcp/geckovision/gecko-surf/txline_sharp_agent-solana-dev"><img src="https://agentmods.dev/badge/mcp/geckovision/gecko-surf/txline_sharp_agent-solana-dev.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
solana-dev 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 8d 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-dev": {
"type": "http",
"url": "https://mcp.solana.com/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 8d ago First seen · 6 lines scan A 49eff50a3a27
solana-dev is an MCP server published in the GitHub repository GeckoVision/gecko-surf (6 stars, last pushed today), licensed Apache-2.0. 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
solana-security-standard
MCP server for the Solana Security Standard (SOL-0XX): scan Solana/Anchor Rust and serve the rules to any MCP client (Cline, Copilot, Cursor, Claude, Windsurf). Runs locally from the @jelleo/solana-security-mcp npm package.
solana-security-mcp
Scan Solana/Anchor code against the Solana Security Standard and serve the ruleset to MCP clients. Runs locally from the @jelleo/solana-security-mcp npm package.
llmwiki-serve
Serve existing Markdown, Obsidian-style, or LLMWiki folders as cited agent-readable context. Runs locally from the llmwiki-serve Python package.
gittr-mcp
MCP server "gittr-mcp" as configured in arbadacarbaYK/gittr-mcp. Runs locally from the gittr-mcp npm package. Needs 3 environment variables to run.
agentic-wallet-guardian-v3
Decision infrastructure for autonomous AI agents: evaluates a proposed blockchain action intent and returns an explainable ALLOW/WARN/BLOCK decision before execution, signed as a verifiable OAA token. Runs locally from the agentic-wallet-guardian-mcp Python package.
agentfund
Fundraising tools for AI agents on Solana: create campaigns, donate via x402, check reputation. Runs locally from the @agentfund/mcp npm package. Needs 2 environment variables to run.