Crypto Liquidations MCP

What kukapay/crypto-liquidations-mcp MCP server does

The kukapay/crypto-liquidations-mcp MCP server collects real-time liquidation events from Binance and makes the recent data available to MCP-compatible clients. It is intended for agents that need short-term visibility into forced futures orders and broader liquidation activity across trading pairs.

The server retains up to 1,000 events in an in-memory collection. It does not write the data to disk or provide persistent storage, so the available history begins when the process starts and is lost when the process stops.

How it works

After launch, the server connects to Binance's futures WebSocket endpoint for aggregate force-order events. Incoming records are held in memory while the process remains active. Internet access is required for this connection.

Clients can request recent records through the get_latest_liquidations tool. Results are returned as a Markdown table with the trading symbol, order side, price, quantity, and event time. The time is formatted as HH:MM:SS. The request accepts a limit value, which defaults to 10 and can be used to request up to 1,000 retained events.

The analyze_liquidations prompt provides instructions for examining liquidation trends across symbols. It is designed to work with the retrieval tool and directs analysis toward event frequency, volume, and possible market impact.

Setup and configuration

The kukapay/crypto-liquidations-mcp MCP server requires Python 3.10, the uv package and dependency manager, and network access to Binance. The documented setup flow is to clone the repository, change into its directory, and run uv sync to install dependencies.

An MCP client then needs to start the server with the repository directory and main.py, using a configuration equivalent to the documented Claude Desktop example. The example contains a local path placeholder that must be replaced with the directory where the repository was cloned. No API key, token, or other credential is specified in the provided setup instructions.

Tools and capabilities

• get_latest_liquidations: Returns the newest retained liquidation events in a Markdown table.
• analyze_liquidations: Supplies a prompt for analyzing liquidation patterns across trading pairs.
• Binance WebSocket ingestion: Receives aggregate force-order events in real time.
• In-memory retention: Keeps a maximum of 1,000 recent events during the current process.

The kukapay/crypto-liquidations-mcp MCP server is suitable for displaying recent liquidation activity, feeding current event data into an agent's market analysis, or examining whether liquidation frequency and volume are changing across symbols.

Limitations and notes

Data is limited to the events captured since the server started and the latest 1,000 records. Restarting the process clears the collection. The material does not describe a database, historical backfill, configurable retention period, logging system, or trading execution capability.

The server depends on Binance's futures WebSocket availability and requires an active internet connection. The documented client integration specifically shows Claude Desktop; compatibility with other clients is not established by the provided material. The kukapay/crypto-liquidations-mcp MCP server reports liquidation records but does not itself claim to place orders or provide investment recommendations.