AlgoVault — Crypto Quant Trade Calls MCP server
io.github.AlgoVaultFi/crypto-quant-signal-mcpAlgoVaultFistreamable-httpv1.36.0Scanned
The Brain Layer for AI Trading Agents — quant calls + cross-venue arb across perp venues via MCP.
11 tools: 3 change things and 8 only read.
- Reads private data · 3
- Reads text others write · 11
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AlgoVault — Crypto Quant Trade Calls MCP server can do
The AlgoVault — Crypto Quant Trade Calls MCP server is published by the GitHub account AlgoVaultFi. It has 11 tools. It can create or change data (3 tools: scan_funding_arb, scan_trade_calls and scan_market_regimes), but cannot delete data. 8 tools only read.
3 tools read private data (chat_knowledge, search_knowledge and get_track_record); 11 tools bring in text other people can write (get_trade_call, get_trade_signal, get_market_regime and 8 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.36.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Changes things 3Claude Code: ask
scan_funding_arbRanked 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 pai…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Funding Arbitrage Scanner
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
scan_market_regimesScreens 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, …Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Market Regime Screener
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
scan_trade_callsReturns 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.Reads text others write1 finding
Why it is in this group
- The name "scan_trade_calls" says "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "scan_trade_calls" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "scan_trade_calls" says "call": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Market Scanner
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
Only reads 8Show 8 read-only tools
chat_knowledgeReturns a synthesized natural-language answer with citations, grounded in the AlgoVault knowledge bundle (every MCP tool description, response shape, integration tutorial, and code…Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe name "chat_knowledge" says "chat": it reads messages.
- private-dataThe description's first sentence says "return" and "vault": it reads secrets.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "chat_knowledge" says "chat": it reads messages, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Knowledge Q&A
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
get_market_regimeReturns the market regime — TRENDING_UP TRENDING_DOWN RANGING VOLATILE — with confidence and a strategy hint, for one crypto perpetual futures.Reads text others writeNo findings
Why it is in this group
- The name "get_market_regime" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Market Regime Classifier
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
get_support_resistance_zonesReturns support and resistance zones for one coin on one venue's perpetuals, such as Binance, Bybit or OKX, for one to three timeframes.Reads text others writeNo findings
Why it is in this group
- The name "get_support_resistance_zones" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns support and resistance zones for one coin on one venue's perpetuals, such as Binance, Bybit or OKX, for one to three timeframes. Read-only. Per timeframe: up to 3 support and 3 resistance zones, ranked outward from price, each with its low and high, distance from price, bars touched in the last 90, tests in the last 30, last touch, and whether it flipped between support and resistance after two closes through it. Also returns volume against its 20-bar average and flags such as no zone above (price above every zone in its history). Use with get_trade_call or get_market_regime for the same coin. (Beta)
Annotations the server declares
- title: Support and Resistance Zones (Beta)
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
get_track_recordReturns the AlgoVault track record — aggregated PFE win rates by call type, timeframe and asset tier, plus the evaluation methodology and window.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_track_record" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "vault": it reads secrets.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Track Record
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
get_trade_callReturns a composite verdict — BUY SELL HOLD trade call with confidence and market regime — for one crypto or tokenized-stock perpetual futures.Reads text others writeNo findings
Why it is in this group
- The name "get_trade_call" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Composite Trade Call
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
get_trade_signalReturns a composite verdict — BUY SELL HOLD trade call with confidence and market regime — for one crypto or tokenized-stock perpetual futures.Reads text others writeNo findings
Why it is in this group
- The name "get_trade_signal" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Trade Signal
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
pre_trade_checkReturns 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.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Pre-Trade Check
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
search_knowledgeReturns ranked snippets from the AlgoVault knowledge bundle answering a question about its MCP tools, response shapes, integration patterns (LangChain, LlamaIndex, MAF, CrewAI), or…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "search_knowledge" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "vault": it reads secrets.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Knowledge Search
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write11
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:56 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.algovault.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.algovault.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.algovault.com/mcp: tools/list returned 11 tools to an anonymous client, including scan_funding_arb (write), scan_trade_calls (write), scan_market_regimes (write)
Posture changes
- Oct 29, 2026
- RFC 9728 protected resource metadata: none to https://api.algovault.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.algovault.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
- Warnscan_trade_calls
The server marks "scan_trade_calls" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "scan_trade_calls" says "call": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:get_support_resistance_zonesOnly readsdescriptioninputSchema
- Changed:pre_trade_checkOnly readsinputSchema
Tools1 added.+1 addedView diff
- Added:get_support_resistance_zonesOnly reads
Tools1 added.+1 addedView diff
- Added:pre_trade_checkOnly reads
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://api.algovault.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://api.algovault.com; Dynamic client registration: not observed ->…View diff
- RFC 9728 protected resource metadata: none to https://api.algovault.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.algovault.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Install
Pinned to version 1.36.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http crypto-quant-signal https://api.algovault.com/mcpclaude mcp add --transport http crypto-quant-signal https://api.algovault.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__crypto-quant-signal__get_trade_call",
"mcp__crypto-quant-signal__get_trade_signal",
"mcp__crypto-quant-signal__get_market_regime",
"mcp__crypto-quant-signal__pre_trade_check",
"mcp__crypto-quant-signal__get_support_resistance_zones",
"mcp__crypto-quant-signal__chat_knowledge",
"mcp__crypto-quant-signal__search_knowledge",
"mcp__crypto-quant-signal__get_track_record"
],
"ask": [
"mcp__crypto-quant-signal__scan_funding_arb",
"mcp__crypto-quant-signal__scan_trade_calls",
"mcp__crypto-quant-signal__scan_market_regimes"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as crypto-quant-signal. Review it before you use it.
Capability tags behind 11 rules
- mcp__crypto-quant-signal__get_trade_call untrusted-input
- mcp__crypto-quant-signal__get_trade_signal untrusted-input
- mcp__crypto-quant-signal__get_market_regime untrusted-input
- mcp__crypto-quant-signal__scan_funding_arb untrusted-input
- mcp__crypto-quant-signal__scan_trade_calls untrusted-input
- mcp__crypto-quant-signal__scan_market_regimes untrusted-input
- mcp__crypto-quant-signal__pre_trade_check untrusted-input
- mcp__crypto-quant-signal__get_support_resistance_zones untrusted-input
- mcp__crypto-quant-signal__chat_knowledge private-data, untrusted-input
- mcp__crypto-quant-signal__search_knowledge private-data, untrusted-input
- mcp__crypto-quant-signal__get_track_record private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.AlgoVaultFi/crypto-quant-signal-mcp/verify?hash=0f6cd0713983cba07a7bbc841a8ba22595edbe2cff444c6755f642de123b59a0" | jq -e '.changed == false'Pinned hash 0f6cd0713983, from Nov 20, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.AlgoVaultFi/crypto-quant-signal-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.AlgoVaultFi/crypto-quant-signal-mcp)Source: MCP Registry · repository. Synced Nov 20, 2026, 15:17 UTC.
AlgoVault — Crypto Quant Trade Calls MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AlgoVault — Crypto Quant Trade Calls MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AlgoVault — Crypto Quant Trade Calls MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AlgoVault — Crypto Quant Trade Calls MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AlgoVault — Crypto Quant Trade Calls MCP server have?
- 11 tools: 3 write, 8 read. scan_funding_arb, scan_trade_calls, scan_market_regimes, get_trade_call, get_trade_signal, get_market_regime, pre_trade_check, get_support_resistance_zones and 3 more.
Does the AlgoVault — Crypto Quant Trade Calls MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AlgoVault — Crypto Quant Trade Calls MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AlgoVault — Crypto Quant Trade Calls MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.