Is the Qqdd27 Coincryptorank MCP server down?

mcp-registry/io.github.qqdd27/coincryptorank-mcp · v1.0.0

healthy
Last checked 2026-10-22 02:02 UTC · handshake 251ms

As of 2026-10-22 02:02 UTC, the Qqdd27 Coincryptorank MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.5%
checks observed
3,799
outages (90d)
18
tools
38

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

Install Qqdd27 Coincryptorank MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http qqdd27-coincryptorank-mcp-server https://coincryptorank.com/api/v1/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (66/100)

D (66/100): 0 error(s), 4 warning(s) across 38 tool(s); ~4,541 tokens of tool definitions.
Scores higher than 1% of 15,507 MCP servers Glimind has audited.
Its tool list costs an agent ~4,541 tokens per session — more than 60% of servers.
65 → 64 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions37
Safety hints7
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (5)

38 of 38 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: adjust_hedge, agent_chat, agent_decisions, agent_status, agent_trigger and 33 more

92 parameter(s) across 29 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: adjust_hedge, analyze_pair_liquidity, backtest_basis_strategy, close_hedged_position, close_position and 24 more

6 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: close_hedged_position, close_position, place_order, set_hedge_protection, set_sl_tp and 1 more

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 32 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 29 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.qqdd27%2Fcoincryptorank-mcp/fixes

agent_status 1 change
{
  "name": "agent_status",
  "description": "Get details of one of your agents (mode, status, risk, triggers, last activity).",
  "inputSchema": {
    "type": "object",
    "required": [
      "agent"
    ],
    "properties": {
      "agent": {
        "type": "string",
        "description": "Agent id or name substring"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
analyze_pair_liquidity 1 change
{
  "name": "analyze_pair_liquidity",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "required": [
      "exchangeA",
      "exchangeB",
      "symbol"
    ],
    "properties": {
      "symbol": {
        "type": "string"
      },
      "exchangeA": {
        "type": "string"
      },
      "exchangeB": {
        "type": "string"
      },
      "slippagePct": {
        "type": "number"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
close_hedged_position 1 change
{
  "name": "close_hedged_position",
  "description": "Close a hedged position (both legs, market, reduce-only). Params: positionId, reason (optional).",
  "inputSchema": {
    "type": "object",
    "required": [
      "positionId"
    ],
    "properties": {
      "reason": {
        "type": "string"
      },
      "positionId": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.qqdd27/coincryptorank-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.qqdd27/coincryptorank-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.qqdd27%2Fcoincryptorank-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.qqdd27%2Fcoincryptorank-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.qqdd27%2Fcoincryptorank-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.qqdd27%2Fcoincryptorank-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.qqdd27%2Fcoincryptorank-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.qqdd27%2Fcoincryptorank-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c7e13e6bdf053997…, first seen 2026-10-20, included at leaf 32633 of 42,839. Version history · verify what your client received.

Tools (38)

Compare: most reliable finance servers · most reliable other servers · most reliable data servers · most reliable knowledge servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Qqdd27 Coincryptorank MCP server down right now?

As of 2026-10-22 02:02 UTC, the Qqdd27 Coincryptorank MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Qqdd27 Coincryptorank MCP server provide?

Qqdd27 Coincryptorank MCP server advertises 38 tools, including adjust_hedge, agent_chat, agent_decisions, agent_status, agent_trigger.

How do I install Qqdd27 Coincryptorank MCP server?

Point your MCP client at this streamable-http endpoint: https://coincryptorank.com/api/v1/mcp

Is the Qqdd27 Coincryptorank MCP server safe to connect to an AI agent?

Glimind scanned all 38 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Qqdd27 Coincryptorank MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve