AlgoVault — Crypto Quant Trade Calls

Quick start (30 seconds)

No code. No install. No API key to start — sign in free when you need more. The server speaks Streamable HTTP at https://api.algovault.com/mcp — any Model Context Protocol client connects directly.

1. Add the connector. In Claude → Customize → Connectors → + → Add custom connector:

2. Ask for a call. In plain language:

"Get me a trade call for ETH on the 4h timeframe"

Your Claude now has a quant analyst built in. Prefer local? Run npx -y crypto-quant-signal-mcp.

Running locally on npm 12+? npm v12 disables dependency install scripts by default. AlgoVault's optional local SQLite mode uses the native better-sqlite3 module — if you install it into a project, run npm approve-scripts (or npm install --allow-scripts) to build it. The hosted HTTP transport (api.algovault.com/mcp) needs no local build.

What one call returns

One API call. One verdict. Not 8 raw indicators. get_trade_call returns a directional BUY / SELL / HOLD with a confidence score and the detected market regime — a composite verdict, not a data dump for your agent to interpret.

Under the hood, a self-tuning model fuses momentum, trend structure, derivatives positioning, open interest, and volume into one weighted call. Every call reports market regime — trending, ranging, or volatile — alongside direction and confidence. Directional calls fire only when conviction clears the threshold; roughly 99% of evaluations return HOLD.

{
  "call": "BUY",
  "confidence": 78,
  "price": 84250.50,
  "indicators": {
    "funding_rate": 0.0001,
    "funding_24h_avg": 0.00008,
    "funding_state": "NORMAL",
    "oi_change_pct": 2.4,
    "volume_24h": 2381602633,
    "trend_persistence": "HIGH",
    "breakout_pending": "INACTIVE"
  },
  "regime": "TRENDING_UP",
  "reasoning": "Trending regime, upward bias. Funding pressure mild. Volatility neither expanding nor compressed. Trend persistence elevated; momentum structure. Strong conviction from aligned signals.",
  "timestamp": 1712764800,
  "coin": "BTC",
  "timeframe": "1h",
  "also_see": [
    { "coin": "ETH", "timeframe": "1h", "confidence": 82 },
    { "coin": "SOL", "timeframe": "15m", "confidence": 73 }
  ],
  "_algovault": {
    "version": "1.30.0",
    "tool": "get_trade_call",
    "compatible_with": []
  }
}

The _algovault block is the envelope every tool response carries: the server version, the tool that answered, your quota, and compatible_with — the companion packages that accept this object directly. It projects from a machine-verified registry, so it lists a package only once that package is published and runnable. It is [] today, and that is the truthful answer: there is no companion package yet.

Live, verifiable track record

The full record is public and on-chain — no cherry-picking, no survivorship bias:

• Live dashboard — algovault.com/track-record
• Merkle batch verifier — algovault.com/verify
• Anchor contract on Base L2 — 0x6485…0f81
• All batches (raw JSON) — api.algovault.com/api/merkle-batches

AlgoVault is also a verified agent on the ERC-8004 Identity Registry (Base L2), agentId 44544 — a portable, on-chain handle AI orchestrators can resolve.

Works with your stack

AlgoVault is drop-in for every MCP-spec client, every major agent framework, and every official exchange Agent Trade Kit — no SDK, no wrapper. It serves Streamable HTTP at https://api.algovault.com/mcp; tools/list + resources/list is the API surface.

MCP clients.

Agent plugin hosts. The npm package ships plugin.json, mcp.json and .cursor-plugin/plugin.json, so an Agent-Plugins-compatible host — Cursor included — can read the server definition out of the installed package instead of being handed a config block to paste.

Agent frameworks. First-party tutorials pair AlgoVault with each framework's canonical MCP adapter — copy-pasteable demo code, no SDK.

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.

Exchange Agent Trade Kits. AlgoVault returns the analytics; your agent's risk policy decides what to execute. All demos run testnet/demo only. For Binance, the Agent OS path is the recommended default for new integrations — OAuth at connect time, no API keys on the machine; the key-based kit remains right for custom order types.

Tools & resources

The MCP tools live at https://api.algovault.com/mcp. Every asset works across the full supported timeframe range, on major crypto perpetual venues.

• get_trade_call (alias get_trade_signal) — composite BUY/SELL/HOLD verdict with confidence + regime, any asset, any timeframe.
• scan_trade_calls — scans the top-N perps by open interest on a venue; returns every actionable call in one shot.
• scan_funding_arb — cross-venue funding-rate spreads across 7 venues (Hyperliquid, Binance, Bybit, Gate, KuCoin, Aster, OKX), ranked. The only MCP server doing multi-exchange derivatives arbitrage.
• get_market_regime — classifies TRENDING_UP / TRENDING_DOWN / RANGING / VOLATILE for strategy selection.
• search_knowledge + chat_knowledge — free BM25 search and grounded Q&A over the full knowledge bundle.
• get_track_record — the published track record as a tool call, for clients that bridge tools but not resources. include opens the per-asset, per-venue and recent-call sections.

Performance is exposed as a read-only MCP resource: performance://signal-performance (aggregated PFE win rate, never raw outcomes). Full parameter reference at algovault.com/docs.

Skills (20 ready-to-use Anthropic Agent Skills)

Single-prompt wrappers over 1–3 tool calls — regime gating, multi-timeframe consensus, funding-arb monitoring, and more. Install with claude plugin install AlgoVaultLabs/algovault-skills; browse at algovault.com/skills.

Pricing

Quota-only tiers. Every tier gets all venues, all assets, all timeframes — you pay for call volume, nothing else.

Two meters per paid tier, monthly and daily, enforced independently: a call is refused when either is exhausted, and the daily window is a UTC calendar day resetting at 00:00 UTC. Quota is counted per call, regardless of verdict.

Subscriptions: Sign up at api.algovault.com/signup. Starter unlocks 10,000 calls/mo (up to 1,000/day) for $9.99/mo, or $39.90 for six months prepaid — add ?interval=6month to pick the prepay term. API key delivered instantly after checkout.

Pro 6-month is currently $129 — limited-time pricing; subscribe now and renewals keep your price.

x402 micropayments: AI agents pay per HTTP call with USDC on Base — no signup, no API key, no billing. The payment receipt is the credential. See x402.org.

What's new in v1.31.0

• 🧩 Install from the package, not from a pasted config block. plugin.json, mcp.json and .cursor-plugin/plugin.json now ship inside the npm tarball, so an Agent-Plugins-compatible host — Cursor included — reads the server definition straight out of the installed package. Until this release those files lived in the repository only, and no npm consumer could obtain them.

• v1.31.1 — Trade-call verdicts are now chosen by one declared rule per timeframe and trend direction, instead of a global mode setting. The calls you receive are unchanged by the switch.

Upgrading from v1.30.x — one value in the response envelope changed: _algovault.compatible_with is now [] and names no companion package. If your client rendered those package names, stop rendering them; there is no companion package published today. Nothing else in the envelope changed, and no tool or parameter was added, renamed or removed.

v1.30.x highlights (recap)

• 🔑 Your key, one click away. Every tool response that carries an auth block now returns claim_url and claim_hint in the _algovault envelope — a direct link to keep the key you are already using, and a heads-up before you reach the cap.
• 💵 Six-month pricing is machine-readable. GET /api/plans/public gains price_usd_6month on every tier, so a client can render prepay pricing instead of hardcoding it.
• 🤝 Enterprise is quoted, not published. The plans endpoint now returns null for Enterprise price and limits rather than a fixed figure. No key was removed — the values are null.

v1.29.x highlights (recap)

• 📊 The track record is a tool, not only a resource. get_track_record returns the same verified aggregate as performance://signal-performance, so a harness that bridges tools but not resources can read it.
• ✋ HOLD means HOLD. When a book is not currently trading, the call returns HOLD instead of a direction, and the reasoning says so and says when it resumes.
• 🔓 Allowances are machine-readable. GET /api/plans/public returns the current free and paid call limits, unauthenticated.

Refresh your MCP client to pick up this release. MCP clients cache tools/list at session start — Claude.ai/Desktop: toggle the connector off+on; Cursor/Cline: restart the MCP server connection.

Privacy

Local mode: zero telemetry — call history stays on your machine. Remote mode: request metadata logged for analytics (IP hashed, never stored raw). See the privacy policy.

License

MIT

Disclaimer: AlgoVault provides directional entry interpretation for AI agents. Exit timing is determined by your agent or strategy. This is not financial advice. Past performance does not guarantee future results.