All servers · Crypto & blockchain
TxWhy
io.github.SUNDRAM07/txwhy · v0.2.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Failed Solana transaction in, working transaction out. Exact cause, rebuilt tx, verifiable repair.
Connect
streamable-http · https://txwhy.vercel.app/api/mcp
claude mcp add --transport http txwhy https://txwhy.vercel.app/api/mcp{
"mcpServers": {
"txwhy": {
"url": "https://txwhy.vercel.app/api/mcp"
}
}
}Tools as reported by the server
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 limits, slippage ondiagnose_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.
Website · JSON · Text for agents · Registry updated 2026-10-08