Official Model Context Protocol (MCP) specification and server implementation fo
Official Model Context Protocol (MCP) specification and server implementation for BitCLI. Connect Cursor, Claude, or AutoGPT to live order flow.
active Production-safe Score 87/100 http no auth
At a glance
| Endpoint | https://mcp.bitcli.io/mcp |
|---|---|
| Source | https://github.com/BitCLI-io/bitcli-mcp-server |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-11-02 00:07:43 |
| Last checked | 2026-11-17 21:27:07 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 1153 / 1694 ms |
| Last successful check | 2026-11-17 21:27:07 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
system_docs— BEHAVIOR: Read-only RAG documentation tool. Reads and returns official BitCLI markdown specifications, indicator formulas, CLI command guidemarket_data— BEHAVIOR: Read-only analytical gateway. Fetches real-time derivatives intelligence across Binance, Bybit, and Hyperliquid. PRICING: $0.001calc_engine— BEHAVIOR: Deterministic mathematical calculation. Evaluates crypto futures risk management models using live exchange parameters. PRICING:alert_manager— BEHAVIOR: State-mutating operation. Injects or removes in-memory execution triggers in the C++ engine. When triggered, it dispatches asynchruser_account— BEHAVIOR: Read-only configuration query. Inspects user ledger states, subscription tiers, and verified notification endpoints. PRICING: Fresend_notification— BEHAVIOR: Outbound messaging operation. Routes proactive notifications to the human trader's verified Telegram chat, channel, or Discord web
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:27:07 | ✓ | ✓ | 1709 ms | 85 | active |
| 2026-11-17 20:49:18 | ✓ | ✓ | 1043 ms | 85 | active |
| 2026-11-17 20:20:22 | ✓ | ✓ | 1110 ms | 85 | active |
| 2026-11-17 19:33:33 | ✓ | ✓ | 1082 ms | 85 | active |
| 2026-11-17 18:57:11 | ✓ | ✓ | 1266 ms | 85 | active |
| 2026-11-17 18:27:43 | ✓ | ✓ | 1106 ms | 85 | active |
| 2026-11-17 17:46:38 | ✓ | ✓ | 1027 ms | 85 | active |
| 2026-11-17 17:01:00 | ✓ | ✓ | 1752 ms | 85 | active |
| 2026-11-17 16:28:15 | ✓ | ✓ | 1578 ms | 85 | active |
| 2026-11-17 15:44:45 | ✓ | ✓ | 1250 ms | 85 | active |
| 2026-11-17 14:55:55 | ✓ | ✓ | 1147 ms | 85 | active |
| 2026-11-17 14:25:44 | ✓ | ✓ | 1078 ms | 85 | active |
| 2026-11-17 13:40:40 | ✓ | ✓ | 1090 ms | 85 | active |
| 2026-11-17 12:56:42 | ✓ | ✓ | 1050 ms | 85 | active |
| 2026-11-17 12:40:12 | ✓ | ✓ | 1217 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.bitcli.io/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-bitcli-io-mcp # JSON