AlgoVault — Crypto Quant Trade Calls
REMOTE · API.ALGOVAULT.COM · 2 COMPONENTS
The Brain Layer for AI Trading Agents — quant calls + cross-venue arb across perp venues via MCP.
Available components
Last scanned (7 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2867 tokens (~179/item across 16 items; 10 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- “pre_trade_check” reworded the description of “rules” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 2 Nov 26 0
- Resource “algovault-knowledge-v1.32.0” was removed ▼ functional
- New resource “algovault-knowledge-v1.33.0” functional
- Server version: 1.32.0 → 1.33.0 functional
- 1 Nov 26 −1
- Tool “pre_trade_check” rewrote its description, which is the text the model reads security
- “pre_trade_check” added an optional parameter “orderType” cosmetic
- “pre_trade_check” added an optional parameter “leverage” cosmetic
- “pre_trade_check” added an optional parameter “equityUsd” cosmetic
- “pre_trade_check” added an optional parameter “rules” cosmetic
- “pre_trade_check” added an optional parameter “stopPct” cosmetic
- “pre_trade_check” added an optional parameter “targetPct” cosmetic
- 31 Oct 26 0
- New tool “pre_trade_check” functional
- 24 Oct 26 0
- Resource “algovault-knowledge-v1.31.1” was removed ▼ functional
- New resource “algovault-knowledge-v1.32.0” functional
- Server version: 1.31.1 → 1.32.0 functional
- 20 Oct 26 0
- Schema quality: 135 → 168 ▼ functional
- New tool “scan_market_regimes” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.algovault.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=algovault.com | CN=YE2,O=Let's Encrypt,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6600a84c4027043b0c6d83f799e0859c669 |
| SANs: *.algovault.com, algovault.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.algovault.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| algovault.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://cdn.tailwindcss.com https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://algovault.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https:; connect-src 'self' https://api.algovault.com https://plausible.algovault.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.algovault.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.algovault.com/mcp | HTTPS enforced | 308 | https://api.algovault.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
chat_knowledge ~148
Returns a synthesized natural-language answer with citations, grounded in the AlgoVault knowledge bundle (every MCP tool description, response shape, integration tutorial, and code example). Use when you need an explanation, code pattern, or how-to; for raw ranked snippets without LLM synthesis use search_knowledge (faster, no quota cost). Read-only: calls an LLM, no other side effects. Quota: Free 10/month, Starter 50, Pro 200, Enterprise 2000.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Optional model override (default claude-haiku-4-5-20251001). |
| question | string | yes | Natural-language question (5-500 chars). |
No output schema declared.
No examples provided.
get_market_regime ~162
Returns the market regime — TRENDING_UP TRENDING_DOWN RANGING VOLATILE — with confidence and a strategy hint, for one crypto perpetual futures. Composite verdict: trend ranging + cross-venue funding rate. Read-only, live exchange APIs. Verified track record: get_track_record or performance://signal-performance; on-chain verified merkle anchor.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Base asset crypto signal, e.g. BTC ETH SOL signal. Crypto quant regime. |
| exchange | string | – | Crypto venue, e.g. Binance Bybit OKX Bitget Hyperliquid. Multi-exchange. |
| timeframe | string | – | Candle timeframe, e.g. 1h 4h 1d. Buy sell hold AI trading signal context. |
No output schema declared.
No examples provided.
get_track_record ~113
Returns the AlgoVault track record — aggregated PFE win rates by call type, timeframe and asset tier, plus the evaluation methodology and window. The same verified aggregate the performance://signal-performance resource serves, callable from harnesses that bridge tools only. Defaults to the compact aggregate; use include for the per-asset, per-venue or recent-signal breakdowns. Read-only, no side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | Optional extra sections: byAsset, byExchange, recentSignals. Omit for compact. |
No output schema declared.
No examples provided.
get_trade_call ~209
Returns a composite verdict — BUY SELL HOLD trade call with confidence and market regime — for one crypto or tokenized-stock perpetual futures. One asset only; whole-market scan: scan_trade_calls. Read-only: live exchange APIs, no orders. Verified track record: get_track_record or performance://signal-performance; on-chain verified merkle anchor.
| Name | Type | Req | Description |
|---|---|---|---|
| assetClass | string | – | Force engine: 'perp' or 'equity'. Cross-venue multi-exchange AI trading signal. |
| coin | string | yes | Base asset, e.g. BTC ETH SOL signal, or a US stock/ETF ticker (no USDT). |
| exchange | string | – | Crypto venue (default Binance), e.g. Binance Bybit OKX Bitget Hyperliquid. |
| includeReasoning | boolean | – | Include reasoning: trend ranging crypto signal and market regime drivers. |
| timeframe | string | – | Candle timeframe, 1m to 1d. Default 15m. Crypto quant intraday horizon. |
No output schema declared.
No examples provided.
get_trade_signal ~239
Returns a composite verdict — BUY SELL HOLD trade call with confidence and market regime — for one crypto or tokenized-stock perpetual futures. One asset only; whole-market scan: scan_trade_calls. Read-only: live exchange APIs, no orders. Verified track record: get_track_record or performance://signal-performance; on-chain verified merkle anchor. [ALIAS] This tool is an alias of get_trade_call — same behavior, kept for backward compatibility. Prefer get_trade_call for new integrations.
| Name | Type | Req | Description |
|---|---|---|---|
| assetClass | string | – | Force engine: 'perp' or 'equity'. Cross-venue multi-exchange AI trading signal. |
| coin | string | yes | Base asset, e.g. BTC ETH SOL signal, or a US stock/ETF ticker (no USDT). |
| exchange | string | – | Crypto venue (default Binance), e.g. Binance Bybit OKX Bitget Hyperliquid. |
| includeReasoning | boolean | – | Include reasoning: trend ranging crypto signal and market regime drivers. |
| timeframe | string | – | Candle timeframe, 1m to 1d. Default 15m. Crypto quant intraday horizon. |
No output schema declared.
No examples provided.
pre_trade_check ~340
Returns a pre-trade check of a crypto perpetual futures order against your own rules: each passes or fails with its numbers, then GO, CAUTION or WAIT. Adds isolated liquidation distance, whether it hits before your stop, fees, accuracy needed to break even over your hold, funding by venue (cross-venue) and the regime. Read-only: places no orders.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Asset symbol, e.g. BTC, ETH, SOL. |
| equityUsd | number | – | Account equity in USD. Enables the percent-of-equity rules. |
| exchanges | array | – | Only compare these venues (default: every supported venue). |
| holdHours | number | – | Expected holding time in hours (default 8); sets the funding cost window. |
| leverage | number | – | Isolated leverage you will use, e.g. 10. Enables the liquidation checks. |
| orderType | string | – | market (taker entry) or limit (maker entry). Default market. |
| rules | object | – | Your rules, each key optional. Saved rules apply too; a failed one returns WAIT. |
| side | string | yes | Direction of the order you intend to place: long or short. |
| sizeUsd | number | yes | Order notional in USD, e.g. 10000. |
| stopPct | number | – | Stop-loss distance from entry in percent, e.g. 2. |
| targetPct | number | – | Target distance from entry in percent, e.g. 4. |
| timeframe | string | – | Market-regime timeframe: 1h, 4h or 1d (default 4h). |
No output schema declared.
No examples provided.
scan_funding_arb ~130
Ranked cross-venue funding arbitrage across major crypto perpetual futures venues — funding rate spreads, long one venue short another, as a BUY SELL HOLD composite verdict per pair. AI trading signal for crypto quant and Claude trading agents. Trade call via get_trade_call, market regime via get_market_regime. On-chain verified merkle anchor.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max ranked results, e.g. 5 (free tier cap). Crypto quant AI trading signal. |
| minSpreadBps | number | – | Minimum funding rate spread in bps. Cross-venue multi-exchange crypto signal. |
No output schema declared.
No examples provided.
scan_market_regimes ~633
Screens a whole crypto perpetual futures venue by market regime — TRENDING_UP TRENDING_DOWN RANGING VOLATILE — and returns each matching coin with confidence, trend strength, ADX, volatility ratio and how long the regime has held. Rows are the market regime classifier output for the last closed bar, sampled on Binance, Bybit, OKX and Bitget; another venue, or a timeframe a venue cannot serve, is refused with the alternatives. Billing: one call per returned row; non-matching coins are free. For a live single-coin read with cross-venue funding, call get_market_regime. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| assetClass | string | – | all (default), crypto, tradfi (every non-crypto class), equity, commodity, index, fx or premarket. |
| coins | array | – | Restrict to these symbols, e.g. ["BTC","ETH"]. Symbols not on the venue are listed in not_found and not billed. |
| exchange | string | – | Venue to screen (default Binance). A venue outside the sampled set is refused with the sampled list. |
| limit | integer | – | Page size, 1 to 100 (default 20). |
| maxRegimeAgeBars | integer | – | Keep only coins whose regime began within this many bars (1 = changed on the last closed bar). Coins whose regime start is not yet known are excluded. |
| minConfidence | number | – | Optional confidence floor, 0 to 100. |
| minLiquidityUsd | number | – | Optional USD liquidity floor applied to the scan universe: notional open interest, or 24h volume on venues that expose no bulk OI. Omitted means no floor. |
| offset | integer | – | Rows to skip, for paging within one snapshot. A changed as_of means the snapshot advanced between pages. |
| oiBasis | string | – | OI-delta basis for rankBy=oi_change: notional (default, USD) or contracts (base-coin, price-independent). Ignored by other lenses. |
| oiChangeWindow | string | – | OI-delta window for rankBy=oi_change: 1h, 4h, or 24h (default 24h). Ignored by other lenses. |
| rankBy | string | – | Optional universe lens — the same lenses and aliases as scan_trade_calls rankBy; rows then echo the lens metric. Omit to screen every coin. |
| regime | array | – | Keep only these regimes (any of): TRENDING_UP, TRENDING_DOWN, RANGING, VOLATILE. |
| sortBy | string | – | confidence (default), regime_age (most recent regime change first, unknown starts last), or rank (lens order; needs rankBy). |
| timeframe | string | – | Regime timeframe: 1h, 4h or 1d (default 4h). |
| topN | integer | – | Lens universe size, 1 to 1000 (default 100 with rankBy). Without rankBy it selects the top coins by open interest. |
No output schema declared.
No examples provided.
scan_trade_calls ~470
Returns ranked BUY SELL HOLD trade calls across the top crypto perpetual futures by open interest — one scan for whole-market coverage, each with confidence and market regime. Use this for breadth; use get_trade_call for per-coin depth and reasoning. Read-only: reads live exchange APIs, places no orders.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | Crypto venue (default Binance), e.g. Binance Bybit OKX Bitget Hyperliquid. |
| includeHolds | boolean | – | Include HOLD calls after non-HOLD (default false). |
| includeReasoning | boolean | – | Enrich each non-HOLD call with price, the top 2-3 drivers, and one-line reasoning (default false → bare verdict cells). HOLDs stay bare. Same per-call detail as get_trade_call. |
| limit | integer | – | Max ranked calls to return, 1 to 100 (default 10). Non-HOLD ranked first. |
| minConfidence | number | – | Optional confidence floor, 0 to 100, applied to non-HOLD trade calls. |
| minLiquidityUsd | number | – | Optional USD liquidity floor applied to the scan universe: notional open interest, or 24h volume on venues that expose no bulk OI. Omitted means no floor. |
| oiBasis | string | – | OI-delta basis for rankBy=oi_change: notional (default, USD) or contracts (base-coin, price-independent). Ignored by other lenses. |
| oiChangeWindow | string | – | OI-delta window for rankBy=oi_change: 1h, 4h, or 24h (default 24h). Ignored by other lenses. |
| rankBy | string | – | Universe lens: oi (default) volume gainers losers movers funding_positive funding_negative volatility oi_change (aliases vol gain lose move pfr nfr atr oid). funding_*/volatility/oi_change rank among… |
| timeframe | string | – | Candle timeframe, 1m to 1d for the scan. Default 15m intraday. |
| topN | integer | – | How many top perps by open interest to scan, 1 to 100 (default 20). |
No output schema declared.
No examples provided.
search_knowledge ~134
Returns ranked snippets from the AlgoVault knowledge bundle answering a question about its MCP tools, response shapes, integration patterns (LangChain, LlamaIndex, MAF, CrewAI), or code examples. Call this BEFORE other tool calls to confirm parameter usage and avoid hallucinating tool shapes. Fast: BM25 lexical search, no LLM call, no quota cost. For a synthesized natural-language answer use chat_knowledge. Read-only, no side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max ranked results (1-50, default 10). |
| query | string | yes | Natural-language search query (3-500 chars). |
No output schema declared.
No examples provided.
How do I install the AlgoVault — Crypto Quant Trade Calls MCP server?
AlgoVault — Crypto Quant Trade Calls is a hosted endpoint at https://api.algovault.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.algovault.com
claude mcp add --transport http algovaultfi-crypto-quant-signal-mcp 'https://api.algovault.com/mcp'
What is the AlgoVault — Crypto Quant Trade Calls MCP server?
AlgoVault — Crypto Quant Trade Calls is an MCP server listed in the public MCP registry as io.github.AlgoVaultFi/crypto-quant-signal-mcp. The Brain Layer for AI Trading Agents, quant calls + cross-venue arb across perp venues via MCP. This page covers its hosted endpoint (https://api.algovault.com/mcp).
Is the AlgoVault — Crypto Quant Trade Calls MCP server safe to use?
AlgoVault — Crypto Quant Trade Calls scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AlgoVault — Crypto Quant Trade Calls MCP server expose?
AlgoVault — Crypto Quant Trade Calls exposes 10 tools: get_trade_call, get_trade_signal, get_market_regime, scan_funding_arb, scan_trade_calls, and 5 more. Their descriptions and schemas cost roughly 2,578 tokens of context every time the server is loaded.
Does the AlgoVault — Crypto Quant Trade Calls MCP server require authentication?
No. We connected to AlgoVault — Crypto Quant Trade Calls without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AlgoVault — Crypto Quant Trade Calls MCP server still maintained?
AlgoVault — Crypto Quant Trade Calls is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.