crypto-quant-signal-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSPORT | No | Transport mode for the MCP server, e.g., 'stdio' for local use or 'http' for remote. | stdio |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_trade_callA | 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. |
| get_trade_signalA | 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. |
| get_market_regimeA | 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. |
| scan_funding_arbA | 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. |
| scan_trade_callsA | 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. |
| chat_knowledgeA | 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. |
| search_knowledgeA | 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. |
| get_track_recordA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| usage-stats | Request analytics — call counts, tool breakdown, tier distribution, top assets, response times. Requires Pro or higher. |
| signal-performance | Signal track record — PFE win rates by timeframe, asset, tier, and signal type. Measures whether price moved in the signal direction during the evaluation window. |
| venues | Per-venue lifecycle state machine: shadow / promoted / retired. Each venue carries asset_count, integration + lifecycle timestamps (integrated_at / promoted_at / retired_at), and extension_count. New venues default to 'shadow' (experimental — not yet on the public /track-record dashboard) and are flagged ready-for-promotion when PFE WR clears the internal bar; an operator launches the promotion. Agents querying with a shadow venue's exchange_id should surface an 'experimental' caveat to the end user. |
| skills-analytics | Per-Skill invocation counters (calls_24h, calls_7d, calls_all_time, first/last seen) for the algovault-skills plugin. Public — slug-level aggregates only. |
TDQS
Scored across 8 tools
Most tools are clearly separated by scope (market-wide scan vs single-asset call, funding arb vs regime), but get_trade_call and get_trade_signal are exact duplicates -- one is explicitly an alias -- which will cause agent confusion. chat_knowledge and search_knowledge also both serve knowledge retrieval, though their descriptions distinguish synthesis from snippets.
Tool names consistently use snake_case imperative verb + noun (scan_, get_, chat_, search_). Minor inconsistency exists between trade_call and trade_signal for the same concept, and 'arb' is abbreviated in scan_funding_arb, but the overall pattern is predictable.
Eight tools is a well-scoped set for a crypto quant signal server: broad scan, per-asset verdict, regime, arbitrage, track record, and knowledge access. None feel extraneous, and the count matches the stated domain.
The main signal lifecycle is covered: market-wide scan, single-asset calls, regime, funding arbitrage, and verified track record. Minor gaps exist, such as no direct tool for raw market data or per-asset listing, but agents can accomplish the core workflow with this surface.