Is Crush Protocol safe and trustworthy?

tashan scores Crush Protocol on public evidence — tashan score 68.0/100, it is currently active, no known advisories against the current release, its declared dependencies reach: credentials. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Crush Protocol?

In Claude Code: run `claude mcp add crush-protocol-mcp-client -- npx -y @crush-protocol/mcp-client`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Crush Protocol?

source: crush-protocol/crush-mcp-server.

‹ The Index

Crush Protocol

npm

MCP server for market data, backtests, live strategies, and trading via Crush

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Finance & Crypto — see all ranked ›

Install (Claude Code):

claude mcp add crush-protocol-mcp-client -- npx -y @crush-protocol/mcp-client

tashan score: 68.0
Adoption: 296/wk
Upkeep: 86.0
Freshness: 99.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.13.0 — this package, not its dependency tree

Handles credentials or secretsfrom declared dependencies

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-11 @crush-protocol/mcp-client now reaches credentials Its declared dependencies reach further into your machine than they did before.
2026-08-24 @crush-protocol/mcp-client published 0.13.0, was 0.12.0 A new release is available.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 2 changes to Crush Protocol in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-crush-protocol-mcp-client.svg)](https://tashan.sh/capability/pkg-crush-protocol-mcp-client.html)

npm ↗ · source ↗ · pkg:@crush-protocol/mcp-client

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-08-25 · scorer s5 · how · something wrong here?