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/biccsdev/solana_debug_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/mcp/biccsdev/solana_debug_mcp/solana-debug-mcp)<a href="https://agentmods.dev/mcp/biccsdev/solana_debug_mcp/solana-debug-mcp"><img src="https://agentmods.dev/badge/mcp/biccsdev/solana_debug_mcp/solana-debug-mcp/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/biccsdev/solana_debug_mcp/solana-debug-mcp"><img src="https://agentmods.dev/badge/mcp/biccsdev/solana_debug_mcp/solana-debug-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
solana-debug-mcp 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 1mo 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-debug-mcp": { "command": "npx", "args": [ "-y", "solana-debug-mcp" ] } }
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.
- 1mo ago First seen · 9 lines scan A 5cecbee64d25
solana-debug-mcp is an MCP server published in the GitHub repository biccsdev/solana_debug_mcp (2 stars, last pushed 4mo 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
x402-doctor
Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it. Remote server at x402-doctor.tsharpe.workers.dev.
anchor-debug
CLI tool that makes Anchor program failures understandable — translates hex error codes, visualizes CPI call stacks, and resolves account names from IDL. Runs locally from the anchor-debug npm package.
sap-mcp
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments. Runs locally from the @oobe-protocol-labs/sap-mcp-server npm package. Needs 2 environment variables to run.
payql
MCP server "payql" as configured in PaulieB14/payql. Runs /ABSOLUTE/PATH/TO/payql/dist/index.js with node. Needs 4 environment variables to run.
dexjup-mcp
MCP server combining DEX Screener market data with Jupiter (Solana) quotes and gated swap execution. Runs locally from the dexjup-mcp npm package.
dbgprobe-mcp-server
Debug probe Model Context Protocol server for AI agents and developer tooling. Runs locally from the dbgprobe-mcp-server Python package. Needs 9 environment variables to run.