LiqSonar

com.liqsonarPublished by liqsonar.comOfficial publisherv1.1.0Updated Oct 30, 2026

Crypto futures order-flow signals, pumps, liquidation levels, order book walls and verdicts

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant LiqSonar crypto futures order-flow signals, pump alerts, liquidation levels, order book walls and verdicts.

What you can do
  • Retrieve crypto futures order-flow signals and market verdicts.
  • Look up pump alerts and liquidation levels.
  • Inspect order book walls and related market data.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to pull crypto futures market intelligence — order flow, liquidation levels, order book walls and pump signals — into a conversation or analysis without leaving the chat.
Requirements
A remote MCP connection to the LiqSonar endpoint over streamable HTTP. Authentication is required: either OAuth sign-in, or an Authorization header carrying a LiqSonar Pro API key (lsk_...) obtained from the provider's API docs page.
Before you install
The server handles trading-related market data, not financial advice; treat signals and verdicts as informational. A Pro API key is a secret and should be kept out of shared logs. Signing in over OAuth grants the server access to your LiqSonar account. No write or payment actions are described in the available material.

Installation

In SourceWeft

  1. Open LiqSonar in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.liqsonar%2Fliqsonar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "liqsonar": {
      "type": "http",
      "url": "https://liqsonar.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestOct 30, 2026
  2. v1.0.0Oct 30, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.