Liquidation structure
Separate heatmap density from liqmap levels
Read Binance heatmaps as model-based density fields, then use single- or multi-exchange liqmaps for ranked price levels above and below spot.
Kingfisher intelligence for AI agents
Kingfisher MCP connects compatible AI clients to Binance heatmaps, multi-exchange liquidation maps, market crowding, toxic order flow, open interest, and GEX+ dealer flows. Ask in plain language and receive a conditional read with units, sign conventions, and invalidations.
https://mcp.thekingfisher.io/mcp Paste this exact URL into a compatible remote MCP client. This page is the guide; the mcp. subdomain is the server.
Where does BTC liquidation pressure sit, and how does GEX+ change the risk?
Rank the liquidation levels, then compare gamma, vanna, charm, and measured spot/IV beta before calling the regime stabilizing or destabilizing.
Example Kingfisher synthesis.Kingfisher market dataMaps · GEX+ · Greeks · TOF · OI
Documented skillsContext · method · guardrails
Your AI agentClear, conditional answers
The interpretation layer
Kingfisher MCP pairs every dataset with purpose-built analytical guidance. Your agent gets both the evidence and the method needed to reason about it.
Liquidation structure
Read Binance heatmaps as model-based density fields, then use single- or multi-exchange liqmaps for ranked price levels above and below spot.
Crowding & flow
Combine liquidation ratios, open interest, funding, and normalized toxic order flow instead of relying on a single noisy indicator.
Options mechanics
Combine gamma, vanna, charm, asymmetric spot/IV beta, strike-level pin pressure, and settlement schedules without mixing raw flow and stabilizing-score signs.
Conditional analysis
Synthesize structure, crowding, triggers, and propagation into a conditional risk matrix with clear confirmations and invalidations.
One prompt, complete context
Instead of treating every indicator as an isolated signal, the agent builds a sequence of evidence and tells you exactly what still needs to happen.
Find persistent liquidation density above and below price.
Check whether positioning supports or contradicts the map.
Compare directional GEX+, charm drift, and the measured spot/IV relationship.
Normalize order flow and momentum against their own recent history.
Return the read, its confidence, and what would invalidate it.
One endpoint, live capabilities
The remote server exposes the market data and analytical methods below through OAuth 2.1. Tool names are part of the public MCP contract, so an agent can select them directly.
Binance heatmap density, ranked single- or multi-exchange liqmap levels, and Binance multipair cohorts.
get_liquidation_heatmapget_heatmap_symbolsget_multipair_liqmapget_latest_mapCurrent and historical GEX, directional GEX+, gamma/vanna/charm flow, pin pressure, scheduled charm drift, and measured spot/IV beta.
get_gamma_exposureget_time_gexget_greek_flowsget_gex_plus_mapget_charm_pin_pressureget_charm_tideget_charm_heatmapget_volatility_betaToxic order flow, supported TOF markets, RSI distribution, open interest, funding, and liquidation imbalance.
get_toxic_order_flowget_tof_available_pairsget_rsi_screenerget_open_interestget_liq_ratiosVisible Futures order book, aggregate trades, premium index, funding, and open interest for execution context.
mcp_binance_get_orderbookmcp_binance_get_agg_tradesmcp_binance_get_market_dataOfficial recovery instructions when a compatible client needs to complete or renew OAuth.
get_kingfisher_authentication_helpExpert knowledge, on demand
Each skill gives your agent a narrow, testable way to work with a Kingfisher dataset—from discovering available markets to synthesizing a cross-signal risk matrix.
Official setup
The setup prompt tells an AI agent how to configure Kingfisher as a remote MCP server, preserve existing settings, complete OAuth, and verify the connection. You only step in for browser sign-in and consent.
get_heatmap_symbolshttps://mcp.thekingfisher.io/mcpThese are official Kingfisher instructions for connecting an AI agent to the remote MCP server. Complete every step you can directly. Ask the user only for unavoidable browser sign-in, consent, or permissions.
Use remote Streamable HTTP · Authenticate with OAuth 2.1 + PKCE · Never request an API key