TxWhy
io.github.SUNDRAM07/txwhy · v0.2.0
Failed Solana transaction in, working transaction out. Exact cause, rebuilt tx, verifiable repair.
MCPremoteno credentialsCrypto
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 79/100
What it does: 3 tools · 1 read, 0 write · Crypto, Developer tools
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +6
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: 0
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://txwhy.vercel.app/api/mcpTools
3 tools listed at 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 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.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.SUNDRAM07/txwhy)