Live Order Book Heatmap & Order Flow

io.github.MaestroW4rd0Published by GitHub account MaestroW4rd0v1.0.0Updated Oct 29, 2026

Live crypto order book heatmap PNG, CVD, imbalance and liquidations from 4 public exchange feeds.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote Apify-hosted MCP server that gives an assistant live crypto order book heatmap images, CVD, imbalance and liquidation data from four public exchange…

What you can do
  • Generate live order book heatmap PNG images from public exchange feeds
  • Read cumulative volume delta (CVD) and order book imbalance figures
  • Retrieve liquidation data alongside the heatmap view
  • Draw on four public crypto exchange feeds in one place
When to use it
Useful when you want an assistant to pull a quick visual and numeric read on crypto order flow — heatmaps, imbalance, CVD or liquidations — without building your own exchange data pipeline.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. Authentication is required: either an Apify API token sent as a Bearer token in the Authorization header, or signing in to Apify via OAuth. Network access to the endpoint is needed.
Before you install
Access requires an Apify account credential (an API token in the Authorization header or OAuth sign-in), so treat that token as a secret. The data comes from public exchange feeds and is informational only; it is not trading advice and no trading actions are described.

Installation

In SourceWeft

  1. Open Live Order Book Heatmap & Order Flow 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/io.github.MaestroW4rd0%2Forderbook-heatmap-live/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": {
    "live-order-book-heatmap-order-flow": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=gleaming_carp/orderbook-heatmap-live"
    }
  }
}

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

1
  1. v1.0.0LatestOct 29, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.