CoinCryptoRank MCP
Server Details
Real-time crypto market data, funding rates, arbitrage and trading tools from 60+ exchanges.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- qqdd27/coincryptorank-mcp
- GitHub Stars
- 1
- Server Listing
- CoinCryptoRank MCP
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
35 toolsadjust_hedgeInspect
Adjust one leg of a hedged position: add_long / add_short / trim_long / trim_short. Params: positionId, action, sizeUsd.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| sizeUsd | Yes | ||
| positionId | Yes |
agent_chatInspect
Send a message to your agent (free-form conversation; it answers with its strategy, live data and tools).
| Name | Required | Description | Default |
|---|---|---|---|
| agent | Yes | Agent id or name substring | |
| message | Yes | Your message to the agent |
agent_decisionsInspect
Recent decisions/log of one of your agents (status, trigger, summary, reply).
| Name | Required | Description | Default |
|---|---|---|---|
| agent | Yes | Agent id or name substring | |
| limit | No | Max rows (default 10, max 50) |
agent_statusInspect
Get details of one of your agents (mode, status, risk, triggers, last activity).
| Name | Required | Description | Default |
|---|---|---|---|
| agent | Yes | Agent id or name substring |
agent_triggerInspect
Run the agent's selected trigger (interval → news → trading signal) and return the decision.
| Name | Required | Description | Default |
|---|---|---|---|
| agent | Yes | Agent id or name substring |
analyze_pair_liquidityInspect
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 | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | ||
| exchangeA | Yes | ||
| exchangeB | Yes | ||
| slippagePct | No |
backtest_basis_strategyInspect
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 | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| symbol | Yes | ||
| sizeUsd | No | ||
| exchangeA | Yes | ||
| exchangeB | Yes |
close_hedged_positionInspect
Close a hedged position (both legs, market, reduce-only). Params: positionId, reason (optional).
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| positionId | Yes |
close_positionInspect
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 | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | ||
| exchange | Yes |
get_agent_eventsInspect
Engine event feed for a position (slices, funding collected, alerts, liquidation). Params: positionId (optional), limit (default 30).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| positionId | No |
get_basis_historyInspect
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 | Required | Description | Default |
|---|---|---|---|
| hours | No | ||
| symbol | Yes | ||
| exchangeA | Yes | ||
| exchangeB | Yes |
get_basis_regimeInspect
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 | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | ||
| exchangeA | Yes | ||
| exchangeB | Yes |
get_basis_signalInspect
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 | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | ||
| exchangeA | Yes | ||
| exchangeB | Yes | ||
| maxSizeUsd | No |
get_exchange_skillsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_funding_arbitrageInspect
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 | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows (default 20, max 50) | |
| exchangeA | No | First exchange id, e.g. "binance" | |
| exchangeB | No | Second exchange id, e.g. "bingx" | |
| minRateDiff | No | Minimum absolute rate diff in percent (default 0) |
get_funding_ratesInspect
Current funding rates for perpetual futures from all exchanges. Params: asset (e.g. "BTC"), exchange (e.g. "binance"), limit (default 20, max 50).
| Name | Required | Description | Default |
|---|---|---|---|
| asset | No | ||
| limit | No | ||
| exchange | No |
get_funding_scheduleInspect
Funding schedule for a perp on an exchange: current rate %, interval hours, next payment time, mark price. Params: exchange, symbol.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | ||
| exchange | Yes |
get_klinesInspect
OHLCV candles from the official exchange API (binance or xt). Params: exchange ("binance"|"xt"), symbol, interval ("1m","5m","1h"), limit (max 500).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| symbol | Yes | ||
| exchange | Yes | ||
| interval | No |
get_newsInspect
Latest crypto news headlines with short descriptions. Params: limit (default 10, max 30).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
get_open_ordersInspect
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 | Required | Description | Default |
|---|---|---|---|
| symbol | No | ||
| exchange | Yes |
get_orderbookInspect
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 | Required | Description | Default |
|---|---|---|---|
| depth | No | ||
| symbol | Yes | ||
| exchange | Yes |
get_perp_arbitrageInspect
Perpetual futures arbitrage: same perp traded on two exchanges with a price spread. Params: exchangeA, exchangeB, minSpreadPct, limit.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows (default 20, max 50) | |
| exchangeA | No | ||
| exchangeB | No | ||
| minSpreadPct | No | Minimum spread % (default 0) |
get_portfolioInspect
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 | Required | Description | Default |
|---|---|---|---|
| exchange | No |
get_positionsInspect
The user's open positions from our registry (user_positions) — what the agent/bots have open. Params: exchange (optional), symbol (optional).
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | No | ||
| exchange | No |
get_spot_arbitrageInspect
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 | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows (default 20, max 50) | |
| exchangeA | No | ||
| exchangeB | No | ||
| minProfitPct | No | Minimum profit % (default 0) |
get_threat_levelInspect
Instant risk assessment for a position: GREEN/YELLOW/RED, liq distance %, basis deviation %, reasons, recommended action. Params: positionId.
| Name | Required | Description | Default |
|---|---|---|---|
| positionId | Yes |
get_tickersInspect
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 | Required | Description | Default |
|---|---|---|---|
| topN | No | ||
| symbols | No |
hedge_statusInspect
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 | Required | Description | Default |
|---|---|---|---|
| positionId | No |
list_agentsInspect
List your AI agents: id, name, mode, scenario, status, last decision/trigger.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_hedge_positionsInspect
All hedged positions of the user (open and closed).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
open_hedged_positionInspect
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 | Required | Description | Default |
|---|---|---|---|
| agent | Yes | Your REAL hedge agent (id or name) whose bound API keys will open the position | |
| slPct | No | ||
| tpPct | No | ||
| symbol | Yes | ||
| sizeUsd | Yes | ||
| leverage | Yes | ||
| strategy | No | ||
| exchangeA | Yes | ||
| exchangeB | Yes | ||
| maxSlices | No | ||
| autoTopUpUsd | No | ||
| longExchange | No | which exchange is the LONG leg (default = exchangeA) | |
| marginAlertPct | No | ||
| maxSlippagePct | No | ||
| maxBasisDeviationPct | No |
place_orderInspect
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 | Required | Description | Default |
|---|---|---|---|
| side | Yes | ||
| agent | Yes | Your REAL agent (id or name) whose bound API keys will execute the order (binance/bingx/bybit) | |
| symbol | Yes | ||
| exchange | Yes | ||
| amount_type | Yes | ||
| amount_value | Yes |
set_hedge_protectionInspect
Update protection thresholds of an open position: slPct, tpPct, maxBasisDeviationPct, marginAlertPct, autoTopUpUsd. Params: positionId + any threshold.
| Name | Required | Description | Default |
|---|---|---|---|
| slPct | No | ||
| tpPct | No | ||
| positionId | Yes | ||
| autoTopUpUsd | No | ||
| marginAlertPct | No | ||
| maxBasisDeviationPct | No |
set_sl_tpInspect
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 | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | ||
| exchange | Yes | ||
| stopLossPct | No | ||
| stopLossPrice | No | ||
| takeProfitPct | No | ||
| takeProfitPrice | No |
square_postInspect
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 | Required | Description | Default |
|---|---|---|---|
| title | No | Optional article title (max 200 chars) | |
| content | Yes | Post text (max 4000 chars) |
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Live crypto data: funding rates, funding arbitrage, OI pressure, Fear & Greed. Free, no API key.
Live crypto funding-rate radar across 5 exchanges: events, pair briefings, calendar, spreads.
Real-time market data, screeners, technical analysis & backtesting for stocks, crypto and forex.
Related MCP Servers
- AlicenseAqualityAmaintenanceProvides live crypto derivatives data including funding rates, cross-exchange arbitrage, open interest pressure, Fear & Greed index, BTC dominance, and verified signal performance.347401MIT
- AlicenseAqualityCmaintenanceProvides live cryptocurrency market data from over 100 exchanges, enabling AI agents to fetch prices, order books, funding rates, and more for trading analysis and arbitrage opportunities.131MIT

logicroomx-mcpofficial
AlicenseNot gradedqualityDmaintenanceReal-time crypto spread, funding rates, and cash & carry yields across Binance and OKX for AI assistants.MIT- AlicenseAqualityBmaintenanceProvides live cryptocurrency market data including spot prices, OHLCV candles, order books, funding rates, and technical indicators via public exchange APIs.8MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.