crypto-quant-signal-mcp 1.13.2 โ†’ 1.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +29 -23
  2. package/package.json +1 -1
  3. package/server.json +2 -2
package/README.md CHANGED
@@ -1,4 +1,3 @@
1
-
2
1
  <p align="center">
3
2
  <a href="https://algovault.com">
4
3
  <img src="https://raw.githubusercontent.com/AlgoVaultLabs/crypto-quant-signal-mcp/main/logo.png" alt="AlgoVault" width="120" />
@@ -33,20 +32,14 @@
33
32
 
34
33
  ---
35
34
 
36
- ## ๐Ÿ“Š Live Track Record โ€” Public, Verifiable, On-Chain
37
-
38
- <p align="center">
39
- <a href="https://algovault.com/track-record">
40
- <img src="https://raw.githubusercontent.com/AlgoVaultLabs/crypto-quant-signal-mcp/main/docs/screenshots/track-record-2026-05-16.png" alt="AlgoVault Live Track Record โ€” 90.5% PFE Win Rate across 92,995 trade calls, 36 Merkle batches anchored on Base L2" width="100%" />
41
- </a>
42
- </p>
35
+ ## ๐Ÿ“Š Live Track Record
43
36
 
44
37
  <p align="center">
45
- <strong><span data-tr-field="pfe_wr">90.5%</span> PFE Win Rate</strong> ยท <strong><span data-tr-field="total_calls">92,995</span> trade calls</strong> ยท <strong><span data-tr-field="merkle_batches">36</span> on-chain batches</strong> ยท <strong><span data-tr-field="hold_rate">99%</span> HOLD rate</strong> <!-- SNAPSHOT-LINE -->
38
+ <strong><span data-tr-field="pfe_wr">90.5%</span> PFE Win Rate</strong> ยท <strong><span data-tr-field="total_calls">96,898</span> trade calls</strong> ยท <strong><span data-tr-field="merkle_batches">38</span> on-chain batches</strong> ยท <strong><span data-tr-field="hold_rate">99%</span> HOLD rate</strong> <!-- SNAPSHOT-LINE -->
46
39
  </p>
47
40
 
48
41
  <p align="center">
49
- Every call is hashed at emission, anchored on Base L2 daily, and re-evaluated against actual price action. We can't edit history. <em>Refetch live numbers any time at <a href="https://algovault.com/track-record">algovault.com/track-record</a> or <a href="https://api.algovault.com/api/performance-public">/api/performance-public</a>.</em>
42
+ Every call is hashed at emission and anchored on Base L2 daily. We can't edit history.
50
43
  </p>
51
44
 
52
45
  <p align="center">
@@ -85,27 +78,39 @@ AlgoVault MCP serves Streamable HTTP at `https://api.algovault.com/mcp` โ€” MCP-
85
78
 
86
79
  MCP `tools/list` + `resources/list` is the API surface. No `@algovault/sdk`; the protocol is the contract.
87
80
 
81
+ Building inside an agent framework? See the **Framework integrations** section below for drop-in tutorials.
82
+
88
83
  ---
89
84
 
90
- ## What's new in v1.13.2
85
+ ## Framework integrations
86
+
87
+ Drop-in tutorials for the major Python agent frameworks. Each tutorial pairs AlgoVault MCP with the framework's canonical MCP-adapter library โ€” copy-pasteable demo code, no AlgoVault SDK required.
88
+
89
+ | Framework | Tutorial | Runnable demo | Mirror |
90
+ |---|---|---|---|
91
+ | **LangChain** | [`docs/integrations/langchain.md`](https://github.com/AlgoVaultLabs/algovault-skills/blob/main/docs/integrations/langchain.md) | [`examples/langchain/demo.py`](https://github.com/AlgoVaultLabs/algovault-skills/blob/main/examples/langchain/demo.py) | [algovault.com/docs/integrations/langchain](https://algovault.com/docs/integrations/langchain) |
92
+ | **LlamaIndex** | [`docs/integrations/llamaindex.md`](https://github.com/AlgoVaultLabs/algovault-skills/blob/main/docs/integrations/llamaindex.md) | [`examples/llamaindex/demo.py`](https://github.com/AlgoVaultLabs/algovault-skills/blob/main/examples/llamaindex/demo.py) | [algovault.com/docs/integrations/llamaindex](https://algovault.com/docs/integrations/llamaindex) |
93
+ | **Microsoft Agent Framework** | [`docs/integrations/maf.md`](https://github.com/AlgoVaultLabs/algovault-skills/blob/main/docs/integrations/maf.md) | [`examples/maf/demo.py`](https://github.com/AlgoVaultLabs/algovault-skills/blob/main/examples/maf/demo.py) | [algovault.com/docs/integrations/maf](https://algovault.com/docs/integrations/maf) |
94
+ | **CrewAI** | [`docs/integrations/crewai.md`](https://github.com/AlgoVaultLabs/algovault-skills/blob/main/docs/integrations/crewai.md) | [`examples/crewai/demo.py`](https://github.com/AlgoVaultLabs/algovault-skills/blob/main/examples/crewai/demo.py) | [algovault.com/docs/integrations/crewai](https://algovault.com/docs/integrations/crewai) |
91
95
 
92
- Live since 2026-05-16:
96
+ Each demo is runnable as `python examples/<framework>/demo.py BTC 4h` โ€” gets a real BUY/SELL/HOLD verdict from `api.algovault.com/mcp`, prints it. โ‰ค5 minutes to first call.
97
+
98
+ ---
93
99
 
94
- - **๐ŸŽฏ Tool descriptions rewritten for Anthropic Tool Search.** `get_trade_call`, `scan_funding_arb`, `get_market_regime` (plus the `get_trade_signal` alias) now rank cleanly under BOTH `tool_search_tool_regex_20251119` + `tool_search_tool_bm25_20251119`, which retrieve over `tools/list` name + description + arg-name + arg-description. Combined-text coverage hits โ‰ฅ15 of 20 canonical search phrases AI-agent builders actually type. `get_market_regime` no longer claims "for a Hyperliquid perp" โ€” description now reflects the actual 5-venue coverage. Zero schema mutation; same enum members, same defaults, same Zod constraints.
95
- - **Cache-refresh recommended.** MCP clients cache tools/list at session start. To pick up the refreshed tool descriptions โ€” Claude.ai / Claude Desktop: toggle connector off+on. Cursor / Cline: restart MCP server connection.
100
+ ## What's new in v1.14.0
96
101
 
97
- ### v1.13.0 highlights (recap)
102
+ Live since 2026-05-XX (target):
98
103
 
99
- - **๐Ÿชช ERC-8004 Verified Agent on Base.** AlgoVault MCP is now registered on the canonical ERC-8004 Identity Registry at [`0x8004A169...e539a432`](https://basescan.org/address/0x8004A169FB4a3325136EB29fA0ceB6D2e539a432). Each call you make traces back to a portable, censorship-resistant agent identity on Base L2. Same on-chain track record, plus a verified agent handle that AI orchestrators can resolve. agentId [`44544`](https://basescan.org/token/0x8004A169FB4a3325136EB29fA0ceB6D2e539a432?a=44544). Verify on Basescan.
100
- - **๐Ÿ”Œ New `/api/erc-8004-reputation` endpoint.** Read-only JSON aggregator exposing agentId, identity registry address, registration timestamp, and Basescan link. Cached 5 minutes. Drop-in for any agent that wants to verify AlgoVault's on-chain handle programmatically. See `curl -s api.algovault.com/api/erc-8004-reputation | jq`.
101
- - **๐Ÿงญ Attestation pipeline rolling out separately.** The per-call on-chain attestation flow is in active design. v1.13.0 ships the identity layer cleanly; reputation scoring lands once the canonical ValidationRegistry deployment on Base mainnet is finalized upstream.
104
+ - **๐Ÿงฉ Framework integrations live.** 4 drop-in tutorials shipped in [algovault-skills](https://github.com/AlgoVaultLabs/algovault-skills): LangChain, LlamaIndex, Microsoft Agent Framework, CrewAI. Each tutorial pairs AlgoVault MCP with the framework's canonical MCP-adapter library. Copy-pasteable demo code; no SDK required. See the [Framework integrations](#framework-integrations) section above.
105
+ - **๐Ÿ“ฆ Cross-linked from algovault-skills + signal-MCP READMEs.** Both repos surface the 4 tutorials so framework users discovering AlgoVault from either side find the right entry point.
102
106
 
103
- ### v1.12.0 highlights (recap)
107
+ ### v1.13.2 highlights (recap)
104
108
 
105
- - **๐Ÿช DEX adapters added โ€” Aster + edgeX (experimental).** AlgoVault now produces signals on 2 DEX venues in shadow phase. DEX signals are produced internally for validation; promotion to the public `get_trade_call` exchange parameter happens after the shadow cohort meets the same performance bar as the 5 CEX. Direct callers continue to target the 5 CEX (Binance / Hyperliquid / Bybit / OKX / Bitget).
106
- - **๐Ÿท๏ธ Per-CEX TradFi symbol aliasing (v1.11.1).** `get_trade_call({coin:"GOLD", exchange:"BINANCE"})` now resolves to `XAUUSDT` natively. 4 CEX ร— 4-6 TradFi aliases (GOLD/SILVER/PLATINUM/PALLADIUM, plus COPPER/NATGAS on OKX). Unsupported venue + asset combinations return a structured `TRADFI_SYMBOL_UNSUPPORTED_ON_VENUE` error with `suggested_venues` so agents can self-retry.
109
+ - **๐Ÿ”Ž Tool descriptions rewritten for retrieval ranking.** `get_trade_call`, `scan_funding_arb`, `get_market_regime` descriptions rewritten for Anthropic Tool Search (BM25 + regex retrieval over `tools/list`). Param `describe()` strings tightened. Zero schema mutation โ€” same enum members, same defaults, same Zod constraints. Pure prose payload change.
110
+ - **๐Ÿชช ERC-8004 Verified Agent on Base.** AlgoVault MCP is registered on the canonical ERC-8004 Identity Registry at [`0x8004A169...e539a432`](https://basescan.org/address/0x8004A169FB4a3325136EB29fA0ceB6D2e539a432). Each call traces back to a portable, censorship-resistant agent identity on Base L2. agentId [`44544`](https://basescan.org/token/0x8004A169FB4a3325136EB29fA0ceB6D2e539a432?a=44544) on Basescan. Same on-chain track record; new verified agent handle that AI orchestrators can resolve.
111
+ - **๐Ÿ”Œ `/api/erc-8004-reputation` endpoint.** Read-only JSON aggregator exposing agentId, identity registry address, registration timestamp, and Basescan link. Cached 5 minutes. `curl -s api.algovault.com/api/erc-8004-reputation | jq`.
107
112
 
108
- > **Upgrading from v1.12.x or earlier?** The MCP tool surface is unchanged structurally โ€” `get_trade_call`, `scan_funding_arb`, `get_market_regime` keep their parameter shapes. v1.13.0 only adds a new HTTP endpoint (`/api/erc-8004-reputation`) and a public-facing badge. MCP clients (Claude Desktop, Cursor, Cline) cache `tools/list` at session start โ€” toggle the connector off/on to pick up the latest catalog metadata.
113
+ > **Upgrading from v1.13.x or earlier?** The MCP tool surface is unchanged structurally โ€” `get_trade_call`, `scan_funding_arb`, `get_market_regime` keep their parameter shapes. v1.14.0 only adds the Framework integrations cross-links; no tool schema change. If you upgraded across v1.13.2 you already picked up the refreshed tool descriptions โ€” MCP clients cache `tools/list` at session start, so toggle the connector off/on if you haven't restarted since v1.13.2.
109
114
 
110
115
  ---
111
116
 
@@ -122,6 +127,7 @@ AlgoVault is different. We give your agent **one answer**: a directional verdict
122
127
  - **Cross-venue intelligence.** Full signal generation on 5 exchanges with native candle, OI, funding, and volume data per venue. 2 DEX venues (Aster, edgeX) in experimental shadow phase. Cross-venue funding arbitrage scanning across the major CEX โ€” nobody else does multi-exchange derivatives analysis via MCP. <!-- SNAPSHOT-LINE -->
123
128
  - **Published track record with every release.** Every call is recorded with outcome prices at multiple horizons. PFE Win Rate, Profit Factor, Expected Value computed continuously. No cherry-picking, no survivorship bias. **Anchored on-chain on Base L2 โ€” we cannot rewrite history.**
124
129
  - **ERC-8004 verified agent.** AlgoVault MCP holds a registered agentId on the Base L2 Identity Registry. The agent identity is portable and on-chain.
130
+ - **Drop-in for every major agent framework.** First-party tutorials + runnable demos for LangChain, LlamaIndex, Microsoft Agent Framework, CrewAI. โ‰ค5 minutes to first call. See the [Framework integrations](#framework-integrations) section.
125
131
  - **Self-tuning model.** Indicator weights are tuned from live outcome data by our [Autonomous Optimization Engine](https://algovault.com/how-it-works). The model gets sharper with every signal.
126
132
  - **Crypto + TradFi coverage.** 730+ assets โ€” standard crypto perps on all 5 CEX; TradFi perps (stocks, indices, commodities, FX); liquidity-filtered meme coins. <!-- SNAPSHOT-LINE -->
127
133
 
@@ -198,7 +204,7 @@ Responses also include optional `closest_tradeable` (on HOLD verdicts) and `also
198
204
  { "coin": "SOL", "timeframe": "15m", "confidence": 73 }
199
205
  ],
200
206
  "_algovault": {
201
- "version": "1.13.1",
207
+ "version": "1.14.0",
202
208
  "tool": "get_trade_call",
203
209
  "compatible_with": ["crypto-quant-risk-mcp", "crypto-quant-backtest-mcp"]
204
210
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "crypto-quant-signal-mcp",
3
- "version": "1.13.2",
3
+ "version": "1.14.0",
4
4
  "mcpName": "io.github.AlgoVaultFi/crypto-quant-signal-mcp",
5
5
  "description": "The Brain Layer for AI Trading Agents โ€” composite quant calls across 5 exchanges (Hyperliquid, Binance, Bybit, OKX, Bitget), cross-venue arb, regime-aware classification, and a 20-skill catalog via MCP.",
6
6
  "main": "dist/index.js",
package/server.json CHANGED
@@ -3,7 +3,7 @@
3
3
  "name": "io.github.AlgoVaultFi/crypto-quant-signal-mcp",
4
4
  "title": "AlgoVault โ€” Crypto Quant Trade Calls",
5
5
  "description": "The Brain Layer for AI Trading Agents โ€” quant calls + cross-venue arb across 5 exchanges via MCP.",
6
- "version": "1.13.2",
6
+ "version": "1.14.0",
7
7
  "repository": {
8
8
  "url": "https://github.com/AlgoVaultLabs/crypto-quant-signal-mcp",
9
9
  "source": "github"
@@ -18,7 +18,7 @@
18
18
  {
19
19
  "registryType": "npm",
20
20
  "identifier": "crypto-quant-signal-mcp",
21
- "version": "1.13.1",
21
+ "version": "1.14.0",
22
22
  "transport": {
23
23
  "type": "stdio"
24
24
  },