Back to Browse

Liqscope MCP Server

Developer ToolsModerate5.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

Crypto liquidation data: liquidation maps, totals, funding, open interest and fear and greed.

About

Crypto liquidation data: liquidation maps, totals, funding, open interest and fear and greed.

Security Report

5.7
Moderate5.7Moderate Risk

liqscope is a thin forwarding client that answers tools/list from local literals and sends each tools/call with its arguments to the hosted liqwall.com MCP endpoint, which matches its stated purpose of reading public crypto market data. No malicious patterns, shell execution, or hardcoded secrets were found. The main concerns are low: the LIQWALL_MCP_URL override can redirect requests, and an optional API key would then be sent to whatever URL is configured. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Overrides the upstream endpoint. The default is the pinned hosted endpoint, https://liqwall.com/mcp. (The override variable is a reconstruction added by this rebuild.)Required

Environment variable: LIQWALL_MCP_URL

When set, its value is sent to the upstream on every request as an X-API-Key: <value> header. When it is not set, no key header is sent at all, matching the keyless behaviour the tool surface was captRequired

Environment variable: LIQWALL_API_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "liqscope": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/liqscope@0.1.0"
      ],
      "env": {
        "LIQWALL_API_KEY": "your-liqwall-api-key-here",
        "LIQWALL_MCP_URL": "your-liqwall-mcp-url-here"
      }
    }
  }
}

Some servers take additional arguments. See the repository for details.

Documentation

View on GitHub

From the project's GitHub README.

liqscope

Crypto liquidation data is scattered across exchanges and dashboards. liqscope is a small local bridge to the hosted Liqwall MCP service: you can see where forced liquidations cluster around the current price of a market, how much was liquidated in the last day or hour, how perpetual futures are positioned on funding and open interest, and what the Fear and Greed Index says about market mood right now.

Nothing is stored or computed on your own machine. This package answers tools/list locally from the captured tool definitions and forwards every tools/call to the hosted service over a streamable-HTTP JSON-RPC session, returning whatever the service sends back unchanged.

The tools

Every tool in this surface reads public crypto market data. None of them places an order, opens a position, writes anything, buys anything, starts a subscription, or creates an API key.

  • liquidation_map — Where forced liquidations stand around the current price of one market: USD amounts of long liquidations below the price and short liquidations above it, on Hyperliquid and across large exchanges. Returns the price, totals near the price, the largest levels on each side with their distance, and the live map URL. Requires a coin ticker such as BTC, ETH or SOL; names like Bitcoin and pair names like BTCUSDT are accepted too.
  • liquidations — How much was liquidated in the last 24 hours and the last hour, longs against shorts, for the whole crypto market or for one coin. Returns totals, the split by coin or by exchange, the largest liquidations of the last hour, and the page URL. The coin argument is optional.
  • derivatives — Funding rates, open interest and the long/short ratio of perpetual futures, for one coin or for the ten largest coins by open interest. Returns the Binance funding rate and the average across exchanges, open interest in USD with its changes, and the share of accounts and top traders that are long. The coin argument is optional.
  • fear_greed — The crypto Fear and Greed Index on a scale from 0 (extreme fear) to 100 (extreme greed), for the whole market or for BTC, ETH or SOL, with the values a day, a week and a month ago. The coin argument is optional.

Install and run

As an MCP server via npm:

npx -y @reneturcios/liqscope mcp

MCP client configuration:

{
  "mcpServers": {
    "liqscope": {
      "command": "npx",
      "args": ["-y", "@reneturcios/liqscope", "mcp"]
    }
  }
}

As a container:

docker run -i ghcr.io/cloudcorprecords/liqscope
docker run --rm ghcr.io/cloudcorprecords/liqscope liquidation_map '{"coin":"BTC"}'

CLI

One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:

liqscope liquidation_map '{"coin":"BTC"}'
liqscope liquidations '{"coin":"ETH"}'
liqscope liquidations '{}'
liqscope derivatives '{"coin":"SOL"}'
liqscope fear_greed '{}'
liqscope --version

Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.

Configuration

  • LIQWALL_MCP_URL — Overrides the upstream endpoint. The default is the pinned hosted endpoint, https://liqwall.com/mcp. (The override variable is a reconstruction added by this rebuild.)
  • LIQWALL_API_KEY — When set, its value is sent to the upstream on every request as an X-API-Key: <value> header. When it is not set, no key header is sent at all, matching the keyless behaviour the tool surface was captured with. (The hosted service's registry record pins the X-API-Key header name; the environment-variable forwarding is a reconstruction added by this rebuild.)

Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with liqscope error:.

How forwarding works

The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.

Development

npm install
npm run build   # tsc -> dist/ (dist/cli.js is the bin)
npm test        # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev     # run the CLI from source

The test suite checks the served tool list against the captured surface tool by tool, exercises the session handshake and its reuse, covers both key-header branches, and verifies that arguments go upstream untouched and results come back untouched.

License

MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.

Reviews

No reviews yet

Be the first to review this server!