AlgoVault — Crypto Quant Trade Calls
io-github-algovaultfi-crypto-quant-signal-mcp declares 9 capabilities across 9 tools, with 1 critical issue.
Issues
9 of 9 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
9 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
get_trade_call | read |
declared |
get_trade_signal | read |
declared |
get_market_regime | read |
declared |
scan_funding_arb | read |
declared |
scan_trade_calls | read |
declared |
chat_knowledge | read |
declared |
search_knowledge | read |
declared |
get_track_record | read |
declared |
scan_market_regimes | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 14 | tools/list on https://api.algovault.com/mcp, published in the official MCP registry as io.github.AlgoVaultFi/crypto-quant-signal-mcp 1.31.1 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.