mcpbeat Sign in

TxWhy MCP Server

by sundram07 Your server? Claim it
not responding

TxWhy is listed as active in the registry but did not answer our last check. It exposes 3 tools.

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

Uptime history 31 days of history · worst day 4%
31 days agonow
23.1%
Uptime 24h
21 of 91 checks
3
Tools
read from the server
502 ms
Response time
average over 24h
open, no key
Access
streamable-http

TxWhy does not always answer

Over the last week it answered 28.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add txwhy --transport http https://txwhy.vercel.app/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://txwhy.vercel.app/api/mcp
~/.codex/config.toml
[mcp_servers.txwhy]
url = "https://txwhy.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "txwhy": {
      "url": "https://txwhy.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "txwhy": {
      "type": "http",
      "url": "https://txwhy.vercel.app/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

diagnose
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
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.
repair
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 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.

Endpoints

URLTransportStateLatencyChecked
https://txwhy.vercel.app/api/mcp streamable-http answering 50 ms 11 min ago

Alternatives to TxWhy

same job, measured the same way
A202
by a202-protocol

Verifiable agreements for agent-led commerce: mandates, obligations, evidence, transaction records.

local only
MCP Prepare Transactions
by cryptoapis-io

MCP server for building unsigned transactions on EVM, Tezos, Solana, Kaspa, XRP, UTXO, Tron

74 installs/wk local only
Agentseal
by joeybrar

Verifiable action logs for AI agents. Every action is recorded in a SHA-256 hash chain.

42 installs/wk local only
SciWeave
by desci-labs

AI research grounded in 300M scientific works — every citation a verifiable DOI.

answering
AgentWeb (agentweb.us)
by agentweb

The action index for the web: real sites as callable, verified actions for AI agents.

answering
Witnessed
by barrypmarshall

Signed, reproducible market facts for agents, verifiable without trust.

66 installs/wk local only
DLL Execution
by dllio

Free read-only Base Mainnet transaction Preflight and Verification; no signing or custody.

2 tools answering
Ergonia Works
by ergonia

Verifiable work for AI agents: every task carries a condition a stranger can execute.

6 tools answering

TxWhy — questions

Answers built from our own checks of this server.

What can TxWhy do?
It exposes 3 tools, read directly from the server on our last check. Among them: diagnose_transaction, explain_error, repair_transaction. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is TxWhy working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 21 of 91 checks got a reply (23.1%), average response time 502 ms. The bar chart above shows every period we have measured.
The registry lists TxWhy as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect TxWhy?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does TxWhy need an API key?
No. TxWhy completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is TxWhy?
It answers our handshake in 502 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.