Ext Ops Panel
Open dashboard
Comparison

AlgoVault — Crypto Quant Trade Calls vs AfterFees

AlgoVault — Crypto Quant Trade Calls is an MCP server published by AlgoVaultFi. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). AfterFees is an MCP server published by linyejia. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAlgoVault — Crypto Quant Trade CallsAfterFees
Official MCP Registry Listed
Version: 1.34.0
Downloads/month (npm): 2 690
Downloads/week (npm): 1 049
Forks (GitHub): 6
Stars (GitHub): 10
Not marked · First seen
Listed
Version: 0.18.9
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Listed
Version: 1.33.0
Downloads/month (npm): 2 690
Downloads/week (npm): 1 049
Forks (GitHub): 6
Stars (GitHub): 10
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

AlgoVault — Crypto Quant Trade Calls vs AfterFees
FactAlgoVault — Crypto Quant Trade CallsAfterFees
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)10 (better)1 (worse)
Forks (GitHub) (differs)6 (better)0 (worse)
Last release (differs)2026-11-08Not published
Where it runs (differs)Remote server or your machineRemote server (afterfees.xyz/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/algovaultlabs/crypto-quant-signal-mcpgithub.com/linyejia/afterfees-mcp
Changes in the last 7 days (differs)30
First seen (differs)2026-10-112026-10-30
Endpoint at the last check (differs)Status out of date: last check 43 h ago returned HTTP 405Responded 4 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

AlgoVault — Crypto Quant Trade Calls

In its own words, on Official MCP Registry:

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

AfterFees

In its own words, on Official MCP Registry:

Crypto funding-rate arbitrage across 50 exchanges, net of fees and order-book slippage. Read-only.

How to run each

AlgoVault — Crypto Quant Trade Calls As a remote MCP server

Claude Code
claude mcp add --transport http crypto-quant-signal-mcp https://api.algovault.com/mcp

AfterFees As a remote MCP server

Claude Code
claude mcp add --transport http afterfees https://afterfees.xyz/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: AlgoVault — Crypto Quant Trade Calls · What it can do: AfterFees · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built