AlgoVault MCP v1.31.0 — What's New

AlgoVault MCP v1.31.0 is live

What's new:

• Added: plugin.json, mcp.json and .cursor-plugin/plugin.json now ship inside the published npm package. An Agent-Plugins-compatible host — Cursor included — can read the server definition straight from the installed package. The files existed in the repository before this release but were not part of the tarball, so no npm consumer could obtain them.
• Changed: _algovault.compatible_with no longer names any companion package. It is projected from a machine-verified registry and is [] today, which is the truthful answer: no companion package is published. The README previously printed two package names and stated that downstream tools accept the object directly; both statements are gone. A client that rendered those names should stop.
• Changed: Every colour on every public page now comes from one generated theme region, so the site, the docs and the page templates cannot drift apart.
• Fixed: Signing in with an email that already holds a paid subscription now returns that subscription's key instead of minting a free one, and the page shown afterwards states the real tier and links the billing portal. A free key cannot resolve at /account, so the portal was unreachable for those accounts.
• Fixed: The billing-portal link from /account works again. A form-action directive in the page's Content-Security-Policy was blocking the form that opens it.

Now tracking 2272+ assets with 91.2% PFE Win Rate across 817,300 evaluated calls.

Upgrade now — remote agents get the new version automatically:

Remote MCP   https://api.algovault.com/mcp
npm          npx -y crypto-quant-signal-mcp@1.31.0

📖 Docs: algovault.com/docs
📊 Track record: algovault.com/track-record

Built by AlgoVault Labs — call interpretation for AI trading agents.