Remote MCP · Endpoint
Quay MCP server
No. Quay answered an MCP handshake 28 minutes ago.
UpLast checked 28 minutes ago
Server URL
https://tron-agent-tools.sharkweather1.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.quay21/quay
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 86 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Pay-per-call TRON fee, payment, and address checks. Agents pay USDT or USDC.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 28 minutes ago | Handshake completed | 86 ms |
| 10 days ago | Handshake completed | 107 ms |
| 11 days ago | Handshake completed | 315 ms |
| 11 days ago | Handshake completed | 117 ms |
| 13 days ago | Handshake completed | 92 ms |
| 14 days ago | Handshake completed | 75 ms |
| 15 days ago | Handshake completed | 108 ms |
| 16 days ago | Handshake completed | 87 ms |
| 17 days ago | Handshake completed | 89 ms |
| 19 days ago | Handshake completed | 616 ms |
| 21 days ago | Handshake completed | 71 ms |
| 24 days ago | Handshake completed | 271 ms |
| 26 days ago | Handshake completed | 77 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.
Listing data comes from the official MCP registry. Glide is not affiliated with Quay and makes no claim about it beyond what these checks measured.