AlgoVault — Crypto Quant Trade Calls
NPM · CRYPTO-QUANT-SIGNAL-MCP · 2 COMPONENTS
The Brain Layer for AI Trading Agents — quant calls + cross-venue arb across perp venues via MCP.
Available components
Last scanned (3 hours ago)
Scores higher than 22% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security77
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects markdown-it 14.1.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 740 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to AlgoVaultLabs/crypto-quant-signal-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +5
- CVE-2026-67314 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- CVE-2026-101906 affects this package: high ▼ security
- CVE-2026-67315 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101905 affects this package: high ▼ security
- CVE-2026-67320 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-101909 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2026-101899 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-67321 affects this package: high ▼ security
- CVE-2026-111758 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Dependency health: unverified → partial ▲ functional
- 2 Nov 26 −5
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-67314 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- CVE-2026-101906 affects this package: high ▼ security
- CVE-2026-67315 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-101909 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-101903 affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-101907 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2026-101899 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-67321 affects this package: high ▼ security
- CVE-2026-111758 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-67320 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-101905 affects this package: high ▼ security
- Known CVEs: fail → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- Package version: 1.32.0 → 1.33.0 functional
- 1 Nov 26 0
- CVE-2026-101899 affects this package: high ▼ security
- CVE-2026-101905 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-67320 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-111758 affects this package: high ▼ security
- CVE-2026-67321 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-101907 affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-101903 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101909 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-67315 affects this package: high ▼ security
- CVE-2026-101906 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-67314 affects this package: high ▼ security
- 31 Oct 26 0
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-101903 affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-101907 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2026-101899 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-67321 affects this package: high ▼ security
- CVE-2026-111758 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-67320 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-101905 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-101909 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101906 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-67314 affects this package: high ▼ security
- CVE-2026-67315 affects this package: high ▼ security
- 30 Oct 26 0
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-101905 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-101909 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-101903 affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-101907 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2026-101899 affects this package: high ▼ security
- CVE-2026-67314 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-67321 affects this package: high ▼ security
- CVE-2026-111758 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-67320 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-101906 affects this package: high ▼ security
- CVE-2026-67315 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- 29 Oct 26 0
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-67314 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- CVE-2026-101906 affects this package: high ▼ security
- CVE-2026-67315 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-101909 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-101903 affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-101907 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2026-101899 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67321 affects this package: high ▼ security
- CVE-2026-111758 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-67320 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-101905 affects this package: high ▼ security
- 28 Oct 26 0
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-101909 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-101903 affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-101907 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-67314 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2026-101899 affects this package: high ▼ security
- CVE-2026-67321 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-67320 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-111758 affects this package: high ▼ security
- CVE-2026-67315 affects this package: high ▼ security
- CVE-2026-101906 affects this package: high ▼ security
- 21 Oct 26 −1
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/crypto-quant-signal-mcp@1.33.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | AlgoVaultLabs/crypto-quant-signal-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/AlgoVaultLabs/crypto-quant-signal-mcp/.github/workflows/publish-npm.yml@refs/tags/v1.33.0 |
| Rekor log index | 3641106609 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:567da98785d5a9394bf9a0356d19924ca1b05dba2c867cb6ebfc18ed54db59b2d8f6b0f43b531189dd4937ae1e7d82040564911089583b05ac37f01f7 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 26 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3pq3-5fj3-cg6v | CVE-2026-101898 | high | yes | |
| GHSA-42h9-826w-cgv3 | CVE-2026-67313 | medium | yes | |
| GHSA-44g4-m2mj-wpvx | CVE-2026-101899 | medium | yes | |
| GHSA-4hqw-qxg8-jxx2 | CVE-2026-101900 | medium | yes | |
| GHSA-542g-h47m-68v8 | CVE-2026-101901 | high | yes | |
| GHSA-7q8q-rj6j-mhjq | CVE-2026-67319 | medium | yes | |
| GHSA-9fr6-4gfg-395g | CVE-2026-101902 | medium | yes | |
| GHSA-f4gw-2p7v-4548 | CVE-2026-67315 | medium | yes | |
| GHSA-gcfj-64vw-6mp9 | CVE-2026-67320 | high | yes | |
| GHSA-hcpx-6fm6-wx23 | CVE-2026-67321 | medium | yes | |
| GHSA-j8rh-479h-cp32 | CVE-2026-101904 | medium | yes | |
| GHSA-jqh4-m9w3-8hp9 | CVE-2026-67317 | medium | yes | |
| GHSA-m8m8-qj5v-23w3 | CVE-2026-101905 | high | yes | |
| GHSA-mghh-pgcx-3jjj | CVE-2026-101906 | high | yes | |
| GHSA-mmx7-hfxf-jppx | CVE-2026-67316 | medium | yes | |
| GHSA-mwf2-3pr3-8698 | CVE-2026-67318 | medium | yes | |
| GHSA-pmv8-rq9r-6j72 | CVE-2026-67312 | medium | yes | |
| GHSA-vh66-26gq-q6x8 | CVE-2026-101908 | medium | yes | |
| GHSA-x97p-jq2g-jp4f | CVE-2026-101909 | high | yes | |
| GHSA-xj6q-8x83-jv6g | CVE-2026-67314 | medium | yes | |
| GHSA-253c-mchw-3w2r | medium | yes | ||
| GHSA-6v5v-wf23-fmfq | CVE-2026-48988 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-gfr2-rv44-r23c | CVE-2026-111758 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-r7fv-28h4-cvq7 | CVE-2026-111759 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vfgh-jcmw-g37q | CVE-2026-111766 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Stale | 74 |
| No linked repository | 6 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the AlgoVault — Crypto Quant Trade Calls MCP server?
AlgoVault — Crypto Quant Trade Calls runs locally as an npm package, launched with npx -y crypto-quant-signal-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · crypto-quant-signal-mcp
claude mcp add algovaultfi-crypto-quant-signal-mcp -- npx -y crypto-quant-signal-mcp
What is the AlgoVault — Crypto Quant Trade Calls MCP server?
AlgoVault — Crypto Quant Trade Calls is an MCP server listed in the public MCP registry as io.github.AlgoVaultFi/crypto-quant-signal-mcp. The Brain Layer for AI Trading Agents, quant calls + cross-venue arb across perp venues via MCP. This page covers its npm package (crypto-quant-signal-mcp).
Is the AlgoVault — Crypto Quant Trade Calls MCP server safe to use?
AlgoVault — Crypto Quant Trade Calls scores 43 out of 100 on VerifyMCP. We recorded 26 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the AlgoVault — Crypto Quant Trade Calls MCP server still maintained?
AlgoVault — Crypto Quant Trade Calls is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AlgoVault — Crypto Quant Trade Calls MCP server under?
AlgoVault — Crypto Quant Trade Calls declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.