Remote MCP · Endpoint
Sato Hub: Build Onchain & Crypto Agents MCP server
No. Sato Hub: Build Onchain & Crypto Agents answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://satohub.ai/api/mcp
The last check completed an MCP handshake.
- Registry name
- ai.satohub/onchain-agents
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.60 s
- Tools exposed
- 48 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Build any crypto agent: x402, ERC-8004, wallets. Does a server take your key? Hosted? Maintained?
- Website
- https://satohub.ai/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.60 s |
| 1 day ago | Handshake completed | 217 ms |
| 3 days ago | Handshake completed | 248 ms |
| 3 days ago | Handshake completed | 159 ms |
| 4 days ago | Handshake completed | 114 ms |
| 5 days ago | Handshake completed | 166 ms |
| 7 days ago | Handshake completed | 1.00 s |
| 10 days ago | Handshake completed | 288 ms |
| 12 days ago | Handshake completed | 277 ms |
| 14 days ago | Handshake completed | 139 ms |
| 17 days ago | Handshake completed | 142 ms |
| 19 days ago | Handshake completed | 353 ms |
| 21 days ago | Handshake completed | 1.39 s |
| 23 days ago | Handshake completed | 232 ms |
| 25 days ago | Handshake completed | 303 ms |
| 26 days ago | Handshake completed | 119 ms |
| 28 days ago | Handshake completed | 170 ms |
| 29 days ago | Handshake completed | 228 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Sato Hub: Build Onchain & Crypto Agents and makes no claim about it beyond what these checks measured.