Remote MCP · Endpoint

TxWhy MCP server

No. TxWhy answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://txwhy.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.SUNDRAM07/txwhy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
165 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Failed Solana transaction in, working transaction out. Exact cause, rebuilt tx, verifiable repair.
Website
https://txwhy.vercel.app/
Listing
From the official MCP registry (active).
Recent checks of TxWhy
CheckedResultHandshake
8 hours agoHandshake completed165 ms
13 hours agoHandshake completed160 ms
2 days agoHandshake completed160 ms
4 days agoHandshake completed1.19 s
7 days agoHandshake completed214 ms
9 days agoHandshake completed170 ms
11 days agoHandshake completed159 ms
14 days agoHandshake completed1.26 s
16 days agoHandshake completed339 ms
18 days agoHandshake completed162 ms
20 days agoHandshake completed180 ms
21 days agoHandshake completed285 ms
23 days agoHandshake completed164 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with TxWhy and makes no claim about it beyond what these checks measured.