CoinCryptoRank MCP
REMOTE · COINCRYPTORANK.COM
Real-time crypto market data, funding rates, arbitrage and trading tools from 60+ exchanges.
Available components
Last scanned (1 hour ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 38 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3241 tokens (~85/item across 38 items; 38 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 38 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Oct 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 38 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 27 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 20 Oct 26 0
- Tool “get_24h_stats” rewrote its description, which is the text the model reads security
- Tool “get_recent_trades” rewrote its description, which is the text the model reads security
- Tool “get_symbol_rules” rewrote its description, which is the text the model reads security
- 19 Oct 26 0
- New tool “get_24h_stats” functional
- New tool “get_recent_trades” functional
- New tool “get_symbol_rules” functional
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://coincryptorank.com/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=coincryptorank.com | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7b8e12ad18053d72138b165d71d9db05 |
| SANs: coincryptorank.com, *.coincryptorank.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of coincryptorank.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| coincryptorank.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| content-security-policy | default-src 'self' https: data: blob:; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.google-analytics.com https://static.cloudflareinsights.com https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline' https:; img-src 'self' https: data: blob:; connect-src 'self' https: wss: data:; font-src 'self' https: data:; media-src 'self' https: data: blob:; frame-src 'self' https://www.googletagmanager.com https://challenges.cloudflare.com; frame-ancestors 'none'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://coincryptorank.com/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://coincryptorank.com/api/v1/mcp | HTTPS enforced | 301 | https://coincryptorank.com/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
adjust_hedge ~64
Adjust one leg of a hedged position: add_long / add_short / trim_long / trim_short. Params: positionId, action, sizeUsd.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| positionId | string | yes | – |
| sizeUsd | number | yes | – |
No output schema declared.
No examples provided.
agent_chat ~54
Send a message to your agent (free-form conversation; it answers with its strategy, live data and tools).
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Agent id or name substring |
| message | string | yes | Your message to the agent |
No output schema declared.
No examples provided.
agent_decisions ~55
Recent decisions/log of one of your agents (status, trigger, summary, reply).
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Agent id or name substring |
| limit | number | – | Max rows (default 10, max 50) |
No output schema declared.
No examples provided.
agent_status ~39
Get details of one of your agents (mode, status, risk, triggers, last activity).
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Agent id or name substring |
No output schema declared.
No examples provided.
agent_trigger ~39
Run the agent's selected trigger (interval → news → trading signal) and return the decision.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Agent id or name substring |
No output schema declared.
No examples provided.
analyze_pair_liquidity ~90
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).
| Name | Type | Req | Description |
|---|---|---|---|
| exchangeA | string | yes | – |
| exchangeB | string | yes | – |
| slippagePct | number | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
backtest_basis_strategy ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | – |
| exchangeA | string | yes | – |
| exchangeB | string | yes | – |
| sizeUsd | number | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
close_hedged_position ~49
Close a hedged position (both legs, market, reduce-only). Params: positionId, reason (optional).
| Name | Type | Req | Description |
|---|---|---|---|
| positionId | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
close_position ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_24h_stats ~114
24-hour rolling statistics for one symbol from the exchange itself: last price, change percent, high/low, base and quote volume. Params: exchange ("binance"=futures, "binance_spot", "bybit", "bybit_spot", "okx", "okx_spot"), symbol (base ticker "BTC" or pair "BTCUSDT"/"BTC/USDT" — both accepted).
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_agent_events ~54
Engine event feed for a position (slices, funding collected, alerts, liquidation). Params: positionId (optional), limit (default 30).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| positionId | string | – | – |
No output schema declared.
No examples provided.
get_basis_history ~90
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).
| Name | Type | Req | Description |
|---|---|---|---|
| exchangeA | string | yes | – |
| exchangeB | string | yes | – |
| hours | number | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_basis_regime ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exchangeA | string | yes | – |
| exchangeB | string | yes | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_basis_signal ~89
Combined entry signal: basis regime + liquidity check. Returns signal (ENTER_*_BIAS/HOLD), z-score, maxNeutralUsd, recommended action. Params: exchangeA, exchangeB, symbol, maxSizeUsd (optional cap).
| Name | Type | Req | Description |
|---|---|---|---|
| exchangeA | string | yes | – |
| exchangeB | string | yes | – |
| maxSizeUsd | number | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_exchange_skills ~67
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_funding_arbitrage ~173
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
get_funding_rates ~70
Current funding rates for perpetual futures from all exchanges. Params: asset (e.g. "BTC"), exchange (e.g. "binance"), limit (default 20, max 50).
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | – |
| exchange | string | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
get_funding_schedule ~52
Funding schedule for a perp on an exchange: current rate %, interval hours, next payment time, mark price. Params: exchange, symbol.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_klines ~82
OHLCV candles from the official exchange API (binance or xt). Params: exchange ("binance"|"xt"), symbol, interval ("1m","5m","1h"), limit (max 500).
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | – |
| interval | string | – | – |
| limit | number | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_news ~35
Latest crypto news headlines with short descriptions. Params: limit (default 10, max 30).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
get_open_orders ~84
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).
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
get_orderbook ~79
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).
| Name | Type | Req | Description |
|---|---|---|---|
| depth | number | – | – |
| exchange | string | yes | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_perp_arbitrage ~93
Perpetual futures arbitrage: same perp traded on two exchanges with a price spread. Params: exchangeA, exchangeB, minSpreadPct, limit.
| Name | Type | Req | Description |
|---|---|---|---|
| exchangeA | string | – | – |
| exchangeB | string | – | – |
| limit | number | – | Max rows (default 20, max 50) |
| minSpreadPct | number | – | Minimum spread % (default 0) |
No output schema declared.
No examples provided.
get_portfolio ~90
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").
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | – |
No output schema declared.
No examples provided.
get_positions ~52
The user's open positions from our registry (user_positions) — what the agent/bots have open. Params: exchange (optional), symbol (optional).
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
get_recent_trades ~125
Recent public trades (tape) for a symbol, straight from the exchange API — no aggregator. Params: exchange ("binance", "binance_spot", "bybit", "bybit_spot", "okx", "okx_spot"), symbol (base ticker "BTC" or pair "BTCUSDT"/"BTC/USDT"), limit (default 50, max 200). Returns price, size, side and timestamp per trade.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | – |
| limit | number | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_spot_arbitrage ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exchangeA | string | – | – |
| exchangeB | string | – | – |
| limit | number | – | Max rows (default 20, max 50) |
| minProfitPct | number | – | Minimum profit % (default 0) |
No output schema declared.
No examples provided.
get_symbol_rules ~130
Trading rules for a symbol as the EXCHANGE defines them: minimum quantity, minimum notional, quantity/price step (tick size) and max leverage. Call this before sizing an order — a size below minNotional is rejected by the venue. Params: exchange ("binance"=futures, "binance_spot", "bybit", "bybit_spot", "okx", "okx_spot"), symbol (base ticker "BTC" or pair "BTCUSDT"/"BTC/USDT").
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_threat_level ~48
Instant risk assessment for a position: GREEN/YELLOW/RED, liq distance %, basis deviation %, reasons, recommended action. Params: positionId.
| Name | Type | Req | Description |
|---|---|---|---|
| positionId | string | yes | – |
No output schema declared.
No examples provided.
get_tickers ~66
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"]).
| Name | Type | Req | Description |
|---|---|---|---|
| symbols | array | – | – |
| topN | number | – | – |
No output schema declared.
No examples provided.
hedge_status ~60
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).
| Name | Type | Req | Description |
|---|---|---|---|
| positionId | string | – | – |
No output schema declared.
No examples provided.
list_agents ~28
List your AI agents: id, name, mode, scenario, status, last decision/trigger.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_hedge_positions ~23
All hedged positions of the user (open and closed).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_hedged_position ~285
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Your REAL hedge agent (id or name) whose bound API keys will open the position |
| autoTopUpUsd | number | – | – |
| exchangeA | string | yes | – |
| exchangeB | string | yes | – |
| leverage | number | yes | – |
| longExchange | string | – | which exchange is the LONG leg (default = exchangeA) |
| marginAlertPct | number | – | – |
| maxBasisDeviationPct | number | – | – |
| maxSlices | number | – | – |
| maxSlippagePct | number | – | – |
| sizeUsd | number | yes | – |
| slPct | number | – | – |
| strategy | string | – | – |
| symbol | string | yes | – |
| tpPct | number | – | – |
No output schema declared.
No examples provided.
place_order ~189
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).
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Your REAL agent (id or name) whose bound API keys will execute the order (binance/bingx/bybit) |
| amount_type | string | yes | – |
| amount_value | number | yes | – |
| exchange | string | yes | – |
| side | string | yes | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
set_hedge_protection ~101
Update protection thresholds of an open position: slPct, tpPct, maxBasisDeviationPct, marginAlertPct, autoTopUpUsd. Params: positionId + any threshold.
| Name | Type | Req | Description |
|---|---|---|---|
| autoTopUpUsd | number | – | – |
| marginAlertPct | number | – | – |
| maxBasisDeviationPct | number | – | – |
| positionId | string | yes | – |
| slPct | number | – | – |
| tpPct | number | – | – |
No output schema declared.
No examples provided.
set_sl_tp ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | – |
| stopLossPct | number | – | – |
| stopLossPrice | number | – | – |
| symbol | string | yes | – |
| takeProfitPct | number | – | – |
| takeProfitPrice | number | – | – |
No output schema declared.
No examples provided.
square_post ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Post text (max 4000 chars) |
| title | string | – | Optional article title (max 200 chars) |
No output schema declared.
No examples provided.
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.
remote · coincryptorank.com
claude mcp add --transport http qqdd27-coincryptorank-mcp 'https://coincryptorank.com/api/v1/mcp'
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 75 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 38 tools: get_funding_arbitrage, get_spot_arbitrage, get_perp_arbitrage, get_funding_rates, get_tickers, and 33 more. Their descriptions and schemas cost roughly 3,241 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.