TxWhy

io.github.SUNDRAM07v0.2.0Updated Oct 8, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsFinance

Overview

AI-generated overview

A remote MCP endpoint that diagnoses failed Solana transactions and returns the cause plus a rebuilt, verifiable transaction.

What it does
TxWhy accepts a failed Solana transaction and reports the exact cause of the failure. It then rebuilds the transaction and returns a repaired version that can be verified. The registry description frames the flow as failed transaction in, working transaction out.
When to use it
Useful when a Solana transaction fails and you need to know why before retrying, or when you want an assistant to produce a corrected transaction rather than guess at the error. It fits Solana development and debugging workflows.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the provider's hosted endpoint. No packages, environment variables, headers, or authentication are declared.
Before you install
The service receives the contents of your failed transaction, which may include account addresses and other on-chain details, and it sends that data to a third-party endpoint. The rebuilt transaction should be reviewed before it is signed or submitted, since signing and broadcasting are not described here.

Installation

In SourceWeft

  1. Open TxWhy in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "txwhy": {
      "type": "http",
      "url": "https://txwhy.vercel.app/api/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.2.0LatestOct 8, 2026