Alpaca Trading API integration for Model Context Protocol (MCP)
Grok Crypto Quant API is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Bias-free crypto backtests (399 coins), signals, token scam checks. Free samples; pay via x402 USDC.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http grok-crypto-quant-api-mcp https://grok-backtest-api.fly.dev/mcp
# 2 — ask your agent for something these tools do
# backtest, market_signals, token_check and 10 more
Grok Crypto Quant API costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http grok-crypto-quant-api-mcp https://grok-backtest-api.fly.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Backtest crypto strategies on 399 Coinbase coins without survivorship bias. DIY backtests usually use today's coin list, so dead coins vanish and returns are overstated; this rebuilds the universe from each past day's top coins. Breakout, momentum, dip-buy or MA-trend rules on daily data with fees, slippage, H1/H2 split and a luck flag. No data fetching or backtest code on your side. Price: $0.05
| Parameter | Type | Required | Notes |
|---|---|---|---|
| strategy | yes | — | |
| universe | no | — | |
| start | no | YYYY-MM-DD | |
| end | no | YYYY-MM-DD | |
| initial_capital | number | no | Starting capital in USD |
| fee | number | no | Fee per side (0.009 = 0.9%) |
| slippage | number | no | Slippage per side |
| include_trades | boolean | no | — |
Daily crypto market regime in one call: BTC/ETH vs 20/50-day MAs, breadth of the point-in-time top-N (no survivorship bias), coins nearest a 20-day breakout, and the R1 breakout strategy's gate and entry signals. No candle fetching or indicator code. Completed UTC daily closes only. Price: $0.01 USDC per call (x402, Base mainnet). Free sample: signals_sample.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top_n | integer | no | Universe size for breadth / breakout scan |
Token scam check in one call instead of wiring up five data sources: honeypot sell simulation, unverified code, mint/pause/blacklist powers, taxes, upgradeable proxy, age, liquidity, fake major-token (e.g. fake USDC) lookalikes and spam-airdrop patterns. Base, Ethereum or Solana. Never visits metadata URLs. Price: $0.02 USDC per call (x402, Base mainnet). Free pre-check: validate_token_check.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | base, ethereum or solana |
| address | string | yes | Token contract / mint address |
Find robust strategy params, not lucky ones: tests up to 50 combos on the same survivorship-bias-free backtester, ranks by worst-half (H1/H2) return with neighbourhood smoothing, flags overfitting, and recommends the most stable parameters rather than the best-fit ones. Price: $0.50 USDC per call (x402, Base mainnet). Free pre-check: validate_optimize.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| strategy | yes | — | |
| grid | object | yes | param -> values to try; <= 50 combos total, <= 10 values per param |
| universe | no | — | |
| start | no | YYYY-MM-DD | |
| end | no | YYYY-MM-DD | |
| initial_capital | number | no | Starting capital in USD |
| fee | number | no | Fee per side (0.009 = 0.9%) |
| slippage | number | no | Slippage per side |
| rank_by | string | no | — |
Survivorship-free top-N coin list for any past date: Coinbase USD pairs ranked by trailing 20-day dollar volume using only data available that day. Fixes your own backtests: picking today's top coins hides the ones that died and overstates returns. Price: $0.05 USDC per call (x402, Base mainnet). Free pre-check: validate_universe.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | no | YYYY-MM-DD | |
| top_n | integer | no | — |
| min_age_days | integer | no | — |
| min_avg_dollar_volume | number | no | — |
Free, one day delayed: yesterday's full /signals result (BTC/ETH trend, breadth, breakout watchlist, R1 gate) so you can judge quality before paying. Today's result: paid market_signals ($0.01). Limit 60/hour per client.
No parameter schema on file.
Free sample of the paid backtest tool on the same survivorship-bias-free engine: any strategy, point-in-time top-10 universe, window = last days (14..90) completed days, summary only. Full version: backtest ($0.05). Limit 30/hour per client.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| strategy | yes | — | |
| days | integer | no | Window length in days, ending on the last completed UTC day |
Free: service status, prices, network and data range.
No parameter schema on file.
Free: request schemas, examples, prices and limits for every paid tool/endpoint.
No parameter schema on file.
Free: check backtest arguments (same as the paid backtest tool) before paying.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| strategy | yes | — | |
| universe | no | — | |
| start | no | YYYY-MM-DD | |
| end | no | YYYY-MM-DD | |
| initial_capital | number | no | Starting capital in USD |
| fee | number | no | Fee per side (0.009 = 0.9%) |
| slippage | number | no | Slippage per side |
| include_trades | boolean | no | — |
Free: check optimize_strategy arguments and count grid combos before paying.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| strategy | yes | — | |
| grid | object | yes | param -> values to try |
| universe | no | — | |
| start | no | YYYY-MM-DD | |
| end | no | YYYY-MM-DD | |
| initial_capital | number | no | Starting capital in USD |
| fee | number | no | Fee per side (0.009 = 0.9%) |
| slippage | number | no | Slippage per side |
| rank_by | string | no | — |
Free: format-check a token_check request (no on-chain lookups).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | — |
| address | string | yes | — |
Free: check universe_snapshot arguments (date in range, enough history) before paying.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | no | YYYY-MM-DD | |
| top_n | integer | no | — |
| min_age_days | integer | no | — |
| min_avg_dollar_volume | number | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Grok Crypto Quant API or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| backtest | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| market_signals | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| token_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| optimize_strategy | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| universe_snapshot | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| signals_sample | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| backtest_sample | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| health | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_schema | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| validate_backtest | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| validate_optimize | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| validate_token_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| validate_universe | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Grok Crypto Quant API can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.