BitCLI
REMOTE · MCP.BITCLI.IO · 2 COMPONENTS
Real-time crypto futures order flow, BCT-30 matrices, and HFT alerts across 1,650+ contracts.
Available components
Last scanned (45 minutes ago)
Scores higher than 43% 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 Security57
- 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 6 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2137 tokens (~356/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_notification" 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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Tool “market_data” rewrote its description, which is the text the model reads security
- Tool “system_docs” rewrote its description, which is the text the model reads security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 58
First indexed and scored.
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://mcp.bitcli.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bitcli.io | CN=YE2,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6fa35cecf8407aedf16ff0413a2a1432c31 |
| SANs: *.bitcli.io, bitcli.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.bitcli.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| bitcli.io. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.bitcli.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.bitcli.io/mcp | HTTPS enforced | 301 | https://mcp.bitcli.io/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 →
alert_manager ~397
BEHAVIOR: State-mutating operation. Injects or removes in-memory execution triggers in the C++ engine. When triggered, it dispatches asynchronous out-of-band notifications (Telegram/Discord) without requiring the agent to remain awake. PRICING: Targeted coin alerts cost $0.001 USD. Global wildcard scans ('*') cost $0.002 USD. Wildcards require a positive USD balance on Free/Trader plans. ACTIONS & PARAMETER INTERACTIONS: - 'create': Deploys a new trigger. Requires 'command'. Returns the assigned alert_id and expiration time. - 'list': Returns an array of currently active triggers, their IDs, and remaining TTLs. Ignores 'command' and 'alert_id'. - 'cancel': Removes a specific trigger. Requires 'alert_id'. Ignores 'command'. - 'clear_all': Purges all active triggers for the account. Ignores 'command' and 'alert_id'. USAGE GUIDELINES: Use this tool to establish asynchronous monitoring instead of polling `market_data`. Requires an authenticated API key; anonymous guests will receive an authorization error. Enforces plan capacity limits. ERRORS: Authentication failures, capacity limit breaches, or syntax errors return an explicit 'isError: true' payload detailing the rejection reason.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Trigger management action. |
| alert_id | integer | – | Numeric alert identifier (required for 'cancel'). |
| command | string | – | Unified BitCLI command string (required for 'create', e.g. 'btc 95k', '* vol 15m x4 cd=30m'). |
| destinations | array | – | Array of destination routing strings obtained via `user_account` (e.g. ['tg_user:12345']). Defaults to the user's registered Telegram. |
| ttl_minutes | integer | – | Mandatory lifetime in minutes (range: 1 to 1440). Alerts automatically expire afterward. |
No output schema declared.
No examples provided.
calc_engine ~365
BEHAVIOR: Deterministic mathematical calculation. Evaluates crypto futures risk management models using live exchange parameters. PRICING: $0.001 USD per execution. Deducted from daily tariff quota or USD balance. SYNTAX EXAMPLES (Passed in 'command'): - '/pos btc 65k 63.7k 50' (Position Sizing) - '/liq sol 20x short' (True Liquidation with MMR) - '/dca btc 65k:100 64k:200' (DCA Break-Even with exit fees) - '/rr btc 65k 64k 67k 69k' (Multi-Target R:R) - '/fncost btc 10000 long' (Carry Cost) - '/atr btc 1h 2' (Volatility Stops) RETURNS: Output is a structured JSON payload. Depending on the command, keys include: 'ideal_lot_coins', 'notional_usd', 'required_margin', 'liquidation_price', 'true_breakeven_price', 'effective_rr_ratio', or 'stop_distance'. USAGE GUIDELINES: Use this tool exclusively for mathematical risk modeling and lot sizing. For live market scanning, use `market_data`. For setting execution triggers, use `alert_manager`. After calculating risk parameters, it is highly recommended to route the generated stop-loss or liquidation prices into `alert_manager` to automate monitoring. ERRORS: Malformed syntax returns an 'error' JSON key with correction guidance.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The CLI risk command (e.g. '/pos btc 65000 63700 50'). |
| exchange | string | – | Default exchange context if not explicitly specified inside the command string. |
No output schema declared.
No examples provided.
market_data ~480
BEHAVIOR: Read-only analytical gateway. Fetches real-time derivatives intelligence across Binance, Bybit, and Hyperliquid. PRICING: $0.001 USD per execution. Deducted from daily tariff quota or USD balance. ACTIONS & RETURNS: - 'screener': Scans 1,650+ perpetuals to catch pumps, dumps, whale volume spikes, and short squeezes. Returns a JSON array of matched assets containing fields: symbol, price, rvol, fund, oi, oichg, rsi, bias, natr, cvd. - 'consensus': Returns JSON with Quant TA consensus score, CVD slope, RSI, ATR, and EMA bias for a single coin. - 'bct_matrix': Returns compact historical candlestick matrices with server-side computed indicators to minimize token usage. USAGE GUIDELINES: Use this to analyze market state or find trade setups. Do NOT use this tool to continuously poll for price updates or wait for conditions to be met; instead, invoke `alert_manager` to establish asynchronous monitoring. ERRORS: Malformed filters or unlisted tickers return an explicit JSON error object with syntax correction guidance.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Analytical action to perform. |
| coin | string | – | Asset ticker (required for 'consensus' and 'bct_matrix', e.g. 'BTC'). |
| columns | array | – | Selective columns for 'bct_matrix' to minimize inference tokens. |
| command | string | – | Filter command for 'screener' (e.g. 'vol>10m rvol>2 fund<0 sort:rvol_desc'). Omit for default radar. |
| exchange | string | – | Exchange scope. 'agg' provides volume-summed cross-exchange data. |
| indicators | array | – | Technical indicators for 'bct_matrix' (e.g. ['rsi:14', 'ema:200']). Computed server-side. |
| inline_indicators | boolean | – | If True, appends indicator values to every row. If False, snapshots latest values in @META. |
| limit | integer | – | Result count limit: 1-25 for 'screener', 1-512 for 'bct_matrix'. |
| tf | string | – | Candle timeframe interval (used only for 'bct_matrix'). |
No output schema declared.
No examples provided.
send_notification ~406
BEHAVIOR: Outbound messaging operation. Routes proactive notifications to the human trader's verified Telegram chat, channel, or Discord webhook. Dispatches discretionary trade ideas, market condition updates, or risk reports to keep the user informed without waiting for prompts. PRICING: $0.001 USD per dispatch. Deducted from daily tariff quota or USD balance. PARAMETER INTERACTIONS: - 'target': Destination identifier string obtained from `user_account.list_destinations`. Prefixes determine transport: 'tg_user:' / 'tg_channel:' for Telegram, 'out_wh:' for Discord webhooks. Must belong to the authenticated account. - 'message': Main message body. For Telegram, supports HTML tags. For Discord, maps to the embed description. - 'title': Optional subject line. For Discord, renders as the embed headline. For Telegram, prepends as a bold header if provided. RETURNS: Structured JSON confirming transmission: 'status' ('dispatched'), 'target', 'message_length', 'timestamp_utc', and '_usage' (cost_usd and remaining quota/balance). USAGE GUIDELINES: Call `user_account` with action='list_destinations' prior to sending to retrieve valid target strings. Use this tool exclusively for informative messaging and human-in-the-loop updates. Do NOT use this tool to monitor market prices or set execution triggers (use `alert_manager` instead). ERRORS: Unauthenticated calls, unverified/foreign destinations, empty messages, or exhausted quotas return an explicit 'isError: true' payload.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Notification content. HTML tags supported for Telegram: <b>, <i>, <code>, <pre>. |
| target | string | yes | Verified delivery route (e.g. 'tg_user:12345678', 'out_wh:discord_vip') retrieved via `user_account.list_destinations`. |
| title | string | – | Optional headline used as Discord embed title or Telegram bold subject line. |
No output schema declared.
No examples provided.
system_docs ~290
BEHAVIOR: Read-only RAG documentation tool. Reads and returns official BitCLI markdown specifications, indicator formulas, CLI command guides, and webhook setups. Returns a single string containing the requested Markdown document. PRICING: Free ($0.000). Does not consume quotas. USAGE GUIDELINES: Use this tool FIRST to understand BitCLI mechanics, verify command grammar, or check webhook templates before constructing queries. Do NOT use this tool to query live market prices or active triggers (use `market_data` or `alert_manager` instead). TOPICS: - 'syntax': Price targets, percentage corridors, velocity moves. - 'calculators': Position sizing, true MMR liquidation, DCA break-even, multi-target R:R. - 'market_intel': Screener filters, cross-exchange aggregation. - 'indicators': CVD divergence, Z-Scores, 8h normalized funding. - 'webhooks': PineScript relay setup, private chat routing. - 'tariffs': Subscription tiers and limits. - 'partners': Affiliate program rules. - 'ai': AI Copilot features. - 'mcp': Model Context Protocol architecture, API key setup, and Cursor IDE integration. - 'index': System overview. ERRORS: Requesting an invalid topic returns a structured JSON error indicating the file was not found.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Specific documentation chapter to retrieve. |
No output schema declared.
No examples provided.
user_account ~199
BEHAVIOR: Read-only configuration query. Inspects user ledger states, subscription tiers, and verified notification endpoints. PRICING: Free ($0.000). Does not consume daily quotas or balance. ACTIONS: - 'get_billing': Returns subscription tier, available daily USD API quota, remaining USD balance, active alert count, and per-key daily spending safety limits. - 'list_destinations': Returns verified external dispatch targets (Telegram chat IDs, Discord Webhooks) that can be supplied to the `alert_manager`. USAGE GUIDELINES: Use this tool at the beginning of a workflow to understand available budget and determine valid delivery destinations. Do NOT use this tool to manage triggers (use `alert_manager`) or query market data (use `market_data`). ERRORS: Unauthenticated requests lacking a valid API key return an HTTP 401 equivalent error with a registration portal link.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Account action to perform. |
No output schema declared.
No examples provided.
How do I install the BitCLI MCP server?
BitCLI is a hosted endpoint at https://mcp.bitcli.io/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 · mcp.bitcli.io
claude mcp add --transport http bitcli-io-bitcli-mcp-server 'https://mcp.bitcli.io/mcp'
What is the BitCLI MCP server?
BitCLI is an MCP server listed in the public MCP registry as io.github.BitCLI-io/bitcli-mcp-server. Real-time crypto futures order flow, BCT-30 matrices, and HFT alerts across 1,650+ contracts. This page covers its hosted endpoint (https://mcp.bitcli.io/mcp).
Is the BitCLI MCP server safe to use?
BitCLI scores 60 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 BitCLI MCP server expose?
BitCLI exposes 6 tools: system_docs, market_data, calc_engine, alert_manager, user_account, send_notification. Their descriptions and schemas cost roughly 2,137 tokens of context every time the server is loaded.
Does the BitCLI MCP server require authentication?
No. We connected to BitCLI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BitCLI MCP server still maintained?
BitCLI 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.