Remote MCP · Endpoint
TronSave MCP server
No. TronSave answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.tronsave.io/testnet/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.tronsave/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 801 ms
- Tools exposed
- 53 tools
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- Buy, sell and extend TRON Energy/Bandwidth on the TronSave market. Quotes need no login.
- Website
- https://docs.tronsave.io/
- Repository
- https://github.com/tronsave/tronsave-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 801 ms |
| 9 days ago | Handshake completed | 590 ms |
| 10 days ago | Handshake completed | 672 ms |
| 11 days ago | Handshake completed | 544 ms |
| 12 days ago | Handshake completed | 632 ms |
| 14 days ago | Handshake completed | 558 ms |
| 14 days ago | Handshake completed | 552 ms |
| 15 days ago | Handshake completed | 567 ms |
| 17 days ago | Handshake completed | 581 ms |
| 19 days ago | Handshake completed | 586 ms |
| 21 days ago | Handshake completed | 547 ms |
| 24 days ago | Handshake completed | 607 ms |
| 26 days ago | Handshake completed | 538 ms |
| 28 days ago | Handshake completed | 530 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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.
Listing data comes from the official MCP registry. Glide is not affiliated with TronSave and makes no claim about it beyond what these checks measured.