BotIndex MCP Server — Market Intelligence Layer for AI Trading Agents
Problem
AI trading agents using Bitget Agent Hub have execution capabilities (place orders, manage positions, query balances) but lack a structured market intelligence feed to inform what to trade and when.
Agents currently need to:
- Scrape multiple data sources for funding rate arbitrage signals
- Monitor token launch quality across platforms (Pump.fun, Doppler, Jupiter)
- Track cross-exchange price divergences
- Assess on-chain sentiment and whale flows
This is undifferentiated work that every agent builder reimplements.
Proposal: BotIndex as the Intelligence Layer
BotIndex MCP Server provides 11 structured endpoints covering crypto market intelligence — designed specifically for AI agent consumption.
Relevant endpoints for Bitget trading agents:
| Endpoint |
What it returns |
Trading use case |
funding-arb |
Cross-exchange funding rate arbitrage opportunities |
Delta-neutral carry trades on Bitget futures |
signals |
Aggregated market signals (momentum, sentiment, volume) |
Entry/exit timing |
doppler/trending |
Real-time token launch velocity on Base |
Early position entry via Bitget spot |
pumpfun/graduating |
Solana tokens approaching graduation threshold |
Momentum trades |
correlation-leaders |
Cross-asset correlation breakdown signals |
Portfolio hedging on Bitget futures |
Integration Example
An agent with both MCP servers installed:
# codex.toml — or equivalent MCP config
[[mcp_servers]]
name = "bitget"
command = "npx"
args = ["-y", "bitget-mcp-server"]
[mcp_servers.env]
BITGET_API_KEY = "..."
BITGET_SECRET_KEY = "..."
BITGET_PASSPHRASE = "..."
[[mcp_servers]]
name = "botindex"
command = "npx"
args = ["-y", "botindex-mcp-server"]
Agent workflow:
botindex_funding_arb → finds BTC funding rate divergence (Bitget -0.03% vs HyperLiquid +0.05%)
bitget_futures_get_funding_rate → confirms Bitget's current rate
bitget_spot_place_order + bitget_futures_place_order → executes delta-neutral position
botindex_signals → monitors for exit signal
Details
Happy to collaborate on a combined quickstart guide or example agent that demonstrates the intelligence → execution pipeline.
BotIndex MCP Server — Market Intelligence Layer for AI Trading Agents
Problem
AI trading agents using Bitget Agent Hub have execution capabilities (place orders, manage positions, query balances) but lack a structured market intelligence feed to inform what to trade and when.
Agents currently need to:
This is undifferentiated work that every agent builder reimplements.
Proposal: BotIndex as the Intelligence Layer
BotIndex MCP Server provides 11 structured endpoints covering crypto market intelligence — designed specifically for AI agent consumption.
Relevant endpoints for Bitget trading agents:
funding-arbsignalsdoppler/trendingpumpfun/graduatingcorrelation-leadersIntegration Example
An agent with both MCP servers installed:
Agent workflow:
botindex_funding_arb→ finds BTC funding rate divergence (Bitget -0.03% vs HyperLiquid +0.05%)bitget_futures_get_funding_rate→ confirms Bitget's current ratebitget_spot_place_order+bitget_futures_place_order→ executes delta-neutral positionbotindex_signals→ monitors for exit signalDetails
botindex-mcp-server(1.3.1)io.github.Cyberweasel777/botindex-mcp-serverHappy to collaborate on a combined quickstart guide or example agent that demonstrates the intelligence → execution pipeline.