# CoinCryptoRank MCP (remote · coincryptorank.com)

Real-time crypto market data, funding rates, arbitrage and trading tools from 60+ exchanges.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `coincryptorank.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/qqdd27-coincryptorank-mcp/api-v1-mcp.md), [page](https://verifymcp.io/servers/qqdd27-coincryptorank-mcp/api-v1-mcp)

## Channel facts

- Endpoint: `https://coincryptorank.com/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 35 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2872 tokens (~82/item across 35 items; 35 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 18% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "agent_chat" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the CoinCryptoRank MCP server?

CoinCryptoRank MCP is a hosted endpoint at https://coincryptorank.com/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http qqdd27-coincryptorank-mcp 'https://coincryptorank.com/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "qqdd27-coincryptorank-mcp": {
      "url": "https://coincryptorank.com/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "qqdd27-coincryptorank-mcp": {
      "type": "http",
      "url": "https://coincryptorank.com/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.qqdd27-coincryptorank-mcp]
url = "https://coincryptorank.com/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "qqdd27-coincryptorank-mcp": {
      "type": "remote",
      "url": "https://coincryptorank.com/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add qqdd27-coincryptorank-mcp --url 'https://coincryptorank.com/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  qqdd27-coincryptorank-mcp:
    url: "https://coincryptorank.com/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "qqdd27-coincryptorank-mcp": {
      "Transport": "http",
      "Url": "https://coincryptorank.com/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add qqdd27-coincryptorank-mcp -t streamable-http -u 'https://coincryptorank.com/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "qqdd27-coincryptorank-mcp": {
      "type": "http",
      "url": "https://coincryptorank.com/api/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (35)

### `get_funding_arbitrage` (~173 tokens)

Cross-exchange funding-rate arbitrage opportunities from our live table. Returns assets where one exchange pays positive funding (long side) and another negative (short side). Params: exchangeA (e.g. "binance"), exchangeB (e.g. "bingx") to filter pairs between these two, minRateDiff (minimum |rate_diff| in %, e.g. 0.05), limit (max rows, default 20).

Input parameters:

- `exchangeA` (string): First exchange id, e.g. "binance"
- `exchangeB` (string): Second exchange id, e.g. "bingx"
- `limit` (number): Max rows (default 20, max 50)
- `minRateDiff` (number): Minimum absolute rate diff in percent (default 0)

### `get_spot_arbitrage` (~104 tokens)

Spot arbitrage opportunities: buy asset on one exchange, sell on another. Params: exchangeA, exchangeB (filter pairs between these two), minProfitPct (e.g. 0.5), limit.

Input parameters:

- `exchangeA` (string)
- `exchangeB` (string)
- `limit` (number): Max rows (default 20, max 50)
- `minProfitPct` (number): Minimum profit % (default 0)

### `get_perp_arbitrage` (~93 tokens)

Perpetual futures arbitrage: same perp traded on two exchanges with a price spread. Params: exchangeA, exchangeB, minSpreadPct, limit.

Input parameters:

- `exchangeA` (string)
- `exchangeB` (string)
- `limit` (number): Max rows (default 20, max 50)
- `minSpreadPct` (number): Minimum spread % (default 0)

### `get_funding_rates` (~70 tokens)

Current funding rates for perpetual futures from all exchanges. Params: asset (e.g. "BTC"), exchange (e.g. "binance"), limit (default 20, max 50).

Input parameters:

- `asset` (string)
- `exchange` (string)
- `limit` (number)

### `get_tickers` (~66 tokens)

Top crypto prices from our aggregated ticker feed (global VWAP across 60+ exchanges). Params: topN (default 10, max 30), symbols (optional array like ["BTC","ETH"]).

Input parameters:

- `symbols` (array)
- `topN` (number)

### `get_orderbook` (~79 tokens)

Orderbook depth snapshot for a symbol on an exchange. Params: exchange (e.g. "binance_spot", "bingx"), symbol (e.g. "BTC/USDT"), depth (default 10, max 25).

Input parameters:

- `depth` (number)
- `exchange` (string, required)
- `symbol` (string, required)

### `get_news` (~35 tokens)

Latest crypto news headlines with short descriptions. Params: limit (default 10, max 30).

Input parameters:

- `limit` (number)

### `get_portfolio` (~90 tokens)

The user's real exchange balances from their connected accounts (Binance futures, BingX spot+futures, Bybit, XT, Pionex). Use when the user asks about their balances, positions, or portfolio. Params: exchange (optional: "binance" | "bingx" | "bybit" | "xt" | "pionex").

Input parameters:

- `exchange` (string)

### `get_positions` (~52 tokens)

The user's open positions from our registry (user_positions) — what the agent/bots have open. Params: exchange (optional), symbol (optional).

Input parameters:

- `exchange` (string)
- `symbol` (string)

### `get_basis_history` (~90 tokens)

Minute-level price basis history between two exchanges for the same perp symbol (buyPrice vs sellPrice from our archive). Params: exchangeA, exchangeB, symbol (e.g. "HOME_USDT"), hours (default 6, max 48).

Input parameters:

- `exchangeA` (string, required)
- `exchangeB` (string, required)
- `hours` (number)
- `symbol` (string, required)

### `get_basis_regime` (~83 tokens)

Basis regime between two exchanges: mean/std/z-score/percentiles of the price spread, trend, oscillation score, and a signal (ENTER_LONG_BIAS / ENTER_SHORT_BIAS / HOLD). Params: exchangeA, exchangeB, symbol.

Input parameters:

- `exchangeA` (string, required)
- `exchangeB` (string, required)
- `symbol` (string, required)

### `get_funding_schedule` (~52 tokens)

Funding schedule for a perp on an exchange: current rate %, interval hours, next payment time, mark price. Params: exchange, symbol.

Input parameters:

- `exchange` (string, required)
- `symbol` (string, required)

### `get_klines` (~82 tokens)

OHLCV candles from the official exchange API (binance or xt). Params: exchange ("binance"|"xt"), symbol, interval ("1m","5m","1h"), limit (max 500).

Input parameters:

- `exchange` (string, required)
- `interval` (string)
- `limit` (number)
- `symbol` (string, required)

### `analyze_pair_liquidity` (~90 tokens)

Orderbook liquidity for a hedged pair: max neutral size (min of both legs depth within slippage), best prices, recommendation. Params: exchangeA, exchangeB, symbol, slippagePct (default 0.3).

Input parameters:

- `exchangeA` (string, required)
- `exchangeB` (string, required)
- `slippagePct` (number)
- `symbol` (string, required)

### `backtest_basis_strategy` (~101 tokens)

Backtest the funding-harvest strategy (S2) on our REAL funding archive: gross/net %, annualized, winrate, max consecutive negative periods, verdict. Params: exchangeA, exchangeB, symbol, days (max 90), sizeUsd.

Input parameters:

- `days` (number)
- `exchangeA` (string, required)
- `exchangeB` (string, required)
- `sizeUsd` (number)
- `symbol` (string, required)

### `get_basis_signal` (~89 tokens)

Combined entry signal: basis regime + liquidity check. Returns signal (ENTER_*_BIAS/HOLD), z-score, maxNeutralUsd, recommended action. Params: exchangeA, exchangeB, symbol, maxSizeUsd (optional cap).

Input parameters:

- `exchangeA` (string, required)
- `exchangeB` (string, required)
- `maxSizeUsd` (number)
- `symbol` (string, required)

### `open_hedged_position` (~285 tokens)

Open a NEUTRAL hedged position: LONG on exchangeA + SHORT on exchangeB (or vice versa via longExchange param). Entry is executed by the hedge engine strictly from orderbooks (max neutral size, slices, basis control). REAL mode only. Params: exchangeA, exchangeB, symbol, sizeUsd (≤5000), leverage (1-10), strategy ("funding"|"basis"|"hybrid"), longExchange (optional, default exchangeA), protection: slPct/tpPct/maxBasisDeviationPct/marginAlertPct/maxSlippagePct/maxSlices/autoTopUpUsd.

Input parameters:

- `agent` (string, required): Your REAL hedge agent (id or name) whose bound API keys will open the position
- `autoTopUpUsd` (number)
- `exchangeA` (string, required)
- `exchangeB` (string, required)
- `leverage` (number, required)
- `longExchange` (string): which exchange is the LONG leg (default = exchangeA)
- `marginAlertPct` (number)
- `maxBasisDeviationPct` (number)
- `maxSlices` (number)
- `maxSlippagePct` (number)
- `sizeUsd` (number, required)
- `slPct` (number)
- `strategy` (string)
- `symbol` (string, required)
- `tpPct` (number)

### `close_hedged_position` (~49 tokens)

Close a hedged position (both legs, market, reduce-only). Params: positionId, reason (optional).

Input parameters:

- `positionId` (string, required)
- `reason` (string)

### `hedge_status` (~60 tokens)

Current status of hedged position(s): legs, avg prices, current basis, PnL, margin/liq distance, threat level, funding countdown. Params: positionId (optional — omit for all open positions).

Input parameters:

- `positionId` (string)

### `adjust_hedge` (~64 tokens)

Adjust one leg of a hedged position: add_long / add_short / trim_long / trim_short. Params: positionId, action, sizeUsd.

Input parameters:

- `action` (string, required)
- `positionId` (string, required)
- `sizeUsd` (number, required)

### `set_hedge_protection` (~101 tokens)

Update protection thresholds of an open position: slPct, tpPct, maxBasisDeviationPct, marginAlertPct, autoTopUpUsd. Params: positionId + any threshold.

Input parameters:

- `autoTopUpUsd` (number)
- `marginAlertPct` (number)
- `maxBasisDeviationPct` (number)
- `positionId` (string, required)
- `slPct` (number)
- `tpPct` (number)

### `get_threat_level` (~48 tokens)

Instant risk assessment for a position: GREEN/YELLOW/RED, liq distance %, basis deviation %, reasons, recommended action. Params: positionId.

Input parameters:

- `positionId` (string, required)

### `list_hedge_positions` (~23 tokens)

All hedged positions of the user (open and closed).

### `get_agent_events` (~54 tokens)

Engine event feed for a position (slices, funding collected, alerts, liquidation). Params: positionId (optional), limit (default 30).

Input parameters:

- `limit` (number)
- `positionId` (string)

### `get_open_orders` (~84 tokens)

List open orders on an exchange (REAL). Params: exchange ("binance"|"bingx"|"bybit"), symbol (optional, e.g. "BTC_USDT"). binance = futures open orders, bybit = linear perps; bingx spot returns unsupported (single-order query only).

Input parameters:

- `exchange` (string, required)
- `symbol` (string)

### `close_position` (~82 tokens)

Close an open position from our registry (user_positions): market reduce-only on the exchange (binance/bingx/bybit), cancel exchange SL/TP, record realized PnL. Params: exchange, symbol (e.g. "BTC_USDT"). Returns fill price and PnL.

Input parameters:

- `exchange` (string, required)
- `symbol` (string, required)

### `set_sl_tp` (~116 tokens)

Set/update exchange-side stop-loss and take-profit on an open position (REAL; binance futures, bybit linear; bingx spot unsupported). Params: exchange, symbol, stopLossPct/takeProfitPct (percent from entry) or absolute stopLossPrice/takeProfitPrice.

Input parameters:

- `exchange` (string, required)
- `stopLossPct` (number)
- `stopLossPrice` (number)
- `symbol` (string, required)
- `takeProfitPct` (number)
- `takeProfitPrice` (number)

### `place_order` (~189 tokens)

Place a real market order on the user's exchange (Binance or BingX — only exchanges connected to this agent). Trading is only allowed when the agent mode is REAL. The order size is strictly limited by the agent's risk % of free balance; the system validates and may reject. A stop-loss and take-profit are placed on the exchange automatically. Params: exchange ("binance"|"bingx"), symbol (asset like "BTC"), side ("BUY"|"SELL"), amount_type ("PERCENTAGE"|"FIXED_USDT"), amount_value (number).

Input parameters:

- `agent` (string, required): Your REAL agent (id or name) whose bound API keys will execute the order (binance/bingx/bybit)
- `amount_type` (string, required)
- `amount_value` (number, required)
- `exchange` (string, required)
- `side` (string, required)
- `symbol` (string, required)

### `list_agents` (~28 tokens)

List your AI agents: id, name, mode, scenario, status, last decision/trigger.

### `agent_status` (~39 tokens)

Get details of one of your agents (mode, status, risk, triggers, last activity).

Input parameters:

- `agent` (string, required): Agent id or name substring

### `agent_chat` (~54 tokens)

Send a message to your agent (free-form conversation; it answers with its strategy, live data and tools).

Input parameters:

- `agent` (string, required): Agent id or name substring
- `message` (string, required): Your message to the agent

### `agent_trigger` (~39 tokens)

Run the agent's selected trigger (interval → news → trading signal) and return the decision.

Input parameters:

- `agent` (string, required): Agent id or name substring

### `agent_decisions` (~55 tokens)

Recent decisions/log of one of your agents (status, trigger, summary, reply).

Input parameters:

- `agent` (string, required): Agent id or name substring
- `limit` (number): Max rows (default 10, max 50)

### `square_post` (~86 tokens)

Publish a post to Binance Square using YOUR Binance Square OpenAPI key (set in Integrations). Max 3 different $TICKER coin tags per post; write prices as plain numbers (no $). Daily limit: 100 posts.

Input parameters:

- `content` (string, required): Post text (max 4000 chars)
- `title` (string): Optional article title (max 200 chars)

### `get_exchange_skills` (~67 tokens)

List official exchange MCP servers and AI skill libraries we aggregate (Binance Skills Hub, BingX AI Skills, OKX Agent Trade Kit, Bybit MCP, Coinbase CDP, ...) with availability for YOUR connected exchange keys — tells an AI client which exchange skills it can actually use.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/qqdd27-coincryptorank-mcp/api-v1-mcp#diagnostics

## Score history

- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69
- 2026-09-17: 69
- 2026-09-16: 68
- 2026-09-15: 68
- 2026-09-14: 67
- 2026-09-13: 67
- 2026-09-12: 66
- 2026-09-11: 66
- 2026-09-10: 65
- 2026-09-09: 65
- 2026-09-08: 65
- 2026-09-07: 64
- 2026-09-06: 64
- 2026-09-05: 63
- 2026-09-04: 63
- 2026-09-03: 62
- 2026-09-02: 62
- 2026-09-01: 61
- 2026-08-31: 61

## Common questions

### What is the CoinCryptoRank MCP server?

CoinCryptoRank MCP is listed in the public MCP registry as io.github.qqdd27/coincryptorank-mcp. Real-time crypto market data, funding rates, arbitrage and trading tools from 60+ exchanges. This page covers its hosted endpoint (https://coincryptorank.com/api/v1/mcp).

### Is the CoinCryptoRank MCP server safe to use?

CoinCryptoRank MCP scores 70 out of 100 on VerifyMCP. 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.

### What tools does the CoinCryptoRank MCP server expose?

CoinCryptoRank MCP exposes 35 tools: get_funding_arbitrage, get_spot_arbitrage, get_perp_arbitrage, get_funding_rates, get_tickers, and 30 more. Their descriptions and schemas cost roughly 2,872 tokens of context every time the server is loaded.

### Does the CoinCryptoRank MCP server require authentication?

No. We connected to CoinCryptoRank MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CoinCryptoRank MCP server still maintained?

CoinCryptoRank MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://coincryptorank.com/api/v1/mcp
- Authorisation metadata: https://coincryptorank.com/.well-known/oauth-protected-resource/api/v1/mcp
- Repository: https://github.com/qqdd27/coincryptorank-mcp
- Website: https://coincryptorank.com/
- Changelog RSS feed: https://verifymcp.io/servers/qqdd27-coincryptorank-mcp/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/qqdd27-coincryptorank-mcp/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/qqdd27-coincryptorank-mcp/api-v1-mcp