MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

AlgoVault - Crypto Quant Trade Calls

Earlier Revision Publisher unverified Confidence: Good (0.85)

AlgoVault - Crypto Quant Trade Calls is an MCP server published by AlgoVaultFi, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-25.

Does AlgoVault - Crypto Quant Trade Calls support the current MCP specification (2026-07-28)?

Not yet confirmed. AlgoVault - Crypto Quant Trade Calls is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.

Is AlgoVault - Crypto Quant Trade Calls a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for AlgoVault - Crypto Quant Trade Calls (as of 2026-08-25).

How do I connect to AlgoVault - Crypto Quant Trade Calls?

AlgoVault - Crypto Quant Trade Calls is available via a hosted remote endpoint at https://api.algovault.com/mcp, the package npm:crypto-quant-signal-mcp, the official MCP Registry under io.github.AlgoVaultFi/crypto-quant-signal-mcp, the source repository at https://github.com/algovaultlabs/crypto-quant-signal-mcp. Authentication: none. Transports: sse-legacy.

What tools does AlgoVault - Crypto Quant Trade Calls expose?

AlgoVault - Crypto Quant Trade Calls exposes 7 tools, including get_trade_call, get_trade_signal, get_market_regime, scan_funding_arb, scan_trade_calls, chat_knowledge (last verified 2026-08-25).

Does AlgoVault - Crypto Quant Trade Calls support MCP revision 2025-11-25?

Yes. AlgoVault - Crypto Quant Trade Calls supports MCP revision 2025-11-25 (checked 2026-08-25).

When were AlgoVault - Crypto Quant Trade Calls's facts last verified?

2026-08-25. Each fact on this page links to the sources used to verify it.

Which tools does AlgoVault - Crypto Quant Trade Calls expose?

7 tools verified.

  • get_trade_call
  • get_trade_signal
  • get_market_regime
  • scan_funding_arb
  • scan_trade_calls
  • chat_knowledge
  • search_knowledge

The Brain Layer for AI Trading Agents - quant calls + cross-venue arb across perp venues via MCP.

Which MCP spec revisions does AlgoVault - Crypto Quant Trade Calls support?

AlgoVault - Crypto Quant Trade Calls has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source

How widely adopted is AlgoVault - Crypto Quant Trade Calls?

Ranked #200 in The MCP 500 with Adoption Index 50.96 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
Docker MCP Catalog no API ·
npm downloads (weekly) 2,045 API ·
GitHub stars 8 API ·
GitHub forks 4 API ·
Last push 2026-09-15T06:11:14Z API ·
Repository archived no API ·

Repository and package signals for AlgoVault - Crypto Quant Trade Calls

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Created
Open issues
2
Primary language
TypeScript
License (repository)
MIT
Continuous integration
Present
Tests
Present
Security policy
None

Declared topics: ai-agents, base, crypto, defi, funding-rate, hyperliquid, mcp, model-context-protocol, perpetual-futures, quant, trading, trading-signals, x402 — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
1.28.1
Last published
First published
Releases
48
License (package)
MIT
Maintainers
1
Direct dependencies
37
Unpacked size
7.1 MB
Registry signature
Signed
Build provenance
Attested

How was this verified, and what are the sources?

Verified · method: endpoint-probe · confidence 0.85 (Good).

  1. Official MCP Registry record for io.github.AlgoVaultFi/crypto-quant-signal-mcp at version 1.26.0 - lists remote endpoint https://api.algovault.com/mcp and repository https://github.com/algovaultlabs/crypto-quant-signal-mcp - accessed
  2. Endpoint probe of https://api.algovault.com/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 7 tools - accessed
  3. Endpoint probe of https://api.algovault.com/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 7 tools - accessed