TxWhy
io.github.SUNDRAM07/txwhyVersion 0.2.0Failed Solana transaction in, working transaction out. Exact cause, rebuilt tx, verifiable repair.
Status
Responds82 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:42 UTC
- Latency
- 82 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://txwhy.vercel.app/api/mcpResponds82 msNo sign-in
Claude Code
claude mcp add --transport http txwhy https://txwhy.vercel.app/api/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: txwhy
Remote MCP server URL: https://txwhy.vercel.app/api/mcpCursor
{
"mcpServers": {
"txwhy": {
"url": "https://txwhy.vercel.app/api/mcp"
}
}
}VS Code
code --add-mcp '{"name":"txwhy","type":"http","url":"https://txwhy.vercel.app/api/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
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. | Not declared | Not declared | Not declared | Not declared |
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. | Not declared | Not declared | Not declared | Not declared |
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 on plain Jupiter swaps (fresh quote, same tolerance), and slippage on direct Pump.fun, PumpSwap, Raydium AMM v4, Meteora DBC and Meteora DAMM v2 swaps (only the limit moves, never more than 25% against the user). Handles legacy, v0 and version 1 (SIMD-0385) transactions and durable nonces. When the failure cannot be fixed by rebuilding (not enough funds, a private program's own error), it says so and explains why instead of returning something that would fail again. Pass exactly one of `transaction` or `signature`. Sign the returned transaction with your own key and send it within about 60 seconds. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Oct 8, 2026
- Updated
- Oct 8, 2026
- Repository
- Not given
- Categories
- Uncategorized
- GDPR
- Not declared