Provides tools for debugging Solana Anchor program failures, including parsing logs, fetching transaction details, and looking up error codes.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@anchor-debug parse logs from my failed anchor test"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CLI tool that makes Anchor program failures understandable.
When your Anchor test fails with custom program error: 0x1770, anchor-debug tells you exactly what broke, where, and why.
Without anchor-debug:
Error: failed to send transaction: Transaction simulation failed: Error processing Instruction 0: custom program error: 0x7d2With anchor-debug:
✗ Transaction failed
Error: ConstraintHasOne
Code: 0x7d2 (2002)
Msg: A has_one constraint was violated — account field does not match expected value
Program: my_program (9uvbWC...)
CPI call stack:
└─ ✗ my_program (9uvbWC...) ← failed here
Error: A has_one constraint was violated — account field does not match expected value
└─ ✓ TokenkegQfeZy... (Token Program)
└─ ✗ my_program::validate_authority ← failed hereRelated MCP server: Solana MCP Demo
npm install -g anchor-debug
# or use directly with npx
npx anchor-debug --helpanchor test 2>&1 | npx anchor-debuganchor-debug reads stdin, finds the failure, and prints a human-readable error. If the test succeeds, output is passed through unchanged.
npx anchor-debug tx <SIGNATURE> --cluster devnet
npx anchor-debug tx <SIGNATURE> --cluster mainnet-beta
npx anchor-debug tx <SIGNATURE> --cluster http://localhost:8899Fetches the transaction from the RPC, extracts its logs, and formats the error.
npx anchor-debug test
npx anchor-debug test --skip-buildRuns anchor test for you and prints the parsed error on failure.
Flag | Description |
| Also show raw log lines |
| Show all program log messages |
| Cluster or RPC URL (tx command) |
| Pass --skip-build to anchor test |
Log parser — reads Solana program logs line-by-line using a regex state machine
Error database — 60+ Anchor framework errors mapped by hex code (both new 0x7d0+ and legacy 0x1770+ ranges)
CPI tracer — rebuilds the full Program invoke [N] call tree and marks the innermost failing invocation
IDL resolver — reads Anchor.toml and target/idl/*.json to show program names instead of pubkeys
Range | Source |
| Instruction errors |
| IDL errors |
| Constraint errors (Anchor ≥ 0.24) |
| Account errors |
| State errors |
| Legacy constraint errors (Anchor < 0.24) |
anchor-debug works as an MCP server, giving AI coding agents (Claude Code, Cursor, etc.) structured access to Solana error data.
Add to .mcp.json in your project:
{
"mcpServers": {
"anchor-debug": {
"command": "npx",
"args": ["anchor-debug", "mcp"]
}
}
}Or globally in ~/.claude/mcp.json.
Available tools:
Tool | What it does |
| Takes raw log lines → structured error + CPI stack |
| Takes signature + cluster → fetches and parses |
| Takes hex code → error name + message |
Example agent response after calling parse_logs:
{
"failed": true,
"error": {
"name": "ConstraintHasOne",
"code": 2002,
"hex": "0x7d2",
"message": "A has_one constraint was violated — account field does not match expected value",
"category": "constraint"
},
"failedProgram": "my_program",
"failedNode": {
"program": "my_program",
"depth": 2,
"errorMessage": "A has_one constraint was violated"
},
"cpiStack": [...]
}Instead of reasoning about 0x1770, the agent immediately knows what failed and can fix it in one shot.
import { parseLogsFromString, formatResult } from "anchor-debug";
const logs = [
"Program MyProg invoke [1]",
"Program MyProg failed: custom program error: 0x7d2",
];
const parsed = parseLogsFromString(logs.join("\n"));
console.log(formatResult(parsed));M1 — npm package, log parser, Anchor error database
M2 — CPI call stack visualizer, IDL integration
M3 — VS Code extension (inline hints)
MIT
This server cannot be deployed
Solana address risk grades and token scans for AI agents. Pay-per-call via x402 (USDC on Base).
Wallet-signed Solana RPC for AI agents. No API keys, LLM-safe amounts, pay-per-call in SOL.
RiskDataApi — Solana token risk scoring for AI agents. Safety score, insider clusters, honeypot.
Solana token safety for AI agents — rug-pull, honeypot & Token-2022 trap detection before you buy.
