mcp-registry/com.coinfuty/coinfuty · v1.0.0
As of 2026-10-27 15:08 UTC, the Coinfuty MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Free crypto futures data: open interest, funding, long/short, liquidations, volume. No API key.
Point your MCP client at this streamable-http endpoint: https://mcp.coinfuty.com/api/mcp
7 of 7 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 →
2 parameter(s) across 2 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 →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.coinfuty%2Fcoinfuty/fixes
{
"name": "get_coin_summary",
"description": "Full derivatives snapshot for one coin: price and market cap, open interest with 1h/4h/12h/24h change, volume, liquidations (total/long/short), long/short ratio per exchange, and current funding rate per exchange (OI-weighted aggregate included). The single best tool for “what's happening with X futures”.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"symbol"
],
"properties": {
"symbol": {
"type": "string",
"description": "Coin ticker, e.g. BTC"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Coin Derivatives Summary"
}{
"name": "get_coins_markets",
"description": "List coins with live futures market data: price, 1h/24h/7d price change, open interest (with 24h change), current funding rate (OI-weighted, % per interval), 24h volume, 24h liquidations, 24h long/short ratio, and market cap. Sortable; filter to specific symbols with `symbols`.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"sort": {
"enum": [
"oi",
"price",
"volume_24h",
"market_cap",
"funding_rate",
"liq_24h",
"ls_24h",
"price_pct_24h",
"oi_pct_24h",
"trending_score_24h"
],
"type": "string",
"description": "Sort field, default `oi` (open interest)"
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Rows to return, default 20, max 100"
},
"order": {
"enum": [
"asc",
"desc"
],
"type": "string",
"description": "Default desc"
},
"symbols": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 50,
"description": "Restrict to these tickers, e.g. [\"BTC\",\"ETH\"]"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Coin Futures Market Screener"
}{
"name": "get_exchange_breakdown",
"description": "How one coin's futures activity splits across exchanges. metric=oi returns each exchange's open interest USD with 1h/4h/12h/24h % change (window ignored); long_short returns ratio + taker buy/sell volume per exchange; liquidation returns long/short liquidation USD; volume returns traded volume USD with % changes. `total` is the coin-level aggregate.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"symbol",
"metric"
],
"properties": {
"metric": {
"enum": [
"oi",
"long_short",
"liquidation",
"volume"
],
"type": "string"
},
"symbol": {
"type": "string",
"description": "Coin ticker, e.g. BTC"
},
"window": {
"enum": [
"1h",
"4h",
"12h",
"24h"
],
"type": "string",
"description": "Lookback window, default 24h (ignored for oi)"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Per-Exchange Breakdown (OI, long/short, liquidation, volume)"
}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/com.coinfuty/coinfuty"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.coinfuty/coinfuty"}) over MCP.
get_coins_markets ~266 tokensget_price_history ~258 tokensget_exchange_breakdown ~222 tokensget_coin_summary ~151 tokensget_funding_rates ~142 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fcom.coinfuty%2Fcoinfuty?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.coinfuty%2Fcoinfuty?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.coinfuty%2Fcoinfuty.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.coinfuty%2Fcoinfuty.svg :target: https://glimind.com/server/mcp-registry%2Fcom.coinfuty%2Fcoinfuty?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:22b680abf1652311…, first seen 2026-10-17, included at leaf 1132 of 79,969. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers
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.
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"
}
}
}
As of 2026-10-27 15:08 UTC, the Coinfuty MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Coinfuty MCP server advertises 7 tools, including get_coin_summary, get_coins_markets, get_exchange_breakdown, get_funding_rates, get_market_overview.
Point your MCP client at this streamable-http endpoint: https://mcp.coinfuty.com/api/mcp
Glimind scanned all 7 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.
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.