Remote MCP · Endpoint
AlgoVault — Crypto Quant Trade Calls MCP server
No. AlgoVault — Crypto Quant Trade Calls answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.algovault.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.AlgoVaultFi/crypto-quant-signal-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 404 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- The Brain Layer for AI Trading Agents — quant calls + cross-venue arb across perp venues via MCP.
- Website
- https://algovault.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 404 ms |
| 1 day ago | Handshake completed | 423 ms |
| 2 days ago | Handshake completed | 502 ms |
| 3 days ago | Handshake completed | 425 ms |
| 4 days ago | Handshake completed | 436 ms |
| 5 days ago | Handshake completed | 407 ms |
| 6 days ago | Handshake completed | 412 ms |
| 9 days ago | Handshake completed | 559 ms |
| 12 days ago | Handshake completed | 446 ms |
| 14 days ago | Handshake completed | 420 ms |
| 16 days ago | Handshake completed | 603 ms |
| 18 days ago | Handshake completed | 408 ms |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Handshake completed | 443 ms |
| 24 days ago | Handshake completed | 480 ms |
| 26 days ago | Handshake completed | 226 ms |
| 27 days ago | Handshake completed | 413 ms |
| 28 days ago | Handshake completed | 391 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 AlgoVault — Crypto Quant Trade Calls and makes no claim about it beyond what these checks measured.