Failed Solana transaction in, working transaction out. Exact cause, rebuilt tx, verifiable repair.
Connect Remote server
claude mcp add --transport http txwhy https://txwhy.vercel.app/api/mcp
{
"mcpServers": {
"txwhy": {
"url": "https://txwhy.vercel.app/api/mcp"
}
}
}
{
"servers": {
"txwhy": {
"type": "http",
"url": "https://txwhy.vercel.app/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://txwhy.vercel.app/api/mcp
Tools 3 found in our last check
repair_transactionGive it a Solana transaction that failed, or one you are about to send. It finds the cause and returns a rebuilt UNSIGNED transaction that has been simulated against live mainnet state to prove it passes. Fixes expired blockhashes, compute-unit limits, priority fees, loaded-data…
diagnose_transactionExplains why a transaction that landed on mainnet failed: the exact failing instruction in the call tree, the named error, its cause, and how to fix it. Read-only and fast. Use repair_transaction when you want a working transaction back.
explain_errorLooks up what a custom program error code means for a given program, using 1,800+ named errors from major Solana programs plus the runtime's own errors. Use it when you only have a code such as 6001 or 0x1771 from a simulation or an RPC response.
Details
| Endpoint | https://txwhy.vercel.app/api/mcp (Streamable HTTP) |
| First published | 8 Oct 2026 |
| Last updated | 8 Oct 2026 |
| Registry name | io.github.SUNDRAM07/txwhy |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
