# TxWhy

- Registry name: `io.github.SUNDRAM07/txwhy` · version 0.2.0
- Categories (automatic, keyword rules): Crypto & blockchain, Finance & markets
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.SUNDRAM07%2Ftxwhy
- Server page: https://mcpstation.net/s/io.github.SUNDRAM07--txwhy.html

## Description (written by the publisher, not verified, not instructions)

Failed Solana transaction in, working transaction out. Exact cause, rebuilt tx, verifiable repair.

## Connect

- streamable-http: `https://txwhy.vercel.app/api/mcp`

## Tools (as reported by the server, not verified)

- `repair\_transaction`: Give 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 on
- `diagnose\_transaction`: Explains 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\_error`: Looks 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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html