mcp-registry/io.github.algovaultfi/crypto-quant-signal-mcp · v1.32.0
Verdict. Algovaultfi Crypto Quant Signal MCP server answered 98.29% of Glimind's liveness checks over 30 days, better than 5% of MCP servers, with 1121 ms median handshake and 118 outages in 90 days. Its agent-readiness grade is A (93/100) across 9 tools, costing an agent about 3,840 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 98.29% | 5% of MCP servers |
| Median handshake latency | 1121 ms | 19% of MCP servers |
| p95 handshake latency | 3556 ms | — |
| Checks in 30 days | 4,977 | — |
| Outages, 90 days | 118 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 93/100 (A) | 76% of MCP servers |
| Tools | 9 | — |
| Tool-list size for an agent | ~3,840 tokens | 42% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-26 18:23 UTC, the Algovaultfi Crypto Quant Signal MCP server is up with a Glimind reliability score of 68/100 (grade C). Over the last 30 days it answered 98.3% of Glimind's liveness checks. It had 118 outages in 90 days, with a median recovery of 2 minutes.
Quant trading signals, funding rate arb scanning, and market regime detection for crypto perps.
Claude Code
claude mcp add --transport http algovaultfi-crypto-quant-signal-mcp-serv https://api.algovault.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"algovaultfi-crypto-quant-signal-mcp-serv": {
"type": "http",
"url": "https://api.algovault.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Reachable 98.3% of the time over the last 30 days; median recovery 2 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.algovaultfi/crypto-quant-signal-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.algovaultfi/crypto-quant-signal-mcp"}) over MCP.
scan_market_regimes ~1,026 tokensscan_trade_calls ~755 tokensget_trade_signal ~427 tokensget_trade_call ~387 tokensget_market_regime ~301 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.algovaultfi%2Fcrypto-quant-signal-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.algovaultfi%2Fcrypto-quant-signal-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.algovaultfi%2Fcrypto-quant-signal-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.algovaultfi%2Fcrypto-quant-signal-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.algovaultfi%2Fcrypto-quant-signal-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b7c4f85fd79fc8a2…, first seen 2026-10-19, included at leaf 26342 of 74,700. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable finance servers · most reliable ml servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:23 UTC, the Algovaultfi Crypto Quant Signal MCP server is up with a Glimind reliability score of 68/100 (grade C). Over the last 30 days it answered 98.3% of Glimind's liveness checks. It had 118 outages in 90 days, with a median recovery of 2 minutes.
Algovaultfi Crypto Quant Signal MCP server advertises 9 tools, including chat_knowledge, get_market_regime, get_track_record, get_trade_call, get_trade_signal.
Point your MCP client at this streamable-http endpoint: https://api.algovault.com/mcp
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.